My podcast about writing with Ellis Pratt on Cherryleaf
You can listen to the podcast here:
Or go directly to the Cherryleaf post: Podcast 49: Should you specialise? Interview with Tom Johnson.
Alan Houser noted on Twitter that this podcast is “unusually introspective, always insightful”:
An unusually introspective, always insightful episode of the Cherryleaf Podcast. Hat tip to host @ellispratt and guest @tomjohnson https://t.co/h44qs9NCVc #techcomm
— Alan Houser (@arh) December 12, 2018
Here’s a list of some of the topics discussed:
- Why I write so much on my blog, and purposes for writing
- How the personal essay format fits so well into blogging
- Blogging as a means of discovery versus simply expressing knowledge
- The influence of blogs and podcasts, and how this leads to presentations and workshops
- Why a 1,000-word mediocre post might lead to more clicks on ads (the negative influence of social media on writing)
- The growing influence of voice and why I’m reading my longer posts
- The original reason for my series on simplifying complexity, and where there was more disagreement/controversy
- Finding evidence for trends to know which direction we’re really moving
- Why academics are also looking at trends (so they can prepare their students for success in the workplace)
- Why job ads often look for candidates that don’t exist, such as someone who can program in 5 languages and who also has strong writing abilities
- Why it’s so difficult to measure writing as you’re evaluating candidates during job searches (and why checking boxes for technical skills is much easier)
- Ellis’s perspective as a recruiter in determining what companies are looking for in candidates
- Why deep technical knowledge is essential for writing in the developer domain (if you want to avoid merely being an editor/publisher)
- How you define yourself – as a generalist, doc tooling specialist, programming languages, API documentation, or other area?
- Why API documentation is getting simpler in part through standards such as the OpenAPI specification
- Why people don’t always value writing, and how tech writers are embracing different specializations as a result
- Strategies to reduce complexity by separating tool knowledge from content knowledge
Here are links to some of the articles we discussed:
- Tech comm trends – why tech writers will be collaborating more with engineers
- Principle 11: Be both a generalist and specialist at the same time
- Clients from Hell
You can find more podcasts from Ellis at Cherryleaf > Podcasts.
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.