I think this is a muscle that grows though. Making decisions about schema changes in the past may have taken weeks, but if you're doing it once or twice a week you gradually gain confidence in your judgment.
Does it really though? Before I had to think hard before committing to a decision, because it took work to actually implement it. And when it turned out to be wrong, I retained how it went wrong. It made the "muscle" grow.
Now I can commit to a decision without much thought (yea, just nodding along with the AI), and if it turns out to be wrong, I can quickly try an alternative. In fact, my boss would want to quickly try an alternative, instead of letting the programmer learn something out of it for fear of slowing down the AI...
So does the decision making muscle really grow?
I think you're right that the scar tissue of a bad decision helps me retain lessons better. But the calculus has changed now and my nervous system is outdated. I should not feel the same fear that I previously felt, because like you said, I can recover from a bad decision more quickly.
As I keep making decisions at a (seemingly) breakneck speed and see that things are still okay, over time my nervous system will readjust.
At least that's my experience so far.
You can leave comments on the code and then get your agent to connect over MCP to read the comments with context and work on corrections.
It then remembers what you have already reviewed and only shows you diffs for the changes.
Still a WIP, but works well for me.
I have a keyboard shortcut that asks what the agents need from me, and the decisions show up in the html with a recommended decision for each problem.
I reason, decide, and then parallel agents run in each terminal, across multiple terminals.
I am ending the day incapable of listening to one more problem or making one more decision, which is very bad for social interactions.
Today I am working on working less and having more impact by leveraging where agents are good.
What I've noticed in recent months is that the people who have been prompting since chatgpt came out are the ones who know what works and what doesn't, and how to scale it. It's like music: if you hit the right notes, it will sound fine.
Ponytail also helped a lot for generating simplified systems.
By the way, this process is for mature systems. Building from the ground up is more about designing and checking each model decision, basically finding smarter paths to each problems.
I can't leave it all alone; the overengineered decisions are plentiful and make the system brittle when it's not needed.
Lots of unit and live tests help a lot too, especially when you can coordinate live tests with another omp session.
I'm interested in what the next capabilities will be. I feel all this overengineering is more of a shortest path problem, ready to be solved
Jokes aside, I hear you.