this post was submitted on 19 Mar 2026
1117 points (94.9% liked)

Programmer Humor

30560 readers
1016 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] Fatal@piefed.social 35 points 4 days ago (1 children)

Guys, you can laugh at a joke. The AI doesn't win just because someone upvoted a meme. Maintainability of codebases has been a joke for longer than LLMs have been around because there's a lot of truth to it.

Even the most well intentioned design has weaknesses that we didn't see coming. Some of its abstractions are wrong. There are changes to the requirements and feature set that they didn't anticipate. They over engineered other parts that make them more difficult to navigate for no maintainability gain. That's ok. Perfectly maintainable code requires us to be psychics and none of us are.

load more comments (1 replies)
[–] ViatorOmnium@piefed.social 209 points 5 days ago (5 children)

Yes, and so can most experienced developers. In fact unmaintainable human-written code is more often caused by organisational dysfunctions than by lack of individual competence.

[–] Samskara@sh.itjust.works 102 points 5 days ago (1 children)

In my experience there’s usually a confluence of individual and institutional failures.

It usually goes like this.

  1. hotshot developers is hired at company with crappy software
  2. hotshot dev pitches a complete rewrite that will solve all issues
  3. complete rewrite is rejected
  4. hotshot dev shoehorns a new architecture and trendy dependencies into the old codebase
  5. hotshot new dev leaves
  6. software is more complex, inconsistent, and still crappy
[–] ViatorOmnium@piefed.social 21 points 4 days ago* (last edited 4 days ago) (1 children)

That's one of the failure modes, good orgs would have design and review processes to stop it.

There are other classics like arbitrary deadlines, conflicting and shifting requirements and product direction, perverse incentives, etc.

I would even say that the AI craze is a result of the latter.

load more comments (1 replies)
load more comments (4 replies)
[–] SapphironZA@sh.itjust.works 35 points 4 days ago (1 children)

No, so let's vibe unmaintainable code together!

[–] Digit@lemmy.wtf 1 points 2 days ago

Yus [good image]. Use it to assist and expedite learning (mostly by double checking its output, and debugging its code) to get better. Not as a slave to do your work for you.

[–] neukenindekeuken@sh.itjust.works 59 points 4 days ago (5 children)

I mean, yes, absolutely I can. So can my peers. I've been doing this for a long, long time, as have my peers.

The code we produce is many times more readable and maintainable than anything an LLM can produce today.

That doesn't mean LLMs are useless, and it also doesn't mean that we're irreplaceable. It just means this argument isn't very effective.

If you're comparing an LLM to a Junior developer? Then absolutely. Both produce about the same level of maintainable code.

But for Senior/Principal level engineers? I mean this without any humble bragging at all: but we run circles around LLMs from the optimization and maintainability standpoint, and it's not even close.

This may change in the future, but today it is true (and I use all the latest Claude Code models)

[–] SparroHawc@lemmy.zip 20 points 4 days ago (3 children)

The biggest problem with using AI instead of junior developers is that junior developers eventually become senior developers. LLMs .... don't.

load more comments (3 replies)
[–] terabyterex@lemmy.world 21 points 4 days ago (1 children)

sir, this is programmer_humor

load more comments (1 replies)
load more comments (3 replies)
[–] hperrin@lemmy.ca 80 points 5 days ago* (last edited 4 days ago) (4 children)

Pretty sure I can, considering I’m still maintaining a project I originally started in 2009, which is a core component of my email service.

load more comments (4 replies)
[–] grueling_spool@sh.itjust.works 49 points 4 days ago (2 children)

Maybe the real slop was the code we wrote along the way

load more comments (2 replies)
[–] Shady_Shiroe@lemmy.world 34 points 4 days ago (10 children)

I might not be the best, but I can still do a better job than AI

load more comments (10 replies)
[–] Electricd@lemmybefree.net 43 points 5 days ago (1 children)

When that coworker tells you "hah you must have generated this" but you coded this yourself 👀

[–] beejboytyson@lemmy.world 21 points 5 days ago

"You need to try your best" "This was my best...."

[–] GreenBeanMachine@lemmy.world 14 points 4 days ago (1 children)

Yes, but only I can maintain it.

[–] Agent641@lemmy.world 4 points 4 days ago

I can maintain it. But I won't.

[–] Tja@programming.dev 43 points 5 days ago (7 children)

ITT: AI induced dunning-kruger. Everybody can write maintenable code, just somehow it happens that nobody does.

[–] mushroommunk@lemmy.today 50 points 5 days ago (12 children)

