A little background: Through my teens in the 90’s I did a lot of the things you may expect. I was a script kiddie on mIRC, made a tank game in Unreal Engine, and did some Quake modding. From 2002-2004 I landed a job doing Java web dev, SQL, and overall database administration because my father’s friend needed someone that could do that. I was ok at the job, but not great. Being young, my hobby that turned into a 9-5 made me want to stab my eyes out and I quit.

With that said, I can understand a lot of what’s going on, but it doesn’t “click” anymore. I spent 20 years as a career machinist, but I physically can’t do that anymore. Here’s the rub - my twin brother is a brittle diabetic and can’t work (lots of other stuff going on as well), and our mother is getting old (father passed this year). The only reasonable way forward that I can see in order to be able to support my brother is trying to get back into development.

When I stopped, subversion was what we used. I’m trying to understand Git, but it’s a giant conceptual leap. I guess, what I’d like to hear from you all is a way to jump back in as quickly as possible in such a way that it may be a career.

Thanks

  • @Brosplosion@lemm.ee
    link
    fedilink
    13 months ago

    To piggyback, the true main difference is svn stores commits as snapshots and git commits are deltas from previous. This is why git is depicted as a tree since it’s inherently a node-based structure.

    • @ericjmorey@programming.dev
      link
      fedilink
      3
      edit-2
      3 months ago

      A git commit is a snapshot. The node-based tree structure is an artifact of recording pointers to other snapshots and labeling snapshots with a branch name.

      • @Brosplosion@lemm.ee
        link
        fedilink
        33 months ago

        You are correct. Technically a snapshot, but unmodified files are not duplicated from the previous. Imho that is one of the key things to understand about how git works ( and why rebasing and branch manipulation works so well)