804

submitted 1 day ago by cm0002@lemmy.world to c/programmer_humor@programming.dev

58 comments fedilink hide all child comments

top 50 comments

sorted by: hot top controversial new old

[-] AnUnusualRelic@lemmy.world 5 points 10 hours ago

The famous "futur" we were all waiting for.

You may have hear of the future, with flying cars, cities in orbit, everyone living a comfortable life... Like the first steps to the Culture. Not at all. What we have is "the futur". It was born in the US, as so many dubious things are, and will soon spread all over the globe.

[-] squaresinger@lemmy.world 8 points 12 hours ago

A job for a real masochist.

[-] melsaskca@lemmy.ca 21 points 15 hours ago

We used to call vibe coding both "pseudocode" and "flowcharts".

[-] Pyro@programming.dev 4 points 8 hours ago

But those are way more useful than vibe coding.

[-] colourlessidea@sopuli.xyz 6 points 15 hours ago

How’s that the same? Neither is directly executable (though people have tried) and doesn’t create tech debt

[-] Tartas1995@discuss.tchncs.de 6 points 12 hours ago

Flowcharts are where the tech debt starts tbf

[-] Adderbox76@lemmy.ca 12 points 15 hours ago

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....

[-] GamingChairModel@lemmy.world 2 points 9 hours ago

That's kinda always been how technology changes jobs, though, by slowly making the job one of supervising the technology. I'm no longer carving a piece of wood myself, but I'm running the CNC machine by making sure it's doing things properly and has everything it needs to work properly. I'm not physically stabbing the needle through the fabric every time, myself, but I am guiding the sewing machine path on that fabric. I'm not feeding fuel into the oven to maintain a particular temperature, but I am relying on the thermocouple to turn the heating element on and off to maintain the assigned equilibrium that I'll use to bake food.

Many jobs are best done as a team effort between human and machine. Offloading the tedious tasks to the machine so that you can focus on the bigger picture is basically what technology is for. And as technology changes, we need to always be able to recalibrate which tasks are the tedious ones that machines do better, and which are the higher level decisions best left to humans.

[-] Witchfire@lemmy.world 1 points 10 hours ago

I will gladly take up one of these jobs as long as they allow me to trash all generated code and just rewrite it from scratch. It'll be faster than any sort of cleanup.

[-] reksas@sopuli.xyz 14 points 16 hours ago

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.

[-] kamstrup@programming.dev 3 points 10 hours ago

9 times out of 10, this "vibe draft" sends people down a terrible path that they would have never ventured had there been an adult in the room. I swear I review so much code that sets off in the wrong direction because of this, and I am sick of it.

[-] Boo@lemmy.dbzer0.com 14 points 14 hours ago

Working from scratch is better than a terrible frame.

[-] NikkiDimes@lemmy.world 1 points 10 hours ago

I think that's exactly what they're implying. Use it to make a low effort disposable prototype, not scaffolding to expand from.

[-] Boo@lemmy.dbzer0.com 1 points 9 hours ago

But if you get the framing from the terrible prototype/draft, it can lead you into a bad direction. It is like the "Don't think of an Elephant". Once you see the "Elephant" you will struggle not to make something that looks more like an Elephant.

[-] NikkiDimes@lemmy.world 3 points 9 hours ago* (last edited 9 hours ago)

True, but I see it more as a tool for a non-technical person to make a prototype of a user experience more than making a foundation for how a project will actually be built and designed from a code perspective. Like, when it comes to the actual implementation of said project, the developer(s) shouldn't even look at the prototype code. I envision, in this example, as it solely being a tool for non-technical people to express their ideas to the technical side of the operation.

I agree with you though, that still has potential to pollute a project entirely, and we already have methods of creating requirements and documentation for projects so this isn't exactly the most useful thing ever.

[-] Adalast@lemmy.world 1 points 8 hours ago

