vibe coders discover "coding"
-
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.
-
Oh man, imagine how crazy things will get once management realizes they can stop paying all the vibe coders and just let the expert human coders at it from the start! They can even let them use the leftover AI licenses for shits and giggles.
-
Just create a new AI that's specialized in cleaning up vibe code.
-
If they only knew how to actually do the work, they could just ask it to do it right in the first place.
Make me a page display this data.
Now go back and put all that spaghetti code into reusable functions and use them.
I think it generally tries to take the path of least compute power first saving money on their behalf.
-
next theyll invent rudimentary bartering systems
-
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.
This seems to happen in a lot of IT in general.
Your software, db's and infrastructure ends up a mess, but it's so cheap they can pay 3x the number of people to keep sweeping all of the issues under the rug. -
eminem throwing a book titled "C programming" towards the camera.jpg
-
Wait until they figure out how senior engineers learned all this stuff.
-
Wait until they figure out how senior engineers learned all this stuff.
Uphill both ways in the snow I'm sure
-
Uphill both ways in the snow I'm sure
Actually... yes. This was back when "source control" meant keeping the code on an extra floppy in a dusty desk drawer, and "security" meant throwing an extra lock on the office door, and "looking stuff up" meant trying to find useful books at the local bookstore. It was awful.
-
Like every function was written by a different guy almost.
Considering how LLMs work, you might be right.
Considering how LLMs work, you might be one of them.
