• simonced@lemmy.oneEnglish
    2·
    20 hours ago

    Letting your text editor write your code, not using version control… I don’t feel sad at all. Hope lesson was learned.

  • Artyom@lemm.ee
    801·
    3 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.

  • Scary le Poo@beehaw.org
    233·
    3 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
      625·
      3 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·
        2 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.

      • gamer@lemm.ee
        71·
        2 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.

      • letsgo@lemm.eeEnglish
        9·
        2 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.

      • expr@programming.dev
        9·
        2 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.

      • Scary le Poo@beehaw.org
        101·
        3 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
          38·
          2 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
            3·
            2 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/

      • شاهد على إبادة@lemm.ee
        2·
        2 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.

  • gamer@lemm.ee
    5·
    2 days ago

    I made a game engine and a game back in highschool, but all that code is lost because I didn’t know how to use git. I knew git existed (and even knew enough to know it was better than mercurial or svn), but I was too lazy to learn.

  • Lucy :3@feddit.org
    1321·
    4 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!

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

    • danhab99@programming.dev
      3·
      2 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 /

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

    • Lucy :3@feddit.org
      61·
      4 days ago

      Tbf you have to do that for the first push, if a Readme file was autogenerated

      • computergeek125@lemmy.worldEnglish
        4·
        4 days ago

        Does that still happen if you use the merge unrelated histories option? (Been a minute since I last had to use that option in git)

        • Lucy :3@feddit.org
          2·
          4 days ago

          Never have heard of that, but in the case of you also having a Readme that will be even more complicated, I imagine. So just adding -f is the easier option.

  • darklamer@lemmy.dbzer0.com
    99·
    4 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
      31·
      4 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.

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

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

      • lud@lemm.ee
        5·
        4 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·
            3 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.

      • Terrasque
        1·
        3 days ago

        which is about exactly as old as git.

        Wdym by that?

          • Terrasque
            1·
            2 hours ago

            Svn: 20 October 2000

            Git: 7 April 2005

            I remember using svn when git development was started