Search results

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:

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

Prompt engineering series: Creating scripts to automate doc build processes

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

AI is accelerating my technical writing output, and other observations

Upcoming conference: AI the API docs

Prompt engineering series: Gathering source input

Prompt engineering series: Error checking the output

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

Prompt engineering series: Reverse engineering the recipe for excellent documentation

Prompt engineering series: Populating documentation templates using AI

Prompt engineering: Task decomposition and complex tree diagrams

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

Visualizing APIs with tree diagrams, partly generated with AI

Walking and chatting with ChatGPT

Moved AI pages into their own collection and space

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

My 2024 technical writing trends and predictions

Etto, a new AI co-pilot for Heretto — Q&A with Casey Jordan

Webinar recording: Experiments and use cases for AI from a tech writer’s perspective

30+ ways I’m using AI in everyday writing life as a technical writer, blogger, and curious human

Podcast: The evolution of podcasting, with Ed Marsh

You've heard of 'Docs as code' -- Now get ready for 'Code as docs': Q&A with Speakeasy

Doing research with AI tools -- avoiding the trap of fabricated URLs

My experience trying to write original, full-length human-sounding articles using Claude AI

Chatting about AI trends and tech comm with Fabrizio Ferri Benedetti

[Podcast] AI and APIs: What works, what doesn't

Forrester Report, Coding jobs, Hyper-personalization, RFPs, Call center replacement (Oct 9, 2023)

What I learned in using AI for planning and prioritization: Content strategy might be safe from automation

Open-source contribution myths, Hiring poets to train LLMs, Problems with 'content', AI agents (Oct 6, 2023)

Embracing professional redefinition

Documentation failures, Bestiaries, AI Explain post mortem, Inside TechComm podcast (Oct 3, 2023)

New article: AI and APIs: What works, what doesn't

Claude versus ChatGPT -- and a few thoughts on using AI chatbots on an Alaskan cruise

Alphadoc: Build API documentation that tells your API's story

New API course topic: Using AI for summaries

Links from around the web (Sept 5, 2023)

New API doc course topic: Using AI for glossary definitions

New API doc course topic: Using AI for comparison tasks with API responses

New API doc course topic: Using AI For thematic analysis

New API doc course topic: Using AI for language advice

New API doc course topic: Using AI to create doc updates based on bugs

New API doc course topic: Using AI to learn coding

New topic in API course: Using AI tools to write build and publish scripts

New topic in API doc course: AI document engineering with pattern-based prompts

First Look at Oxygen XML's Positron AI Assistant [API doc course]

Adding a new AI section to my API doc course

First look at the Oxygen XML's AI Positron Assistant

Doctave Q&A with Niklas Begley

News turns the content wheel of advertising

Newsletter: Endless news cycles, style checkers, finding research, noticing things around you

AI starting to diminish work for student essay ghostwriters

Newsletter: Copilot for Docs, Wappalyzer, Illusions, Late projects, Forbidden Fruit

Newsletter: Doctave, Chatbase, SiteGPT, small CLs, TC bibliography

What’s missing from the AI workflow: incentives for content creators to provide training data

Newsletter: Content creator ROI, Netlify, Madbot, and Hollywood

Newsletter: AI doc alerts, state of tools, saying easy or just, automated writing teams

Newsletter: Docusaurus, Lens, Docs-as-Code, 2022 site analytics, and HTML Table formatting

Meandering thoughts on my 2022 site analytics

Markprompt Q&A with Michael Fester

Newsletter: Alphadoc, vocab lookup, field, Open Assistant, Markprompt, content ops

Newsletter: GPT-4 tutors, Phind.com, Dark user manuals, interfaces for reading docs, automation scripts, and bball

AI chat interfaces could become the primary user interface to read documentation

Using AI tools to look up words and provide mini-poems to help remember their meaning

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

Newsletter: AI and tech comm survey results, Zoomin's predictions, Beating an ATS, ChatGPT plugin docs

Survey results: Technical writers on AI

Newsletter: Why engineers need to write, tech writers in pop culture, 101 subreddit, Cambrian period of AI (April 4, 2023)

Survey on the impact of AI on tech comm

The influence of language-generative AI tools on tech comm: parlor tricks or disruption?

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

Having fun with ChatGPT

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.