this post was submitted on 10 Mar 2026
247 points (98.8% liked)

Programmer Humor

41333 readers
79 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 6 years ago
MODERATORS
 

idk if it is serious or not, but it is what I saw in indeed newsletter today.

top 50 comments
sorted by: hot top controversial new old
[–] iByteABit@lemmy.ml 4 points 8 hours ago

Knowing how to code is now "syntax heavy"

god I hate this world

[–] WorldsDumbestMan@lemmy.today 5 points 17 hours ago (1 children)

I will sign up! I have no fucking idea how vibe coding works, which makes me perfect!

[–] Birch@sh.itjust.works 4 points 17 hours ago

That's the beauty of it, just ask chatgpt or copilot how to do it, then learn by fixing all their mistakes. Until my company decided to become "AI first" I barely ever touched Python, I still barely know Python, but I now know to spot indentation errors and hallucinated function calls.

[–] garretble@lemmy.world 15 points 1 day ago (1 children)

So I ran into my first genAI coding junk yesterday when I was on a call with my boss and as a solution to a problem we were talking he said, "hold on let me ask Gemini."

I felt my soul die a little bit at that point.

But the fun part is that Gemini first didn't provide a good answer.

And then on the second go it also didn't provide a good answer.

And then on the third attempt we decided to table the issue for the moment because prompt coding on a call was taking longer than I think he expected.

I really disliked that experience.

[–] CanadaPlus 6 points 19 hours ago

Hmm, was the boss hoping to turn that into a "why do I even pay you" moment?

[–] Nemoder@lemmy.ml 16 points 1 day ago (1 children)

You know the "vibes" of different models - when to use

Would that be a vibe-rater?

[–] tracyspcy@lemmy.ml 6 points 1 day ago (1 children)
[–] racketlauncher831@lemmy.ml 3 points 18 hours ago

Say it. Say the words.

[–] quixote84@midwest.social 2 points 18 hours ago

The words are all still stupid because it's a new thing, but there is one specific space that I find it just impossible to deny the way that there are already tools on the market that change the way the job is done:

Claude can turn plain english statements about what data I want from what different parts of the Microsoft 365 administration ecosphere into scripts that take all that data, transform it the way I want it transformed, and turn it into spreadsheets, pivot tables, data manipulation macros, and everything else I need to answer questions which are really hard to answer from the MS web interface. I can ask things like "Which systems have any of these three known vulnerable apps?" or "What software is common to everyone working in this division of the company?"

It's boring stuff, but it makes a world of difference in terms of what I can look at to base my decisions on. I spent less time building repeatable reports for each type of object I need to think about (device, application, user) than I did building even one report for one assessment in years past without automation. And it's not constantly asking the LLM to do things for me, it's building a couple of tools with a much faster iterative process for feature tweaks or debugging than could take place as an interaction between two people. I was making changes to scripts

I'm using it only for specific work areas where I already know the APIs I just don't have the time to stumble through the gather and collate of the various data. Based on the level of complexity of the tools I've been able to build I would say that anybody who knows how to describe the data they work with most could use a tool like this to make that process a lot more automatic. We're not ready for the tool to do the work without human oversight, but we're ready for anybody who works with stacks of data to build their own automation instead of having it built for them.

[–] MrOxiMoron@lemmy.world 20 points 1 day ago (1 children)

10x the speed, sweet. So 10x the salary too right?

[–] tracyspcy@lemmy.ml 17 points 1 day ago

Vibe salary

[–] umbrella@lemmy.ml 78 points 2 days ago (3 children)

programming was never about how fast you could type. the person who wrote this knows nothing about the job.

[–] anon_8675309@lemmy.world 8 points 1 day ago (2 children)

And yet somehow the tech blogs and such always scream about developer productivity. Go faster. Go faster.

From what I’ve seen over the years, only mids care about finishing fast.

[–] sakuraba@lemmy.ml 1 points 3 hours ago

I would never trust anything a tech blog's opinion piece says blindly

[–] CanadaPlus 3 points 19 hours ago* (last edited 19 hours ago)

Yes, but quality takes actual skill to measure, instead of just a diff.

(Although I guess lines are still better than time in office)

[–] tracyspcy@lemmy.ml 30 points 2 days ago

the description is gold, everyone can find something wrong about it.

[–] corsicanguppy@lemmy.ca 3 points 1 day ago

