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.
I know it's not the same as code, but it is similarly exhausting
The teammate would just use AI to write even more slop to address your "review".. thus exacerbating the problem.
The leadership would indeed be upset to find out you are wasting time doing "pointless reviews".
From their POV, if it passes basic QA, it goes to production.
Similar to how TSA puts fake bomb packages once in a while to see if security catches it or if they just aren’t paying attention.
Sadly, businesses tend to be uninterested in anti-progress, especially if it's hard to quantify the cost of poor reviews.
They're basically the lords of their subsystems. If something does not fit the project's vision and their own standard, it's unlikely to get merged. Imagine if you had the authority to dismiss PRs the same way and send the author back to the drawing board? But that's unlikely to happen as you'll be seen as a "bottleneck" by your managers.
It can because to actually write the code, you need to be good at formal logic and attuned to the sequential nature of the machine. Some people are good at it intuitively. Some brings it over from some other domain. But some people have a lot of difficulty grasping such abstraction. They know the elements, they just can't order them in a logical manner. That's why you often see horrible code (the long function, the god class, magic number) and copy-pasted snippets all over the place. The computer don't care (they made it work somehow), but it's unmaintainable code.
I tend to find it does not. Partly steered by by agents.md, partly by the surrounding context of a clean codebase I suppose.
I think that why everyone agrees that taste matters. Because taste implies judgement and knowledge about what’s good. It’s a self correcting mechanism. But people that won’t judge their output and/or don’t strive to do a good job is a recipe for sloppy work.
I would guess you work for a larger company. My experience is more that someone had an idea or got a short description of a problem and then went off and asked Claude to help write the spec before letting Claude implement that spec. The code is starting to be good but often it is way to much code and some times for bugs it is fixing the symptom not the underlying problem. I have several times rejected PRs with, this isn't fixing the actual problem or instead of these 400 lines you could change that one parameter to the existing function and get a better result.
/end rant and back to another day with code review of AI code
The acceptance for wasting work, or hurting someone's ego was always much lower than the acceptance for bad code that does the job right.
Now I can just say "Let's try doing this in two other ways, and pick the best, because this has such and such drawbacks". And it's so nice that this isn't a) causing a massive amount of extra work b) hurting someone's ego. So it's accepted.
So that's why I'm cautiously optimistic that LLMs and very superficial reviews can still be beneficial to quality. We just didn't reject/rewrite PRs before, now we do.
We're talking months here, not years. That isn't "slowly".
> And the better the AI code gets
It doesn’t really get better. Since Opus 4.6, it’s maybe slightly better for code.
But getting there was a frightening ride. My experience went from "copilot can't do more than tab-completing a few lines" to "early codex gives up and apologizes on mid sized changes" to "Claude can write your entire project without getting stuck".
Your goal should be to automate and remove yourself out of the process as much as possible while maintaining quality, while also remaining confident that you will still be valuable.
I'm working on a setup which will allow non-software developers to develop software in a manner that can be pushed safely to production on our architecture. Not because it's a good idea but because it's what top management wants to happen. We've seen a massive influx of tools developed inside our office by 100% vibe code and no reasonable security or scalability, but because they run on someones computer and they do geniunly useful stuff, management wants to use it.
With how AI is evolving in enterprise you can do more and more for these non-developers because you can set their agents up to write code toward arcitecture without their person knowing anything about tech.
I'm quite sure it'll eventually lead to us letting go of any real software engineers, because they are slow. I'm also sure it'll fail spectacularly in a few years. It's already sort of failing. You can have someone spend €10000 in a month writing a heap of shit that does some good stuff, and then €80000 having consultants actually getting it to run decently in your cloud architecture. Which is stupid, but none of those expenses are in a budget because it's not considered a recurring cost. Unlike someone's salary.
I'm quite sure society on a large scale has no idea the storm that's going to come. Because this isn't just happening in software engineering. It's happening in any white collar profession.
Either I read, understand, and can therefore trust the code.
Or I don't read it, don't fully understand it, and I'm just trusting AI to get it right, but have no way to know if it has done.
So far I'm in Column A and it's working well. We're going much faster than we used to.
My usually solution is just to get AI to review it and bring me a list of things to remove. But yeah it's still decisions that you have to make.
Who cares about your happiness and well-being? You're just a worker, just be grateful to your master that he allows you to work for the shareholders.