The most important element to developer success, with APIs, open source, or other tools, is documentation. Yet, any developer will tell you that most of it isn’t very good. Bad documentation happens on accident, for a lot of reasons…

Adam DuVander
Jul 14, 2016 · 1 min read

Busy working on the product

Don’t know enough about the product

Know too much about the product

Haven’t found the time to focus on it

Not sure what needs to do in the docs

Haven’t encountered your undocumented problem before

Too busy with support requests

Too busy with sales

Haven’t hired that role yet

Docs are “good enough”

Developers aren’t their core customer

Waiting to finish a redesign

Want to completely re-imagine the documentation experience

Too many products to document

Nobody thinks it’s their job

Everybody thinks it’s their job

Well-designed products shouldn’t require documentation

They’re working on it

Trying to get a good framework in place

Don’t understand what the audience wants to know

They’re a marketer not an engineer

They’re an engineer not a tech writer

They’re a tech writer not a marketer

There’s too much going on

Everything else gets a higher priority

Not sure how to make them better

And many more… which ones did I miss? Let me know in a response.

Improve your documentation and developer experience by learning from successful APIs. Subscribe at

Every Developer

We all help make technology

Adam DuVander

Written by

With APIs and people, anything is possible. Mostly it’s the people.

Every Developer

We all help make technology

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade