this post was submitted on 25 Oct 2026
360 points (95.0% liked)

Programmer Humor

33809 readers
2463 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 3 years ago
MODERATORS
 

Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.

top 50 comments
sorted by: hot top controversial new old
[–] Sanctus@anarchist.nexus 1 points 3 minutes ago

I like local LLMs. I got to try one recently and it felt different using open ones than corporate ones.

[–] Scrogu@lemmy.zip 1 points 9 minutes ago

Object oriented programming is dogshit.

[–] stingpie@lemmy.world 1 points 21 minutes ago* (last edited 20 minutes ago)

This is gonna make me sound crazy, but always pass functions when possible, and use case statements for how the passed-in functions are applied.

As a simple example, imagine you want to take the average of a set of numbers. Instead of doing sum(numbers)/len(numbers), do:

Quotient_reduce(sum, lambda x,y: x+1, numbers)

then, inside the definition of quotient_reduce,

Def quotient_reduce(accumulate_by, normalize_by, list):

If accumulate_by==sum and normalize_by==(lambda x,y:x+1):

  return [some efficient implementation of average]

Else:

  Return reduce(accumulate_by, list)/reduce(normalize_by, list)

I know it must look insane, but it generalizes normalization, mean, geometric mean, etc, and on the outside there's no taste of the horrible concrete implementation!

Apologies about formatting, I'm on my phone.

[–] NocturnalMorning@lemmy.world 2 points 55 minutes ago* (last edited 27 minutes ago)

I just got out of an interview where they pretty much told me they will ask me to vibe coded the tool they're working on. LLMs do not make your code faster, and you are not more productive using it. I will never change my mind. We coded for 70+ years without it. You're gonna end up with some subtle hard to reproduce bugs that are intermittently reproducible, and code that is nearly unmaintainable, and nobody knows what it does or how it works.

Good luck with that.

[–] JackbyDev@programming.dev 12 points 3 hours ago (1 children)

I've talked about it before, but I really hate PDFs. Specifically the things PDFs are used for. If you aren't planning to print something and will only ever look at it on a screen, HTML is better. It's so frustrating when you're going to a website, you know, a thing that serves content in HTML, and then some piece of information is in a PDF.

[–] thevoidzero@lemmy.world 2 points 1 hour ago (1 children)

If you're sharing graphical elements then I prefer pdfs when you know it's final, and you want to make sure people see it how you intended, and you want it to be vector format. Similar thing if the information is some complex format/layout. People can zoom in instead of having their device messing it up.

But I agree on simple contents like documents, tables, and such

[–] iglou@programming.dev 1 points 19 minutes ago* (last edited 18 minutes ago)

A PDF file being "final", displaying the same everywhere, and being reliable is a myth.

I have never worked with a messier file format, and I have seen many PDFs displaying in as many ways as I have applications able to view PDFs.

[–] PokerChips@programming.dev 8 points 6 hours ago (1 children)

Linux should be forked at a pre-ai date.

[–] explodicle@sh.itjust.works 3 points 6 hours ago (1 children)

I've got good news for you!

[–] PokerChips@programming.dev 1 points 17 minutes ago

Ha! Well, by a solid group of committed lead devs I guess is my point.

Who's coming with me!?

load more comments
view more: next ›