this post was submitted on 21 Mar 2025
764 points (98.8% liked)

Programmer Humor

21985 readers
2183 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
[–] yarr@feddit.nl 73 points 1 week ago (3 children)

It's a scary amount of projects these days managed by a bunch of ZIP files:

  • Program-2.4.zip
  • Program-2.4-FIXED.zip
  • Program-2.4-FIXED2.zip
  • Program-2.4-FIXED-final.zip
  • Program-2.4-FIXED-final-REAL.zip
  • Program-2.4-FIXED-FINAL-no-seriously.zip
  • Program-2.4-FINAL-use-this.zip
  • Program-2.4-FINAL-use-this-2.zip
  • Program-2.4-working-maybe.zip
  • Program-2.4-FINAL-BUGFIX-LAST-ONE.zip
  • Program-2.4-FINAL-BUGFIX-LAST-ONE-v2.zip
[–] ulterno@programming.dev 6 points 1 week ago* (last edited 1 week ago)

I did that with documents in my Uni years.
By the end, I was using ISO timestamps.

[–] Boakes@lemmy.world 4 points 1 week ago* (last edited 1 week ago)
  • Program-1.5-DeleteThis.zip
  • Program-1.6-ScuffedDontUse.zip
  • CanWeDeleteThesePlease.txt (last edit 8 months ago)

Inspired by a small collaboration project from a few years ago.

[–] iegod@lemm.ee 3 points 1 week ago (1 children)

If we're talking actual builds then zip files are perfectly fine as long as the revs make chronological sense.

[–] yarr@feddit.nl 3 points 6 days ago (1 children)

I'm not. I'm talking about in companies where dev A wants dev B to do some work, but they don't use git or any kind of source control, so you email over a cursed ZIP file, then dev B does the work and sends it back with a different name. It's a highly cursed situation.

[–] iegod@lemm.ee 1 points 5 days ago

Yeah that's bad.