Podcast: 10 myths about API documentation
Listen here:
10 myths about API documentation
Here are the myths I address in the podcast.
- You must read source code to write docs.
- You’ll need to extrapolate sample code from one language to create code samples in another.
- You must be a former engineer to be competitive in the API doc space.
- Technical writers usually create the reference material (e.g., OpenAPI spec, Javadoc).
- Almost all job interviewers care about, when it comes to API doc jobs, is technical know-how.
- Developers can and will write if you implement a docs-as-code process.
- Because their role aligns with the audience, with API docs, developers are most suited to be the ones writing for other developers.
- API documentation and developer documentation are synonymous.
- Docs that look good are good.
- People will respect you more if the word “writer” isn’t in your job title.
In the podcast, I mentioned this NY Times article: In the Salary Race, Engineers Sprint but English Majors Endure.
Your Feedback
Here’s a short survey to see if you think these myths are generally true or false. (It would be best if you listened to the podcast first.) You can view the ongoing results here.
About 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.