The guy who wrote this is an idiot, but he became so in a world where "LoC" is a metric -- one that Goodhart would love, but alas.

This is honestly the road to hell and the ~good intentions in one.

[–] UnderpantsWeevil@lemmy.world 80 points 2 days ago (5 children)

Amazed they didn't ask for 5-10 years of experience in AI coding.

[–] Venator@lemmy.nz 2 points 1 day ago

You could have that, would just have to be experience writing code for AI, rather than vice versa...

[–] tracyspcy@lemmy.ml 31 points 2 days ago

wait for it! PHD in vibe coding or relevant experience

load more comments (3 replies)
[–] AdamBomb 52 points 2 days ago (2 children)

natural language is the new programming language

lol. Lmao.

[–] kibiz0r@midwest.social 44 points 2 days ago* (last edited 2 days ago) (4 children)

Dijkstra on the foolishness of natural language programming

But like, what does he know? He wasn’t an AI-native vibe orchestrator.

[–] CanadaPlus 4 points 18 hours ago* (last edited 18 hours ago)

And even this improvement wasn't universally appreciated: some people found error messages they couldn't ignore more annoying than wrong results, and, when judging the relative merits of programming languages, some still seem to equate "the ease of programming" with the ease of making undetected mistakes.

This guy was writing in the year x86 was first introduced, and I still feel like I see this attitude around.

(He manages to shoehorn in a "kids these days" paragraph too, though)

[–] T156@lemmy.world 5 points 1 day ago

All he made was some dinky algorithm. Google Bard could do that in three minutes flat smh.

[–] tracyspcy@lemmy.ml 10 points 2 days ago

Thx for sharing this . Really hope people read it.

load more comments (1 replies)
[–] tracyspcy@lemmy.ml 12 points 2 days ago

“English is the new programming language” would be more punchy

[–] unmagical@lemmy.ml 66 points 2 days ago (4 children)

Spot security vulnerabilities instantly from a candidate that can't actually write code.

[–] GameOverFlow@lemmy.zip 4 points 1 day ago

Just ask the ai to make no failures. Just aks the Ai to eliminate all failures. Easy 10 000 dollar per year. 

load more comments (3 replies)
[–] saltnotsugar@lemmy.world 57 points 2 days ago (4 children)

I need to hire someone to take this functional 15 lines code, and like make it 200 lines of unusable madness.

[–] tracyspcy@lemmy.ml 37 points 2 days ago

But fast! Very fast

load more comments (3 replies)
[–] Sxan@piefed.zip 26 points 2 days ago (5 children)

We did it to ourselves. Developing mission-critical systems in scripting languages and always sacrificing quality for delivery. Fast and sloppy paid þe bills, but we were digging our own graves. Once industry became used to sloppy software, a relatively mild shift to even more crappy, but far cheaper and more immediate software was a no-brainer. Customers haave gotten used to shitty, buggy software. It doesn't matter to þem who's writing it.

[–] avidamoeba@lemmy.ca 23 points 2 days ago (5 children)

The only way for us to not "do this to ourselves" is to form unions. Otherwise we aren't driving the decisions on what is used and what's prioritized at all.

load more comments (5 replies)
[–] MeetMeAtTheMovies@hexbear.net 10 points 2 days ago (1 children)

I wrote an app for my wife and it was really sad watching her just fumble past bugs instead of pointing them out when I was literally watching over her shoulder to get feedback on what needed fixed. I had to tell her several times, “No, don’t just keep reloading. What’s wrong?” Like we’ve all been trained so hard to accept shitty software that even when I could fix stuff easily I know people are just passively accepting the bugs.

[–] MangoCats@feddit.it 7 points 1 day ago

One of my junior devs was having trouble with a bug in an internally developed tool, apparently for weeks before I saw her struggling with it over her shoulder - it was a 5 minute fix, I hope I made it clear to her: speak up when something's wrong - this 5 minute fix has cost you many hours already because you never told me you were having a problem.

load more comments (3 replies)
[–] thedeadwalking4242@lemmy.world 17 points 2 days ago

Fucking idiots. I'm surrounded by idiots

[–] tracyspcy@lemmy.ml 18 points 2 days ago (1 children)

im curious if they have live "vibe coding" session during hiring process

load more comments (1 replies)
[–] weissbinder@feddit.org 18 points 2 days ago (1 children)
load more comments (1 replies)
load more comments
view more: next ›