• Lucy :3@feddit.org
    1411·
    7 days ago

    “Developer”
    “my” 4 months of “work”

    Those are the ones easily replaced by AI. 99% of stuff “they” did was done by AI anyway!

  • Artyom@lemm.ee
    871·
    7 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
    73·
    7 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·
      6 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
      2·
      6 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
        2·
        5 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.

  • darklamer@lemmy.dbzer0.com
    104·
    7 days ago

    The first version control system I ever used was CVS and it was first released in 1986 so it was already old and well established when I first came to use it.

    Anyone in these past forty years not using a version control system to keep track of their source code have only themselves to blame.

    • barsoap@lemm.ee
      32·
      7 days ago

      CVS was, for the longest time, the only player in the FLOSS world. It was bad, but so were commercial offerings, and it was better than RCS.

      It’s been completely supplanted by SVN, specifically written to be CVS but not broken, which is about exactly as old as git. If you find yourself using git lfs, you might want to have a look at SVN.

      Somewhat ironically RCS is still maintained, last patch a mere 19 months ago to this… CVS repo. Dammit I did say “completely supplanted” already didn’t I. Didn’t consider the sheer pig-headedness of the openbsd devs.

      • lud@lemm.ee
        5·
        7 days ago

        Pretty sure GTA V use(d) SVN or something like that. I remember reading the source code and being surprised that they didn’t use GIT.

          • barsoap@lemm.ee
            3·
            6 days ago

            You definitely need something else than git for large assets, yes, its storage layer is just not built for that and they way art pipelines generally work you don’t get merge conflicts anyway because there’s no sane way to merge things so artists take care to not have multiple people work on the same thing at the same time, so a lock+server model is natural. Also, a way to nuke old revisions to keep the size of everything under control.

      • I Cast Fist@programming.dev
        4·
        7 days ago

        “We’ve always done things this way, we ain’t changing!” - some folks in the Foss community, like those RCS maintainers

      • Zron@lemmy.world
        3·
        6 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·
      5 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 /

  • zovits@lemmy.world
    53·
    7 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
      18·
      7 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.

  • Scary le Poo@beehaw.org
    243·
    6 days ago

    Just a heads up, it you don’t know how to use cli git in 2025 you’re probably a shit developer. There are undoubtedly exceptions, but I would argue not knowing version control intimately makes you a bad developer.

    • easily3667@lemmus.orgEnglish
      626·
      6 days ago

      Why learn an archaic and honestly horrifying command line interface, possibly the worst CLI ever made in the history of computing…when nice normal graphical interfaces work better, have discoverability, have troubleshooting tools, and don’t require memorizing scripture?

      • ScoreDivision@programming.dev
        13·
        6 days ago

        Mate… Theres maybe like 5 “git + singleword” commands that cover 99.999% of all of your uses of git. Its really not hard.

      • expr@programming.dev
        10·
        6 days ago

        Because they are universally incapable of coming anywhere close to the full power of git.

        I can’t tell you how many times I’ve had GUI-only people ask me to unfuck their repo (fortunately not at my current job, because everyone uses the CLI and actually knows what they’re doing). It’s an impedance to actually learning the tool.

        Ultimately any GUI is a poor, leaky abstraction over git that restricts many of the things you can do for little actual benefit.

      • letsgo@lemm.eeEnglish
        9·
        6 days ago

        Most cli stuff is a lot easier than programming. If you can’t use cli then by definition you’re a shit programmer.

        Of course if you simply don’t want to use cli that’s a different matter.

      • gamer@lemm.ee
        81·
        5 days ago

        There’s nothing ‘archaic’ about git’s CLI. I think you might just be opposed to CLI’s in general, which is fine for a regular computer user, but paints a grim picture of your competency if you’re a developer.

        • WhatsTheHoldup@lemmy.mlEnglish
          4·
          5 days ago

          That seems unnecessarily harsh.

          I find the built in controls with visual studio supremely convenient.

          After using git init --bare for the remote repo I use the built in git controls for branching and switching out as well as syncing and pushing. Why not, the button is right there and it’s literally faster.

          • Scary le Poo@beehaw.org
            8·
            5 days ago

            The difference is that PRESUMABLY you aren’t utterly dependent upon it. If vscode utterly fucks your repo with a shit command, you’ll not really have any trouble fixing it. That’s the huge difference. The point is not that all GUI controls are always bad all of the time, the point is that you need to know what the hell you are doing in git as a basic tenant of developer competency.

      • Scary le Poo@beehaw.org
        111·
        6 days ago

        The fact that you don’t already know why and are dependent on GUI tools that you don’t fully understand is the reason that you’re probably not a very good developer.

        Git is incredibly powerful. Knowing why and how is infinitely valuable. Nothing about git cli is archaic or even particularly difficult to understand. Also the man page is very excellent.

        • easily3667@lemmus.orgEnglish
          310·
          6 days ago

          Ah, the no true Scotsman fallacy. Neat.

          Your lack of rational thought backed up by facts rather than feelings is why you’re a bad developer.

          See I can do it too.

          But honestly even saying “nothing about the git cli is archaic” is…well, it’s either disqualifying or Stockholm syndrome, and Stockholm syndrome isn’t real.

          • Scary le Poo@beehaw.org
            4·
            5 days ago

            I said that you are probably not very good. Your lack of git knowledge and your seeming inability to learn git means that you’ll likely never be able to function effectively in a development team and will only succeed in holding everyone back. Your lack of knowledge of version control overall is a massive point against you from the outset.

            If you’re a solo developer and never need to collaborate with other developers then good for you, but you lack of version control knowledge means that you’ll also probably end up being one of the ones crying that you lost 6 months of work because of stupid reason x y or z.

            Read up on fallacies, I did not use one. Your pathetic attempt to shoehorn anything that I said into a no true Scotsman fallacy just shows that you also have poor communication skills.

            Holy fucking shit. I didn’t even catch the bit at the end. You really think that cli arguments are archaic??? I’m going to go ahead and assume that regex has you scared shitless as well. Fuck me, you are not a good developer.

            Sidenote, something that will help you understand regex and you can test your strings against it in realtime, look up https://regexr.com/

      • ඞmir@lemmy.ml
        4·
        6 days ago

        As someone using git for the last 10 years by now: you’re wrong. No UI has managed to give me access to all the fuckery I often do very quickly on the command line. I was honestly surprised to see IntelliJ nowadays supports an interactive rebase, but reflog, which should be a basic git feature, is still not widely supported in most IDEs in 2025. Or adding, resetting or checking out files with regex. Setting up and modifying lfs. And these are all basic features, good luck doing something like using branch~n syntax for some of the operations etc.

        Git UI is shit and will be for a long time.

      • شاهد على إبادة@lemm.ee
        2·
        5 days ago

        Why learn a GUI that can change from release to release when I can learn a CLI once and be done with it. An additional plus is that CLIs are easier to script and automate.

      • Transtronaut@lemmy.blahaj.zone
        3·
        5 days ago

        I never understood the SVN hate. Then, as now, the problems are almost never caused by the tools, and almost always caused by the people misusing them.

        • gamer@lemm.ee
          2·
          5 days ago

          I never got around to using anything except git, partly because of all the hate people would throw at the other competitors back in the day. Even if the criticisms were not fair, and even if it was all a secret conspiracy to kill git competitors, it definitely worked out for the best. Imagine the hell we’d be in today if we had to constantly deal with different VCS solutions.

          • Transtronaut@lemmy.blahaj.zone
            1·
            4 days ago

            It wasn’t really that big a deal. Most of them have more in common than they have differences. If anything, I experienced fewer problems in the age of SVN. It has fewer options than git, but it’s also a lot more intuitive and easy to learn, which counts for a lot when your largest limiting factor is your coworkers.

            Not saying I want the world to go back to that, just pointing out the hate is really overblown.