Developer Experience

I'm no English major, but as a writer and consumer of loads of educational (mostly tech) writing, I've come to notice a number of words and phrases that come

Technical writing and editing services

Learn to integrate the craft of writing with the craft of programming. This book teaches you how to create documentation for each step in...

This book provides a broad perspective about the essential aspects of creating technical documentation in today's product development wor...

I recently contributed to a series of fireside chats hosted by LaunchDarkly. One of the themes that we discussed was Developer Experience, and how to improve it. I was asked by one of the attendees at the EMEA event (video here, interview by Cody De Arkland) about further reading on the subject and offered to

While I’ve made a case for Developer Experience (DevEx) – aptly named The Case for a Great Developer Experience – I realized it was making the case to other developers. Obviously developers understand that better docs, a good design, and useful examples make a product easier to use. But how do we quantify that? How […]

The Developer Experience organization at Netlify is quite unique. In this post, we talk through the structure of the organization, how we work, who we are, and some of our team strategies.

In the world of web APIs, the need for governance and shared standards increases as a business seriously considers its data value and platform strategy.

With multiple trends pointing at the growth of the developers buying power in organizations, the mark...

As newer versions of systems are rolled out every day, more powerful and useful functions, APIs, methods, classes are developed in the…

Why is @stripe's API so good?Teams debate the naming of each field, talk about trade-offs, and attempt to plan ahead for new features that may change the shape of the API.We *take the time* to get it right, and individual engineers recognize the best design requires teamwork.— Zach Tratar (@zachtratar) February 21, 2020

Ben Nadel thinks about all of the changes that you can make in an API which could be considered a "breaking change" for a consumer. Depending on how hard you squint, the breadth of breaking changes can be quite a bit larger than we usually think it is.

Written communication tips for effective software developers

Zapier Visual Identity

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.

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

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

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.