Search results

2022 archives

  1. Book review: May I Ask a Technical Question, by Jeff Krinock and Matt Hoff

  2. Thoughts on ChatGPT after reading Crawford's Why We Drive: whatever skill you outsource, atrophies

  3. Having fun with ChatGPT

  4. Two examples where high-level overviews are essential: Macbeth and Elon Musk

  5. Pulling readers through long documents

  6. Stoplight tutorial update -- practically every screenshot updated

  7. Podcast about Archbee -- a new documentation tool with a block-based editor, API publishing capability, content re-use, and more

  8. Attempting to write a Life of a [something] narrative

  9. 'Putting together things': Articulating a thesis about the effects of hyper-specialization on documentation

  10. Expanding from cross-product newsletters to a book club and site

  11. Some advice if you're just starting out your technical writing career

  12. Systems thinking: Limits to Growth, Complex Cause and Effect, and Shifting the Burden

  13. Systems thinking and developer portals

  14. Blobr API portal (API doc topic)

  15. The impact of technical diversity on documentation -- epiphanies on a trip to IKEA

  16. Technical diversity/pluralism/fragmentation in tech comm

  17. My Commute Seattle Spotlight

  18. Review of Peter Norton's Autonorama: The Illusory Promise of High-Tech Driving

  19. Docs as Code

  20. Inline ads -- updated advertising offerings

  21. Keynote presentation to STC India 2022

  22. Remote work

  23. Git and GitHub

  24. API documentation

  25. Every page is page one

  26. Marcom and tech comm

  27. Scrum

  28. Let's Talk Docs podcast -- episode on measuring API documentation quality

  29. The History of Content -- Content Components podcast with Patrick Bosek and Sarah O'Keefe

  30. Preparing for technical writing jobs and interviews -- posts from Aaron Redshaw

  31. Content strategy

  32. DITA

  33. WordPress and web CMSs

  34. Quick reference guides

  35. Screencasting

  36. Faceted filtering

  37. Wikis and crowdsourcing

  38. Help authoring tools (HATs) and single-sourcing

  39. Intro to the series: Trends to follow or forget

  40. [Podcast] Become a technical writer: conversation with Bobby Kennedy about the technical writing courses he offers

  41. My multimodal commuting strategies

  42. Archbee product review -- first look at a new online platform for writing and managing documentation

  43. Part 6: The newsletter as the social content of corporations

  44. MEGAComm recording: How to increase awareness of tech comm inside corporate walls

  45. Updated Metrics and Measurement section in API course to remove scoring aspect

  46. Results of the survey about fizzled trends: Every trend is still with us

  47. Survey about documentation trends that fizzled (one-minute survey)

  48. Webinar recording of 'Using MadCap Flare to Generate API Documentation'

  49. Part 5: More specifics about finding a focus

  50. Part 4: Creating engaging content: A balance of interests

  51. Part 3: Five basics for building an audience on the web

  52. Part 2: Initial attempts and failures with workplace content

  53. Part 1: Introduction to influence on the web

  54. Themes from 2021: working from home and podcasting

  55. Site analytics for 2021 -- a few observations and reflections

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.