I would describe myself as pretty AI-positive in software engineering, and even in technical writing, but something about seeing diagrams that are clearly generated by Nano Banana Pro immediately makes me stop reading. Weird!

No. If you cannot keep docs in sync, let the agent keep it in sync. Better keep the docs in the repo, not in a wiki or elsewhere

Another day, another person telling us how we should change what we have been doing for decades, just to make sure the machine can drop 1,000's of lines of debt that we'll never review, or worse yet, a machine will review it.

I guess the hope is that the middle managers will finally be able to get rid of the annoying techies, this time, as has been the promise for decades.

Maybe these LLMs are the silver bullet to finally free us so we can dance, paint, write poetry, and fuck instead of working.

Not that I consider writing code to be work, since it's always been the easy bit for me, but yeah, just as the machines have taken music, art, poetry, etc, why not let them take everything we enjoy.

PS - You'll prise copilot in vsc from my cold dead fingers :-)

Well, maybe I want my docs folder to be useful for humans checking my code and don't care about LLMs at all..

The blog reads like an advertisement for some product that doesn't exist (yet?). It seems rough to store, access and accurately update this context-code mapping

The constant changing of tense in this article makes it very hard to read.

Im from the opinion that not only for AI agents but detailed development docs (ADRs, Specs …) should live alongside each package.

High level and user docs in /docs

I feel like the article either doesn't really contain any information, or is describing the concept of "code comments" after being translated through 35 languages.