- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or # to comment.
So programmers are now basically the equivalent of in-shop publishing house editors, or a better analogy, a script-doctor in the hollywood production scene.
A company vibe-codes something that is cheap and shitty, then has to pay an editor to actually make it usable.
I hate this timeline…just pay the person to create the code in the first place…
to me, vibe coding seems better used to provide a draft of the work so people with actual skills can then do the final work. A draft made with crayons, dogshit and stale beer but draft none the less.
Or you could just describe what you want to someone who knows how to design code stuff and can ask clarifying questions.
Working from scratch is better than a terrible frame.
We used to call vibe coding both “pseudocode” and “flowcharts”.
How’s that the same? Neither is directly executable (though people have tried) and doesn’t create tech debt
Good lord the repost brigade has arrived to lemmy?
Just do your best plumber / car mechanic impression. “Gee, this codebase is really messed up, looks like I need to basically replace everything.”
(“That can’t be true, that’s what every other programmer I showed this to said. Are you all lying?” “No, we’re not lying, this really is a screwed up codebase.”)
This sounds like the GDP meme:
Two programmers are coding in a terminal when they come across a board of scrum tasks.
The first programmer says to the other “I’ll pay you $100 to vibe code that task.” The second programmer takes the $100 and vibe codes the scrum task using their favorite AI.
They continue coding until they come across a code review from the senior dev, rejecting the pull request. The second programmer turns to the first and says “I’ll pay you $100 to clean up that vibe code”. The first programmer takes the $100 and cleans up the vibe code, using actual skill and no AI.
Coding a little more, the first programmer looks at the second and says, “You know, I gave you $100 to vibe code, then you gave me back the same $100 to clean it up. I can’t help but feel like we both just used AI for nothing.”
“That’s not true”, responded the second programmer. “We fed the AI our code so it would be even smarter next time!”
Narrator: it never did and will never get smarter.
Is this some variant of two guys eat shit?
Context:
Two economists are walking in a forest when they Come across a pile of shit.
The first economist says to the other “Ill pay you $100 to eat that pile of shit.” The second economist takes the $100 and eats the pile of shit.
They continue walking until they come across a second pile of shit. The second economist turns to the first and says “l pay you $100 to eat that pile of shit.” The first economist takes the $100 and eats a pile of shit.
Walking a little more, the first economist looks at the second and says, “You know, I gave you $100 to eat shit, then you gave me back the same $100 to eat shit. can’t help but feel like we both just ate shit for nothing.” “That’s not true”, responded the second economist. “We increased the GDP by $200!”
That’s exactly what I was referencing haha, tried to make the analogy work. Might need to smooth out the edges in a few places
Doesn’t work; all commerce does increase the GDP, but coders don’t believe that the AI gets smarter by using it.
How would you make it better?
It’s a good joke but I don’t think it maps too well
Fair
I don’t even want to clean up my own code, let alone the unholy fucking abortion created by an LLM and a Linked In “CEO and founder” working in tandem.
I do enjoy cleaning code a lot.
When I work on shitty code I’m always thinking about how shitty it is and thinking on how a different design would make it much easier.
When you clean the code, you’re implementing that perfect design you were thinking of all that time. And you know from that point on you’ll be thinking less about how shitty the code is.
If your only task is to clean code and you’re not gonna work on that codebase afterwards, it’s not as rewarding though.
You really should.
Cleaning up code is the most important part of development.
Brb, updating my linkedin. I’m dead serious.
vibe code cleanup specialist, so, normal coder who fixes what a pretend coder fucks up? well you thought AI would take your job but now two people can be employed to do what one person was supposed to do without AI.
And each one will take much longer than the original coder too!
Not necessarily; you’re supposed to throw away the prototype
Thank you AI
Yeah sounds like job creation to me.
Jokes on them I’m a vibe code cleanup expert that cleans up with even vibier code.
Infinite money glitch!
“Computer, fix this code and don’t make mistakes.”
Computer fix this code with just enough mistakes that I can charge them to fix it again, just don’t make it obvious.
Friend’s colleague needed Excel to, “return the month where the majority of days in the week fall into”. Had Copilot do it and sent it to my friend, apparently impressed by making such a robust looking formula.
The formula:
My friend’s solution a minute later:
I can see it could be slimmed even less, but I assume the table is large so LET is doing performance stuff.
If you ask copilot to return a directory tree using MATLAB script it writes a function using a for loop and about 20 lines of code. Meanwhile the documentation defines this task as
dir(“*”)
Okay, what is vibe coding? Because it sounds to me like just doing coding based on your feelings or something, which makes absolutely zero sense.
Coding using an LLM and not even reviewing output
Ah. That makes more sense.
Not much more, though
They clean up AI shitty code?
More like, take a bunch of screenshots of vibe coded website, and treat that as design document while rewriting the whole thing from scratch with clean architecture.
Plot twist they just vibe code the v2
If those dummies accepted the vibe code in the first place and you meet your contractual obligations…
tbh, if they were smart and knew what they were doing, they should have done it that way from the beginning, but they want to cut corners. AI is great at rapid prototyping; but it’s not trustworthy enough to call that a finished product.
To be fair, that’s usually the fastest option to fix other people’s code even if it wasn’t vibe coded. Sometimes that’s the best way to fix your own code too.
Not to be nitpicky but those locations are all over the place, lol. I wonder what the actual percentage of programmers need to pivot to slop cleanup duty.
Depending on how royally the hiring party screwed up, there could be a lot of desperate money to be made
From my experience, a whole lot.
Think about how hard it is to join a new company and learn to maintain their codebase - at least in that situation you are likely going to have someone more familiar with it walk you through it.
Now understand that no such resource exists for vibe code - you’re on your own from the get go.
