this post was submitted on 30 Jul 2026
168 points (100.0% liked)

History Memes

2801 readers
610 users here now

A place to share history memes!

Rules:

  1. No sexism, racism, homophobia, transphobia, assorted bigotry, etc.

  2. No fascism (including tankies/red fash), atrocity denial or apologia, etc.

  3. Tag NSFW pics as NSFW.

  4. Follow all Piefed.social rules.

  5. History referenced must be 20+ years old.

  6. Avoid posting AI-generated content whenever possible.

Banner courtesy of @setsneedtofeed@lemmy.world

OTHER COMMS IN THE HISTORYVERSE:

founded 1 year ago
MODERATORS
PugJesus@piefed.social
Deceptichum@quokk.au
PugJesus@lemmy.world
168
One Expensive Mistake (lemmy.nz)
submitted 16 hours ago by Grumpus_Maximus@thelemmy.club to c/historymemes@piefed.social
21 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] filcuk@feddit.uk 8 points 10 hours ago (1 children)

I don't think recycling code is embarrassing? No-one can be expected to write a new codebase from scratch for every new product or machine. That would be worse than building on top of a solid foundation.

[–] neidu3@sh.itjust.works 4 points 10 hours ago (1 children)

It isn't. Never testing that it's compatible with the new hardware platform is.

[–] filcuk@feddit.uk 3 points 9 hours ago

Having read up on it quickly, the real issue was with a lack of tests and failure handling, so you're not wrong.
Apparently this code wasn't even necessary to run after liftoff, yet it caused the self-destruct.
Crazy.