• dan@upvote.au
    115·
    13 days ago

    Before Git, we used SVN (Subversion), and CVS before that. Microsoft shops used TFS or whatever it’s called now (or was called in the past)

    • i_stole_ur_taco@lemmy.ca
      48·
      13 days ago

      Wasn’t it Visual SourceSafe or something like that?

      God, what a revolution it was when subversion came along and we didn’t have to take turns checking out a file to have exclusive write access.

      • dan@upvote.au
        20·
        13 days ago

        Visual SourceSafe

        Yes! That’s the one I was struggling to remember the name of. My previous employer started on Visual SourceSafe in the 90s and migrated to Team Foundation Server (TFS) in the 2000s. There were still remnants of SourceSafe when I worked there (2010 to 2013).

        I remember TFS had locks for binary files. There was one time we had to figure out how to remove locks held by an ex-employee - they were doing a big branch merge when they left the company, and left all the files locked. It didn’t automatically drop the locks when their account was deleted.

        They had a bunch of VB6 COM components last modified in 1999 that I’m 80% sure are still in prod today. It was still working and Microsoft were still supporting VB6 and Classic ASP, so there wasn’t a big rush to rewrite it.

        • HarkMahlberg@kbin.earth
          6·
          13 days ago

          Welcome to my world… our new lead architect has mandated that we move everything from TFS to GitLab before the end of the year. I hope it comes true.

          • Flames5123@sh.itjust.worksEnglish
            4·
            12 days ago

            At the start of COVID, I migrated our three projects to git from VSS. I also wrote a doc for our other teams to do the same. It was amazing once we got it working. Small team of 3, but we started using feature branches which enabled us to easily merge everything into a testing branch and release only certain features at a time. So much cleaner.

            Before I left, I almost got semi automatic CI/CD working with Jenkins!

          • nogooduser@lemmy.worldEnglish
            3·
            13 days ago

            I remember when our company split up and we had to give them the source code of some older versions that they still used. We couldn’t do that because the repo was corrupt meaning that we couldn’t access some older revisions. We had no problems using it day to day so nobody noticed which meant that all backups were also corrupted.

      • HarkMahlberg@kbin.earth
        7·
        13 days ago

        Yeah VSS was the predecessor to TFS, and now TFS is called Azure DevOps… whatever the fuck that means, Microsoft needs to get it together with product naming. Anyway TFS sucks major rotten ass. I have my problems with git - namely user friendliness - but TortoiseGit has put all those troubles to rest.

        Nothing like that can fix TFS.

    • GhostlyPixel@lemmy.worldEnglish
      8·
      13 days ago

      My first SWE job out of college in 2019 they were still using SVN because none of the seniors could be bothered to learn how to use git.

      The “well this is how we’ve always done it” attitude had a death grip on that place

      • dan@upvote.au
        6·
        13 days ago

        For what it’s worth, SVN is a much simpler object model compared to Git, which makes it easier to understand.

        It’s centralized rather than distributed like Git is, which has some disadvantages. Most operations require access to the server, as opposed to Git where you usually have a copy of the entire repo and can work offline. Git users can clone the repo from other users rather than relying on a centralized server.

        On the other hand, a centralized server also simplifies some things. For example, instead of commit hashes, SVN has revision numbers, which are natural numbers that start at 1 and are incremented for every commit. A lot of software that used SVN used to use the revision number as part of the version or build number.

        Git is definitely the source control system to choose today, but SVN can still have its place.

    • The_Decryptor@aussie.zoneEnglish
      6·
      13 days ago

      A place I worked at did it by duplicating and modifying a function, then commenting out the existing one. The dev would leave their name and date each time, because they never deleted the old commented out functions of course, history is important.

      They’d also copy the source tree around on burnt CDs, so good luck finding out who had the latest copy at any one point (Hint: It was always the lead dev, because they wouldn’t share their code, so “merging to main” involved giving them a copy of your source tree on a burnt disk)

    • ByteJunk@lemmy.world
      3·
      13 days ago

      Oh yeah, I remember using tortoiseCVS briefly.

      Mercurial and Bazaar also showed up at around the same time as git, I think all spurred by BitKeeper ending their free licenses for Linux kernel devs.

      An interesting shot to the foot, that one.

      BitKeeper was a proprietary version control system that somehow (and with a lot of controversy) ended up being adopted by a big chunk of the Linux kernel developers, while others were adamant against it.

      In any case, they provided free licenses to Linux devs, with some feature restrictions (including not being able to see full version history) only available for premium clients, while Devs who worked on open source competing systems were even barred from buying a licence.

      When someone started to work on a client that allowed access to these locked away features, they revoked the free licenses, and a host of solutions started being developed immediately. Linus Thorvalds himself started work on git, and that eventually got adopted by the whole Linux ecosystem and, nowadays, the world.

      As for BitKeeper, it’s been dead for years now.

  • Artyom@lemm.ee
    811·
    13 days ago

    I just want to pause a moment to wish a “fuck you” to the guy who named an AI model “Cursor” as if that’s a useful name. It’s like they’re expecting accidental google searches to be a major source of recruitment.

  • yarr@feddit.nlEnglish
    67·
    13 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
    • Boakes@lemmy.world
      4·
      12 days 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·
      12 days ago

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

      • yarr@feddit.nlEnglish
        3·
        12 days 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.

  • Eager Eagle@lemmy.worldEnglish
    63·
    13 days ago

    if this is real, that’s the kind of people who should be worried about being replaced by an ai

    it’s also Claude

    lmao

    • Scrubbles@poptalk.scrubbles.techEnglish
      16·
      13 days ago

      Was playing around with it. It’s neat tech. It’s interesting all the side projects I can spin up now. It absolutely cannot replace an engineer with a brain.

      I’ve caught so many little things I’ve had to fix, change. It’s an amazing way to kick off a project, but I can’t ever trust blindly what it’s doing. It can get the first 80% of a small project off the ground, and then you’re going to spend 7x as long on that last 20% prompt engineering it to get it right. At which point I’m usually like “I could have just done it by now”.

      I see kids now blindly trusting what it’s doing, and man are they going to fall face first in the corporate world. I honestly see a place for vibe coding in the corporate world. However I also see you still needing a brain to stitch it all together too.

      • Zron@lemmy.world
        3·
        12 days ago

        You know, none of the “AI is dangerous” movies thought of the fact that AI would be violently shoved into all products by humans. Usually it’s like a secret military or corporate thing that gets access to the internet and goes rogue.

        In reality, it’s fancy text prediction that has been exclusively shoved into as much of the internet as possible.

    • danhab99@programming.dev
      3·
      11 days ago

      Genuine question: what would it take to poison an LLM with ai tools to run git push --force origin main or sudo rm -rf /

      • adminofoz@lemmy.cafeEnglish
        1·
        6 days ago

        Pen Tester here. While i don’t focus on LLMs, it would be trivial in the right AI designed app. In a tool-assist app without a human in the loop as simple as adding to any input field.

        && [whatever command you want]] ;

        If you wanted to poison the actual training set in sure it would be trivial, but It might take awhile to gain some respect to get a PR accepted, but we only caught an upstream attack on ssh due to some guy who feels the milliseconds of a ssh login sessions. Given how new the field is, i don’t think we have developed strong enough autism to catch this kind thing like in SSH.

        Unless vibe coders are specifically prompting chatgpt for input sanitization, validation, and secure coding practices then a large portion of design patterns these LLMs spit out are also vulnerable.

        Really the whole tech field is just a nightmare waiting to happen though.

  • zovits@lemmy.world
    41·
    13 days ago

    It’s actually reassuring to see that despite all warnings and doomsayers there will still be opportunities for programmers capable of solving problems using natural intelligence.

    • finitebanjo@lemmy.world
      15·
      13 days ago

      If anything it feels like we’re the doomsayers trying to warn people that their AI bullshit won’t ever work and they’re just not listening as they lay off the masses and push insecure and faulty code.

  • NigelFrobisher@aussie.zone
    37·
    13 days ago

    You need a USB C “Power Ctrl+Z” key. Unlike the regular Ctrl+Z key one of these bad boys is capable of reversing edits across system reboots until as far back as when you originally plugged it in.

    • Jayjader@jlai.lu
      1·
      11 days ago

      From what I understand, you could un ironically do this with a file system using BTRFS. You’d maybe need a udev rule to automate tracking when the “Power Ctrl+Z” gets plugged in.