[anon7000]

It’s easy to produce a high volume of code, sure, but it is not equally easy to test, verify, and integrate it. And with a high volume of code, there is a high volume of shit to review & test & integrate. For companies that give a shit about not vibe coding their way into a disaster (because they have lucrative enterprise contracts that depend on reliability & security), that’s the real blocker. (Plus, these types of projects are big, not trivial, and things are harder to integrate & properly test because of that.)

Not to mention, if a team wants to keep a semblance of understanding of what they own & ship… it can be exhausting to have a huge volume of new code coming into the system.

It’s definitely a productivity unlock. For sure. But there are a lot of knock-on effects we’re still figuring out that counteract how much extra “value” we’re shipping

[xlbuttplug2]

In my case, the volume of code is roughly the same. I'm not using the efficiency towards pumping out more code, just using it to be AFK more.

I spend enough time iterating and refining to the point I'm comfortable taking ownership of the outputted code. Perhaps hypocritically, I do mald when people upload code for review that they clearly haven't taken the effort to read through critically.

[KellyCriterion]

Well, but AI also helps by writing good comments & docs :-) (one thing Im usually very brief)