Search results

2024 archives

  1. Using AI to design landing pages (prompt engineering series)

  2. Why designing landing pages is hard

  3. Unpacking the issues from AI — thoughts on Alan Porter's post Am I the AI Luddite? and Fabrizio Benedetti's How I'm using AI as a technical writer

  4. To establish value, focus more on high priority projects: Reading Michael Lynch's post on why he quit Google to work for himself

  5. Sadik-Khan's Streetfight: Handbook for an Urban Revolution, plus a visual account of Seattle's downtown biking and pedestrian infrastructure

  6. From engineer interviews to written draft, with chain of thought reasoning

  7. New API course on mastering documentation by Mark Wentowski on Docsgeek

  8. Symposium on Usability and Design in France in April 2025

  9. Strategies for making doc bugs actionable

  10. Escaping the Productivity Trap: Experiments with Burkeman's Four Thousand Weeks — guest post by David Kowalsky

  11. NotebookLM podcasts -- the missing piece in the GenAI puzzle?

  12. [Podcast] GenAI and Document360: Conversation with Saravana Kumar

  13. Using AI to jump-start code samples

  14. Unified Knowledge powered by Zoomin -- Q&A with Paul Maass

  15. Two days in my life as a technical writer, followed by reflection and analysis of fragmenting microtasks

  16. What a day in the life of a Technical Writer in the energy industry looks like -- Guest post by Bonnie Denham

  17. Routines and habit stacking

  18. Podcast: Task decomposition and complex tree diagrams

  19. Podcast: Using long-token contexts to quality check an entire API doc set

  20. Podcast: Using file diffs for better release notes in reference docs

  21. Podcast: Populating documentation templates using AI

  22. Podcast: Gathering source material for context input

  23. Podcast: Creating high-fidelity, thematically organized notes from engineering meetings using AI

  24. Blogging as personal training?

  25. Using long-token contexts to quality check an entire API doc set

  26. Seeing invisible details and avoiding predictable, conditioned thought (ZAMM series)

  27. Automate links in your release notes using AI (prompt engineering)

  28. Links from around the web -- June 10, 2024

  29. [Podcast] Uncovering and communicating the value of your tech comm teams' work, with Keren Brown

  30. [Prompt engineering series] Using file diffs for better release notes in reference docs

  31. Updates two years later on my smartphone experiment

  32. Thoughts on Docs as code being a broken promise

  33. Get Better at Using Prompts With Deliberate Practice: One technical writer's little experiment — guest post by Diana Cheung

  34. Prompt engineering series: Creating scripts to automate doc build processes

  35. What should your documentation metrics look like? Q&A with Zoomin about their 2024 Technical Content Benchmark Report

  36. AI is accelerating my technical writing output, and other observations

  37. Upcoming conference: AI the API docs

  38. Prompt engineering series: Gathering source input

  39. Prompt engineering series: Error checking the output

  40. Integrating AI with your content delivery platform and documentation: Zoomin Q&A with Keren Brown

  41. Showcasing your API technical writer portfolio and projects — guest post by Peter Gustafson

  42. Prompt engineering series: Reverse engineering the recipe for excellent documentation

  43. Prompt engineering series: Populating documentation templates using AI

  44. Prompt engineering: Task decomposition and complex tree diagrams

  45. Prompt engineering: Creating high-fidelity, thematically organized notes from engineering meetings using AI

  46. Visualizing APIs with tree diagrams, partly generated with AI

  47. Walking and chatting with ChatGPT

  48. Moved AI pages into their own collection and space

  49. Coffee Chat recording: Ask Me Anything about Managing API documentation projects

  50. Evaluating my 2023 site analytics -- why did my traffic drop?

  51. [Podcast] Breaking ground: New API documentation course at UW, with Bob Watson

  52. My 2024 technical writing trends and predictions

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.