You must log in or # to comment.
OK, the cynic in me thinks that isn’t a vibe coder typing that, but someone in middle/upper management. They’ve recently fired most of their engineering teams and replaced them with (probably externally contracted at a considerably lower rate) vibe coders.
They’re recognizing some of the problems that were highlighted when this trend started to gain traction and are now thinking of a way where they don’t need to accept being wrong in their actions, but also somehow still profit from it by only using real engineers (probably also on external contracts with shitty conditions) when it’s absolutely required.
Maybe I’m wrong.
god imagine how depressing dev would be if all programmers did was clean up AI slop.
I really don’t think people realize how opaque and circuitous some of this shit is.
It would be like taking your compiled machine code and editing it by hand because your compiler sucks.
Just use the right tool from the start.
An acquaintance of mine has basically been doing this for years in the form of slop code written by the cheapest outsourcing firms on earth who cannot comprehend rudimentary requirements and have no concept of coding standards. But management insists this is the most cost effective way of doing things, rather than just having a competent group of qualified people do it right from the start.
It seems as depressing as you’d think.
In my experience I tried to come into a vibe project as a reviewer, and it felt completely unreadable with no underlying principles to hold on to. Like every function was written by a different guy almost.
Now you totally can stuff the context with instructions about how to do everything. And then add 50x mcps to retrieve documentation and policy about how to write the thing, but this is like cheating on an exam by remembering the answers. You already supplied enough context to write the thing yourself.
Wait… Vibe projects are a real thing? I THOUGHT YOU GUYS WERE JOKING!
