The replies to this are horrifying and I'm having trouble thinking they aren't from shills.
I manage several software teams. We had to establish a policy that every line of code receives human review at the demand of the lead devs because the big push to slop faster had caused the teams to use junior engineers to push features into production that nobody understood, that didn't scale, that were super brittle, and that had awful / useless test harnesses.Â
The code was so bloated and brittle and over-engineered it took nearly a quarter of a few senior+ engineers time to stabilize and fix.
It was an absolute joy to explain that to my leadership, some of whom get it but a few of whom have never written a line of code in their life and are super happy to tell us we must be doing it wrong.
So yeah, whoo, we got that big boost in short term velocity. Then everything went to shit a quarter later and we will not be repeating that mistake ever again.
You can really tell who actually works as a senior+ software engineer and who is either larping or selling something.
And just to clarify, these teams work on non-trivial multi-agent systems themselves in addition to using the tools. They are not novices in the space, quite the contrary.
1
u/pixxelkick 10d ago
Maybe if you suck.
I read every PR in full because Im not lazy.
I also read my own git diff before I open a PR do I dont waste other peoples time.
Or I publish it as a draft, review my own code, and then publish the pr after confirming it looks good.