What’s going to happen is the following:

1. Developer needs to document $foo.
2. Developer puts “generate the documentation for $foo” into Claude Code.
3. Claude Code output sounds reasonable, but it refers to stuff that does not exist.
4. [Optional] Developer lazily submits the documentation without reading. Then others start complaining about the documentation being wrong.
5. Developer reviews documentation and notices it’s all bullshit.
6. Developer spends more time fixing the slop outputted by Claude Code than it would take to write it from the scratch.
7. Developer needs to document $bar.
8. Developer asks someone else to do it, because they’re no masochist and they don’t want to go through step 6 again. Tech writer is back.

Try it yourself // Generate documentation, answer codebase questions, and onboard teammates - all from your phone. Kibbler gives you Claude Code access from anywhere.

Oh look, vested interest on making you believe tech writers are becoming obsolete. *yawn*

Ensure PRs have accurate Doxygen before approving merges. That also keeps API documentation accurate, and doesn’t slurp millions of litres of water or megawatts of power. Sheesh.

Good documentation also doesn’t just explain the ‘what’, but the why where it’s important. I doubt any “AI” will do that effectively.