Most of the unmaintainable code I've seen is because businesses don't appreciate the need to occasionally refactor/rewrite or do anything to maintain code. They only appreciate piling more on. They'd do away with bug fixing too if they could.

[–] errer@lemmy.world 20 points 5 days ago

This is why AI coding is being pushed so hard. Guess what’s great at piling on at 30x speed? If piling on is all companies appreciate then that’s what they’ll demand.

load more comments (11 replies)
[–] Bieren@lemmy.today 16 points 5 days ago (3 children)

Can I, sure. Do I give af since my company doesn’t care about me as anything other than a number in a spreadsheet, no.

load more comments (3 replies)
load more comments (5 replies)
[–] dfyx@lemmy.helios42.de 44 points 5 days ago

Yes. That's literally the first point in my job description.

[–] Digit@lemmy.wtf 2 points 2 days ago

Yes.

The code I wrote before LLMs was maintainable, because it was concise clean code.

The code I've let LLMS write for me, unless I spend 30x as long telling it to do it right, is a verbose unreadable noisy spray.

[–] 30p87@feddit.org 30 points 5 days ago (1 children)
load more comments (1 replies)
[–] Kolanaki@pawb.social 10 points 4 days ago (1 children)

10 PRINT 'Hello World!'

20 GOTO 10

EZ

[–] sexual_tomato@lemmy.dbzer0.com 7 points 4 days ago* (last edited 4 days ago) (1 children)

Infinite loop and hard coded magic constant; this should have a configurable timeout and a resource file the string is read from so we can internationalize the application. Additionally, the use of a goto with a hard coded line number is a runtime bug waiting to happen after unrelated refactors; it's best to use a looping construct that has more deterministic bounds.

[–] Digit@lemmy.wtf 1 points 2 days ago

*while true gangsign*

[–] BlackRoseAmongThorns@slrpnk.net 28 points 5 days ago
[–] GreenKnight23@lemmy.world 13 points 4 days ago

yes. yes I can. been doing it for 25 years.

[–] Carighan@piefed.world 18 points 4 days ago (1 children)

I could.

I choose not to! Take that, LLM!

load more comments (1 replies)
[–] Susaga@sh.itjust.works 21 points 5 days ago (1 children)

Why would you tell on yourself like this?

load more comments (1 replies)
[–] SpaceNoodle@lemmy.world 21 points 5 days ago
[–] Electricd@lemmybefree.net 15 points 5 days ago (3 children)

More maintainable that whatever shit it put out

Frankly I believe it can be maintainable if the person doing the prompting actually does something and correctly do their role of human reviewing and correcting. Vibe coding without any review is dooming the software maintainability

[–] Ephera@lemmy.ml 10 points 4 days ago

In my experience, the biggest problem is that maintainable code necessarily requires extending/adapting existing structures rather than just slapping a feature onto the side.

And if we're not just talking boilerplate, then this necessarily requires understanding the existing logic, which problems it solves, and how you can mold it to continue to solve those problems, while also solving the new problem.

For that, you can't just review the code afterwards. You have to do the understanding yourself.
And once you have a clear understanding, it's likely that the actual code change is rather trivial. At least more trivial than trying to convey your precise understanding to an LLM/intern/etc..

load more comments (2 replies)
[–] Digit@lemmy.wtf 1 points 2 days ago

Evasive deflection.

[–] SalamenceFury@piefed.social 12 points 4 days ago

I'm ass at coding and I still can, lmao

[–] apotheotic@beehaw.org 14 points 5 days ago
[–] kubica@fedia.io 14 points 5 days ago

This attack must go against the laws of robotics.

[–] luciferofastora@feddit.org 12 points 5 days ago

I can produce NI-slop on my own. I don't need AI to do it for me.

[–] ICastFist@programming.dev 12 points 5 days ago

I can maintain any code I write myself, so long as I look at it at least once every month

[–] aMockTie@piefed.world 12 points 5 days ago

I would like to think that I'm capable of writing maintainable code like seemingly everyone else in this thread, and I have multiple code bases that have existed for decades that have included necessary updates over time to reinforce that opinion.

I've also seen some truly unfathomable, Lovecraftian horror code in the wild that has persisted for decades.

Seeing Will Smith's character as a representative of humanity, and Sonny as a representative of LLM/GenAI in that context makes this joke absolutely hilarious.

[–] savvywolf@pawb.social 10 points 5 days ago (1 children)

You don't have to outrun the bear, you just have to outrun the other guy.

I think most devs here can out-maintainable-code an llm.

load more comments (1 replies)
load more comments
view more: next ›