I think the issue is deeper than prompts, agents.md, smart flows, etc. I think the problem is that LLMs are searchers, trained on preferring some results. So, if the dumb solution is there, and the smart solution is not there, they won't spit it out.
To elaborate: That advice isn’t as objective as you think.
What one developer calls clean the other calls messy.
My advice is to use it, then document the issues when it gets messy. It takes some time, but no more than recruiting, training, paying another engineer.
I was gonna say it's a difference between producing something to make money, and producing something meant for people to like and perhaps love, but same thing :)
> This was bad enough that Node.js eventually changed unhandled rejections from a warning to a process crash, and browsers added unhandledrejection events. A feature designed to improve error handling managed to create an entirely new class of silent failures that didn’t exist with callbacks.
reply