• yarr@feddit.nl
    link
    fedilink
    English
    arrow-up
    72
    ·
    2 days ago

    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
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      1 day ago

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

    • Boakes@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      1 day 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
      link
      fedilink
      arrow-up
      2
      ·
      1 day ago

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

      • yarr@feddit.nl
        link
        fedilink
        English
        arrow-up
        2
        ·
        18 hours ago

        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.