this post was submitted on 01 Feb 2026
193 points (89.7% liked)

Programmer Humor

29805 readers
1026 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
you are viewing a single comment's thread
view the rest of the comments
[–] bigboismith@lemmy.world 5 points 2 weeks ago (1 children)

Printing to console is often only used for toy code anyway.

[–] silasmariner@programming.dev 7 points 2 weeks ago (3 children)

Wait, how do you debug your code?

[–] Magnum@infosec.pub 2 points 6 days ago (1 children)
[–] silasmariner@programming.dev 1 points 4 days ago (1 children)

Guess you could do that, seems like a pain though

[–] Traister101@lemmy.today 4 points 2 weeks ago (2 children)

A logger? Console prints are shitty in general but especially when you have an actual logger already

[–] SlurpingPus@lemmy.world 9 points 2 weeks ago (1 children)

You know what println never did? Run arbitrary code on my toaster.

[–] Traister101@lemmy.today 1 points 2 weeks ago

Neither did Log4j in basically all cases, some maniac just put arbitrary code callbacks into their logger, undocumented and enabled by default. The insane part isn't the feature itself it's the fact it's enabled by default in a logger of all things.

[–] silasmariner@programming.dev 3 points 2 weeks ago (1 children)

Oh man, I thought that was one of the classic jokes :'( I am out of touch

[–] Traister101@lemmy.today 2 points 2 weeks ago (1 children)

People in my experience are actually very serious about the standard out to debug log which is... baffling. Same people generally outright refuse to learn how to use a debugger in languages where those are pleasant

[–] silasmariner@programming.dev 1 points 2 weeks ago* (last edited 2 weeks ago)

Oh I'm completely serious. The joke is that everyone does it but everyone knows not to do it. I started doing it when I first ran into problems debugging actor contexts, and never stopped.

The good printlns become logs, obviously