Search results

2025 archives

  1. Switching from Commento to LinkedIn for Blog Comments

  2. Podcast: How AI is changing the role of technical writers to context curators and content directors

  3. Two strategies to succeed when AI seems to be eroding jobs around you

  4. Book review of 'Empire of AI: Dreams and Nightmares in Sam Altman's OpenAI' by Karen Hao

  5. Recording of AI Book Club discussion of Karen Hao's Empire of AI: Dreams and Nightmares in Sam Altman's OpenAI

  6. Defining bug zero and two obstacles: Reducing review time and gathering context

  7. Recording of AI Book Club discussion about Kai-fu Lee's AI Superpowers

  8. Why getting to bug zero is so hard

  9. Recording of Coffee and Content episode: What's wrong with AI-generated docs?

  10. Review of Parmy Olson's Supremacy — and the futility of chasing non-capitalist dreams

  11. Productivity Experiments and Advice: Continuing the Journey with Slow Productivity and Meditations for Mortals — guest post by David Kowalsky

  12. Will our next users be AI agents? The future of content delivery with Fabrice Lacroix, founder of Fluid Topics (podcast)

  13. Why attitudes and experiences differ so much with regards to AI among technical writers

  14. AI Book Club recording and notes for The Singularity is Nearer, by Ray Kurzweil

  15. The problem with single-sourced docs when fact checking with AI

  16. The allure of iterative improvement loops (AI experiments)

  17. My first vibecoding project (AI experiments)

  18. API quick reference guides (and the challenges of passing long content into AI contexts)

  19. Notes and discussion for Suleyman's The Coming Wave: AI, Power, and Our Future + AI Book Club recording and transcript

  20. Reflections on the WTD Portland 2025 conference

  21. AI-powered Enterprise Knowledge Platforms: Fluid Topics Q&A with Fabrice Lacroix

  22. API quick reference diagrams and my upcoming AI the Docs presentation

  23. Speaking up and calling out BS when you see it -- some reflections on Jonathan Rauch's book The Constitution of Knowledge

  24. I feel like I’ve seen the future today

  25. New article added to API documentation site: Document360 for API docs

  26. Notes and discussion for Jonathan Warner's More Than Words: How to Think About Writing in the Age of AI + AI Book Club recording

  27. Book review of Jonathan Warner's book More Than Words: How to think about writing in the age of AI

  28. Book review of Crossings: How Road Ecology is Shaping the Future of Our Planet, by Ben Goldfarb

  29. I'm starting an AI Book Club

  30. Countering AGI with superintelligent docs?

  31. Links from around the web: vibecoding, 60-hour work weeks, smaller internet communities, ethical compromises, and expertise

  32. Do developers need code samples in API documentation?

  33. Fixing bugs without thinking, Recursive Self-Improvement, and the shift towards more complex tech comm tasks

  34. Review of Divided Highways, by Tom Lewis — and some thoughts on techno-utopian disillusionment

  35. Rethinking traditional approaches to release notes -- recording of WTD Australia presentation

  36. Is AI eroding slow mode? Push-button solutions versus thought partners, and approaches to challenging writing tasks

  37. Using AI with issue tracking systems (prompt engineering series)

  38. My 2025 trends predictions for tech comm

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.