Developer relations

There are a number of challenges that DevRel professionals face day to day. In this blog, I’ll cover 5 of these common challenges and how to mitigate them.

One of the least and most loved roles in development teams has many names — developer evangelist, developer advocate, DevRel lead, engaged anthropologist, platform customer success, developer relations manager, developer community manager, solutions engineer, tech marketer, to name a few — and its daily tasks varies by company.Simply put, the role of the developer advocate is to help get software developers excited about building on top of your product.

Clear guidance on what is readable on slides. Font size, colors, what shows up best on the displays at the conference center. https://t.co/82kz4zTzER— Katie Cunningham (@kcunning) April 22, 2019

How Glossier used a reader-centric approach to simplify their development team’s code deployment process and improve velocity.

Tips to help engineering teams produce high-quality documentation—with or without the support of designated technical writers.

Imagine this. You’re a woman in a male-dominated field. English is not your first language. Even though you’re confident in your…

Hi, I’m Perry Eising, and I’m on a mission to make tech more approachable and inclusive. I’m the former faculty lead of Epicodus, and a…

The Eisenhower Decision Matrix: How to Distinguish Between Urgent and Important Tasks and Make Real Progress in Your Life

Developer Relations (DevRel) is an interdisciplinary role that sits in a border space between product, engineering, and marketing.

When you travel for work, bring a piece of home with you to make your trips less stressful and more effective.

Here's the key: I understand enough to have a knowledgeable conversation & I know who the right person is to pass the community member off to once I hit my limit. I'm the connector. That ability, not my technical acumen, is what makes me successful.— Mary Thengvall - staycation mode 😎 (@mary_grace) December 28, 2018

Over the last few years, I've seen more and more blogs move over completely or partially to Medium. And while a few years ago that might…

Avoiding oversimplification, writing good error messages, and having better word choice

How do people actually read documentation and how to write documentation and code samples to maximize developer success

Community building is fundamentally about relationships. How do you conduct a cost-benefit analysis on a relationship? We'll share what we've learned.

However hard you work on documentation, it won't work for your software - unless you do it the right way.

How Not to Run a Hackathon

DevRel ProTips: 1) Don't demo things people can't immediately use. 2) Be crystal clear on your message and never do something just because you can if it doesn't further your message.— Aja Hammerly 🦖 (@the_thagomizer) July 17, 2018

whatspeakersneed - A guide to what speakers need to make your conference awesome

Writing clear, helpful copy for when things go wrong • by Marina Posniak & Tamara Hilmes

Take your API documentation to the next level with these expert tips from Diana Lakatos.

Cristiano Betta gives an insight into his developer experience consultancy and his DevRelCon London 2017 talk "Live API teardown".

Many tech writers have a heavy disdain for Frequently Asked Questions (FAQs) in documentation. At first this disdain seemed a bit unfounded and elitist to me, but now, after a recent project, I'm starting to understand the reasons for the disdain. All too often the FAQ format is abused by non-writers who want an easy way to write. The list of random questions grows with each incoming question until it's a ridiculous hodgepodge of information thrown together, with no larger story or narrative.

This post is a write up of a talk given at DevRelCon Tokyo 2017 and a few other events. Slides for this talk are available on Speaker Deck. Prologue We all occasionally have one of these days where...

Notes on advocacy, design, and building better developer products.