I don't really disagree with anything in this post, but the advice is so basic it could have easily been written by an LLM, and apologies for my jadedness but I've seen like a million other posts with the same advice. The advice is simply:

1. Write detailed prompts.

2. Don't trust generated code output - it must be thoroughly reviewed, and feedback should be given back to the LLM.

3. AIs are very helpful for those learning new architectural patterns.

4. Try different tools.

If you really want to learn about using AI to write code (including the pros and cons), I think this post, https://news.ycombinator.com/item?id=44159166, is excellent. Note the author of the Cloudflare OAuth component, kentonv, makes a lot of good, insightful comments in that thread IMO.

I get that a lot of folks wouldn't want to keep a log, but it makes me so sad that the wonderful aider 'ai peer' recommends adding aider logs of all sorts to the gitignore on startup. This feels bad for humans, and bad for AI sense-making too. If you are having this dialog, of course you'd want to be able to reflect on that, I'd think.

It'd be neat to go further. Keeping the agent instructions alongside engineering docs feels like it makes sense. It'd be neat to see what one could do with Backstage like integration, to build out this existing wonderful corporate knowledge-base.

Are there MCP servers yet that can reflect on chat history? Now I want to see a Backstage MCP server even more, one that's extensible by the many Backstage plugins!

Shout out to Kenton Varda & cloudflare doing a nice job making a good commit history of AI use on this project where Kenton was testing the waters. I'm not sure what other good write ups we have for enshrining & promoting the agent instructions as good reference material. https://github.com/cloudflare/workers-oauth-provider/ https://news.ycombinator.com/item?id=44159166