vibe coders discover "coding"
-
That's basically the logic for malpraxis, so this will end with the vibe code using companies (or small owners) being sued.
And I am gonna laugh and laugh and laugh.
-
I did see a job post for a role that was just reviewing AI code. This is all terrible
-
I did see a job post for a role that was just reviewing AI code. This is all terrible
So this is real not satire? I once also thought the whole flat earth thing is satire but unfortunately it's not
-
wrote on last edited by [email protected]
There really is no greater pleasure and no greater value adding activity for a Senior Dev than to wade through masses of code produced by pretty much understanding-free copy & paste from stackoverflow by an automated version of the most junior and clueless coder imaginable.
-
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!
-
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.
-
This is your brain on marketing
-
So, if you worked on it first, do you get a discount for watching and helping, because it doesn't add up?
-
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.
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.
Like every function was written by a different guy almost.
Considering how LLMs work, you might be right.
-
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.
Yeah god that sounds like a nightmare.
-
wrote on last edited by [email protected]
Now go a bit further and ask yourself why you should be replicating humans at all when you can just use humans.
-
So, if you worked on it first, do you get a discount for watching and helping, because it doesn't add up?
This is software engineering and apply basic of statement logic, the hourly rate is the last if statement that was true.
Personally, I make it acccumlate the rate for a max rate of $520 when all if statements match.
-
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.
-
If you vibe coded it, 300/hr
-
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.
nightmare territory that.
-
With all the reasoning thrown around, I’m wondering why the fuck such an advanced system would write JavaScript and not directly machine code.
-
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.
I wonder if this stuff is really worse than the software I write.
-
That's basically the logic for malpraxis, so this will end with the vibe code using companies (or small owners) being sued.
That tracks so well that I'm sure it will happen.
Meta, Microsoft, and Google will still be worth trillions, Nvidia will be worth as much as all of them combined, and an entire wave of entrepreneurs taught to be dependent on these behemoths will be ruined.
Sounds like the system is working as designed better than ever.
