> I am becoming a better architect with AI, because I am spending more mental energy in that lane, getting less embroiled in the nitty-gritty of the code.
I don't believe this, every architect ive ever worked with that was not regularly in the weeds on various things in the codebase were universally terrible and out of touch.
> More people building things is straightforwardly good
No it's not, its the opposite actually its very bad and leads to far far more noise in the system to sort through to find value as someone who's competent.
I am not joking when I say that software craftsmen lost the war when tabs vs spaces was obviated as a point of contention by CI enforced formatting and linting around broader community standards.
Of course I think. I have 20 years of coding experience and knowledge of the codebase and business. That’s why I’m keenly aware of how strange the process is.
What I’d like to know is how you’d train a monkey to read and judge output from an llm on a pull request.
I read this as im "reviewing" a 100% claude generated ten page incident RCA report. It's mostly wrong but bringing that up is not useful so just rubber stamp and move on.
this doesn't really work in the real world. There are many things that actually matter, engineering is fundamentally about handling them.
reply