Search results

I'm trying to gather more information about common practices with API documentation. I created an informal, open survey about API Doc here.

It's an openly editable Google Doc with about 10 questions. You can see others' responses as you enter your own.

If you do any kind of API documentation, I need your participation in the survey. This will allow me to better generalize common practices with API documentation in preparation for some upcoming presentations and blog posts.

I made it open so you can read the existing responses. I chose to use a short-answer response format because practices with API documentation vary so widely -- one practice often varies from another, and they can't easily be captured with simple radio button responses.

I'm hoping to get 25 responses so that I have a decent enough sample size. Right now I have about 10 responses. Basically, when I give some API doc presentations and someone asks me a question like, "Do developers expect you to learn everything from reading the source code files alone?" I want to provide a realistic answer that extends beyond the scope of my own experience.

Again, here's the link to my API Documentation survey. Thanks.

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.

If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.