AI and tech comm
The AI-doc category includes content related to language-generative AI tools like ChatGPT, Bard, and others.
The following content is in the ai category:
Using AI to jump-start code samples | Sep 29, 2024
Two days in my life as a technical writer, followed by reflection and analysis of fragmenting microtasks | Sep 8, 2024
Podcast: Task decomposition and complex tree diagrams | Jul 28, 2024
Podcast: Using long-token contexts to quality check an entire API doc set | Jul 28, 2024
Podcast: Using file diffs for better release notes in reference docs | Jul 28, 2024
Podcast: Populating documentation templates using AI | Jul 28, 2024
Podcast: Gathering source material for context input | Jul 28, 2024
Podcast: Creating high-fidelity, thematically organized notes from engineering meetings using AI | Jul 28, 2024
Using long-token contexts to quality check an entire API doc set | Jul 15, 2024
Seeing invisible details and avoiding predictable, conditioned thought (ZAMM series) | Jun 26, 2024
Automate links in your release notes using AI (prompt engineering) | Jun 26, 2024
[Podcast] Uncovering and communicating the value of your tech comm teams' work, with Keren Brown | May 30, 2024
[Prompt engineering series] Using file diffs for better release notes in reference docs | May 25, 2024
Get Better at Using Prompts With Deliberate Practice: One technical writer's little experiment — guest post by Diana Cheung | Apr 23, 2024
Prompt engineering series: Creating scripts to automate doc build processes | Apr 21, 2024
What should your documentation metrics look like? Q&A with Zoomin about their 2024 Technical Content Benchmark Report | Apr 14, 2024
AI is accelerating my technical writing output, and other observations | Apr 14, 2024
Upcoming conference: AI the API docs | Apr 3, 2024
Prompt engineering series: Gathering source input | Mar 20, 2024
Prompt engineering series: Error checking the output | Mar 20, 2024
Integrating AI with your content delivery platform and documentation: Zoomin Q&A with Keren Brown | Mar 18, 2024
Prompt engineering series: Reverse engineering the recipe for excellent documentation | Mar 4, 2024
Prompt engineering series: Populating documentation templates using AI | Mar 4, 2024
Prompt engineering: Task decomposition and complex tree diagrams | Feb 20, 2024
Prompt engineering: Creating high-fidelity, thematically organized notes from engineering meetings using AI | Feb 20, 2024
Visualizing APIs with tree diagrams, partly generated with AI | Feb 13, 2024
Walking and chatting with ChatGPT | Jan 21, 2024
Moved AI pages into their own collection and space | Jan 20, 2024
[Podcast] Breaking ground: New API documentation course at UW, with Bob Watson | Jan 5, 2024
My 2024 technical writing trends and predictions | Jan 1, 2024
Etto, a new AI co-pilot for Heretto — Q&A with Casey Jordan | Dec 18, 2023
Webinar recording: Experiments and use cases for AI from a tech writer’s perspective | Dec 13, 2023
30+ ways I’m using AI in everyday writing life as a technical writer, blogger, and curious human | Dec 4, 2023
Podcast: The evolution of podcasting, with Ed Marsh | Dec 3, 2023
You've heard of 'Docs as code' -- Now get ready for 'Code as docs': Q&A with Speakeasy | Nov 9, 2023
Doing research with AI tools -- avoiding the trap of fabricated URLs | Nov 9, 2023
My experience trying to write original, full-length human-sounding articles using Claude AI | Oct 25, 2023
Chatting about AI trends and tech comm with Fabrizio Ferri Benedetti | Oct 20, 2023
[Podcast] AI and APIs: What works, what doesn't | Oct 14, 2023
Forrester Report, Coding jobs, Hyper-personalization, RFPs, Call center replacement (Oct 9, 2023) | Oct 9, 2023
What I learned in using AI for planning and prioritization: Content strategy might be safe from automation | Oct 6, 2023
Open-source contribution myths, Hiring poets to train LLMs, Problems with 'content', AI agents (Oct 6, 2023) | Oct 5, 2023
Embracing professional redefinition | Oct 3, 2023
Documentation failures, Bestiaries, AI Explain post mortem, Inside TechComm podcast (Oct 3, 2023) | Oct 2, 2023
New article: AI and APIs: What works, what doesn't | Sep 28, 2023
Claude versus ChatGPT -- and a few thoughts on using AI chatbots on an Alaskan cruise | Sep 18, 2023
Alphadoc: Build API documentation that tells your API's story | Sep 17, 2023
New API course topic: Using AI for summaries | Sep 7, 2023
Links from around the web (Sept 5, 2023) | Sep 5, 2023
New API doc course topic: Using AI for glossary definitions | Sep 4, 2023
New API doc course topic: Using AI for comparison tasks with API responses | Aug 28, 2023
New API doc course topic: Using AI For thematic analysis | Aug 28, 2023
New API doc course topic: Using AI for language advice | Aug 9, 2023
New API doc course topic: Using AI to create doc updates based on bugs | Aug 9, 2023
New API doc course topic: Using AI to learn coding | Jul 25, 2023
New topic in API course: Using AI tools to write build and publish scripts | Jul 19, 2023
New topic in API doc course: AI document engineering with pattern-based prompts | Jul 6, 2023
First Look at Oxygen XML's Positron AI Assistant [API doc course] | Jul 4, 2023
Adding a new AI section to my API doc course | Jul 4, 2023
First look at the Oxygen XML's AI Positron Assistant | Jul 4, 2023
Doctave Q&A with Niklas Begley | Jun 8, 2023
News turns the content wheel of advertising | May 19, 2023
Newsletter: Endless news cycles, style checkers, finding research, noticing things around you | May 19, 2023
AI starting to diminish work for student essay ghostwriters | May 19, 2023
Newsletter: Copilot for Docs, Wappalyzer, Illusions, Late projects, Forbidden Fruit | May 11, 2023
Newsletter: Doctave, Chatbase, SiteGPT, small CLs, TC bibliography | May 9, 2023
What’s missing from the AI workflow: incentives for content creators to provide training data | May 4, 2023
Newsletter: Content creator ROI, Netlify, Madbot, and Hollywood | May 4, 2023
Newsletter: AI doc alerts, state of tools, saying easy or just, automated writing teams | May 2, 2023
Newsletter: Docusaurus, Lens, Docs-as-Code, 2022 site analytics, and HTML Table formatting | Apr 27, 2023
Meandering thoughts on my 2022 site analytics | Apr 23, 2023
Markprompt Q&A with Michael Fester | Apr 23, 2023
Newsletter: Alphadoc, vocab lookup, field, Open Assistant, Markprompt, content ops | Apr 20, 2023
Newsletter: GPT-4 tutors, Phind.com, Dark user manuals, interfaces for reading docs, automation scripts, and bball | Apr 17, 2023
AI chat interfaces could become the primary user interface to read documentation | Apr 17, 2023
Using AI tools to look up words and provide mini-poems to help remember their meaning | Apr 16, 2023
A script that creates a new Jekyll post and populates it with YAML frontmatter, and also makes a curl call to add a Rebrandly shortlink | Apr 16, 2023
Newsletter: AI and tech comm survey results, Zoomin's predictions, Beating an ATS, ChatGPT plugin docs | Apr 11, 2023
Survey results: Technical writers on AI | Apr 10, 2023
Newsletter: Why engineers need to write, tech writers in pop culture, 101 subreddit, Cambrian period of AI (April 4, 2023) | Apr 4, 2023
Survey on the impact of AI on tech comm | Apr 3, 2023
The influence of language-generative AI tools on tech comm: parlor tricks or disruption? | Mar 13, 2023
Thoughts on ChatGPT after reading Crawford's Why We Drive: whatever skill you outsource, atrophies | Dec 11, 2022
Having fun with ChatGPT | Dec 7, 2022
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.