1143
submitted 2 months ago* (last edited 2 months ago) by Ek-Hou-Van-Braai@piefed.social to c/programmer_humor@programming.dev
you are viewing a single comment's thread
view the rest of the comments
[-] Samskara@sh.itjust.works 102 points 2 months ago

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 2 months ago* (last edited 2 months ago)

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.

[-] PapstJL4U@lemmy.world 7 points 2 months ago

Yeah, certain code developed organically (aka shifting demands). Devs know the code gets worse, but either by time or money they don't have the option to review and redo code.

this post was submitted on 19 Mar 2026
1143 points (95.0% liked)

Programmer Humor

31514 readers
2296 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