If you take the time to read the code and understand it to that level, great. But that sort of belies the promise of vibe-coding, where all software engineers essentially become PMs to a bunch of agents.
I use AI to extract information from documentation and write me bespoke examples, but I'd never feel good relying on code it actually generated without extremely thorough testing and review.
> If you take the time to read the code and understand it to that level, great. But that sort of belies the promise of vibe-coding, where all software engineers essentially become PMs to a bunch of agents.
But why would I do vibe coding? I am releasing this code to production systems that will bring the company down if there is a significant error. And my human peers will give me hell for raising terrible code for review.
I have a helpful, endlessly patient junior engineer with superhuman typing speed who will take all of my advice and apply it exactly as a I want it, and write my code for me. When I see errors, I'll tell it, and I'll even ask it to remember why it is a problem in our code base (maybe not others). So it has memory and (mostly) won't do that again.
And I also make sure to apply the same quality to the tests we write together.
Over the last few months I'd say between 50-80% of code being delivered to our repo is "typed" by agents. Humans are still guiding them and ensuring the quality meets our high standards.
I don't really have a grasp on how other people are working with this stuff that they're seeing problems with production code.
I use AI to extract information from documentation and write me bespoke examples, but I'd never feel good relying on code it actually generated without extremely thorough testing and review.