"This thing works terribly."
"Well... it was vibe coded."
"Ah, that explains it."
I hear conversations like this more and more often. The funny part is that as soon as someone says a feature was "vibe coded," expectations immediately drop. At least among developers 😃.
But that raises an interesting question: who is actually responsible for that feature being released?
The answer hasn't changed. It's still the teamlead or techlead.
And here's what we actually have:
On one hand, we can generate much more code, and naturally the business expects features to be delivered faster and cheaper.
On the other hand, we now have much more code to review and many more bugs to catch.
Yes, agents can review code too (just look at how many articles have been written about it).
But here's a simple question:
Would you personally sign off on these changes?
What if it's a B2B product with contractual penalties?
Or a mission-critical system in aviation or healthcare?
For now, code review is one of the main bottlenecks. Developers spend more and more time verifying what the agent generated.
The cognitive load grows. Before, you might have reviewed one feature a day. Now you may need to review five. AI review can help, just like tests, linters, and other engineering practices help.
But today it still doesn't replace human responsibility.
That's why the real challenge is to find the right balance between speed and quality.
And we should measure not only the number of features delivered and development speed, but also the resulting bug rate.
#ai #engineering