I made this comment on a previous post. Vibe Coding is to Coding as Previsualization (Previs is to Visual Effects. (Previs description) A quick slap job that is used to make sure timing is correct, on set assets will all work, and to communicate to artists, directors, producers, and on-set operators what is expected. It is entirely separate from the final product and nothing ever crosses the barrier between Preproduction and Production.

[-] umbraroze@slrpnk.net 32 points 18 hours ago

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.")

[-] Resonosity@lemmy.dbzer0.com 65 points 23 hours ago* (last edited 23 hours ago)

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.

[-] AnarchistArtificer@slrpnk.net 7 points 14 hours ago

This is hilarious. I'm deeply sad that I don't think my irl friends would appreciate this joke, because I want to share it with everyone.

(I am personally irked by vibe coding because some assholes in my life have been real smug about how much better of a programmer they are than me due to vibe coding. )

[-] pineapplelover@lemmy.dbzer0.com 66 points 23 hours ago* (last edited 23 hours ago)

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!"

[-] Resonosity@lemmy.dbzer0.com 14 points 17 hours ago

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

[-] pyre@lemmy.world 181 points 1 day ago

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.

[-] marcos@lemmy.world 8 points 22 hours ago

And each one will take much longer than the original coder too!

[-] abbadon420@sh.itjust.works 40 points 1 day ago

Thank you AI

[-] SkunkWorkz@lemmy.world 6 points 17 hours ago

[-] UnrefinedChihuahua@lemmy.dbzer0.com 21 points 1 day ago

Yeah sounds like job creation to me.

[-] Blackmist@feddit.uk 65 points 1 day ago

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.

[-] calcopiritus@lemmy.world 4 points 16 hours ago

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.

[-] msage@programming.dev 4 points 16 hours ago

You really should.

Cleaning up code is the most important part of development.

[-] Gork@sopuli.xyz 123 points 1 day ago

Jokes on them I'm a vibe code cleanup expert that cleans up with even vibier code.

[-] SpaceNoodle@lemmy.world 53 points 1 day ago

Infinite money glitch!

[-] mitch@piefed.mitch.science 26 points 1 day ago

"Computer, fix this code and don't make mistakes."

[-] A7thStone@lemmy.world 5 points 17 hours ago

Computer fix this code with just enough mistakes that I can charge them to fix it again, just don't make it obvious.

[-] vala@lemmy.dbzer0.com 29 points 1 day ago

Brb, updating my linkedin. I'm dead serious.

[-] ekZepp@lemmy.world 76 points 1 day ago

They clean up AI shitty code?

[-] pelya@lemmy.world 120 points 1 day ago

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.

[-] mathemachristian 2 points 16 hours ago

Good lord the repost brigade has arrived to lemmy?

[-] Sneptaur@pawb.social 1 points 10 hours ago

Downvote, move on

[-] mathemachristian 1 points 10 hours ago

Cant from blahaj

[-] drolex@sopuli.xyz 33 points 1 day ago

What a coincidence! I'm a vibe coder cleanup specialist. I clean up after their brains explode from receiving too much vibration from the computer waves (or something, I don't know how it works exactly. I'm just here with my little sponge)

[-] mitch@piefed.mitch.science 4 points 1 day ago

Oh yeah. Don't you guys also do murder scene remediation?

load more comments (2 replies)

[-] Ilovethebomb@sh.itjust.works 28 points 1 day ago

I have to imagine hiring someone who advertises themselves as a vibe code cleanup expert would be a dent to the ego.

[-] towerful@programming.dev 25 points 1 day ago* (last edited 1 day ago)

Yeh, but you only need 10 vibe code cleaner-uppers per vibe coder.
And a vibe coder is a 10x developer.
You just have to mitigate the increased cost of AI API calls.
It pretty much balances out, with the obvious 20% efficiency boost - which is where everyone makes their money: companies, developers and ~~shovel~~ AI platforms... All 20% efficiency boost. Which directly relates to profit boosts. 20% line goes up!
Which also pays for the datacenters, the ~~shovels~~ GPUs, the power, the cooling and the water for the cooling. It's all cheaper, cause AI is at least 20% more productive.

Even if your vibe-coder-code-fixers turn into vibe-coder-code-vibe-fixers... That's just another 20% efficiency boost. Basically printing money! Oh, but you need to buy more ~~shovels~~ GPUs. But that's also a win because ~~shovels~~ GPUs don't have unions or require holidays. Think of the profits! They work 24/7.
And all you need are vibe-coder-code-vibe-fixer-code-fixers.

...As long as your vibe-coder-code-vibe-fixer-code-fixers don't turn into vibe-coder-code-vibe-fixer-code-vibe-fixers (I'm so lost, I think that's right).

Edit: forgot some ~~shovels~~

[-] mitch@piefed.mitch.science 4 points 1 day ago

A paycheck is a paycheck. Lots of us exchange our ego for daily bread — we have a club and everything. We meet every day after work at your local bar.

load more comments (1 replies)

[-] taiyang@lemmy.world 7 points 1 day ago

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.