Writing Better Documentation with AI Assistance: Clarity, Consistency, and Speed
I came back to this project after a year and couldn't remember what was broken. The docs I wish I'd had, and how AI helps write them.
Notes from someone building real things with AI, code and no-code tools.
In one year away, my framework jumped two major versions and my AI model was retired. How I try to stay current now, without reading everything.
I came back to this project after a year and couldn't remember what was broken. The docs I wish I'd had, and how AI helps write them.
The same kind of tool that wrote this blog's bugs also found them. The difference was the question I asked.
AI is great at the boring 80%. The trick is knowing which 20% you shouldn't hand over.
My prompts used to be 'still not working, fix it'. Here's the template I use now, and a real before and after.
AI made writing code cheap. Knowing what to build, and noticing when it's wrong, is still on us.
When an AI assistant changes ten files at once, Git is how you see what happened and how you go back. Plus what my own commit history taught me.
$ ls ./posts | wc -l → 12
View all posts