this post was submitted on 25 Jul 2024
384 points (98.5% liked)

Programmer Humor

36950 readers
304 users here now

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

Rules:

founded 5 years ago
MODERATORS
 
all 14 comments
sorted by: hot top controversial new old
[–] Australis13@fedia.io 48 points 11 months ago (3 children)

As someone who has inherited code like that, I would like to strangle the first programmer in the comic.

[–] Clent@lemmy.world 41 points 11 months ago (2 children)

"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live."

[–] Telorand@reddthat.com 9 points 11 months ago

The use of "would have" instead of "will have" is making my eye twitch...

[–] Alexstarfire@lemmy.world 1 points 6 months ago

I know him, for he is me.

[–] marcie@lemmy.ml 2 points 11 months ago* (last edited 11 months ago)

you should thank them for the long term employment

[–] LarkinDePark@lemmygrad.ml 2 points 11 months ago (1 children)

Do you own the company or something?

[–] Australis13@fedia.io 1 points 11 months ago

Nope, just inherited a colleague's codebase when they left. It's years later and I still haven't sorted it all out.

[–] ironhydroxide@sh.itjust.works 11 points 11 months ago (1 children)

This is my workplace, but with literally everything, not just code.

[–] Prox@lemmy.world 7 points 11 months ago (1 children)

Capitalism 101

Gotta make that line go up TODAY

Making it go up tomorrow is the next guy's problem

[–] Lifter@discuss.tchncs.de 2 points 11 months ago

It's actually the company's problem. They usually opt to add more debt though, rather that wade through the old stuff.

In the end, all software sucks and should be replaced as soon as possible. Code quality is a lie we tell ourselves so that we can sometimes be proud of our work. It's usually the code we are most proud of that is the worst. Design patterns everywhere making the vode overly convoluted and "future proof". The only future proofing that happens is that no-one will understand it, so they won't change it. Trying to design for the future usually makes it harder in the future.

[–] deathmetal27@lemmy.world 9 points 11 months ago

Technical debt

[–] lowleveldata@programming.dev 8 points 11 months ago

Don't worry I'd post the code on linkedin and credit your profile

[–] chicken@lemmy.dbzer0.com 3 points 11 months ago

The company being successful probably wasn't doing humanity any favors anyway