yarr comments on Git, invented in 2005. Programmers on 2004:

Git, invented in 2005. Programmers on 2004: (lemmy.eco.br)

submitted 1 year ago by driving_crooner@lemmy.eco.br to c/programmer_humor@programming.dev

156 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] yarr@feddit.nl 74 points 1 year 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

hideshow 6 child comments

[–] ulterno@programming.dev 7 points 1 year ago*

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

parent

[–] Boakes@lemmy.world 4 points 1 year ago* (last edited 1 year 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.

parent

[–] iegod@lemm.ee 3 points 1 year ago (1 child)

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

parent

hideshow 2 child comments

[–] yarr@feddit.nl 3 points 1 year ago (1 child)

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.

parent

hideshow 2 child comments

[–] iegod@lemm.ee 1 point 1 year ago

Yeah that's bad.

parent