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
I’m trying to understand Git, but it’s a giant conceptual leap.
To start with, start with just using git locally. Don’t worry about GitHub or similar. Then git and SVN will work very similarly. The main difference is that you need to
git addfiles with changes inside before you commit them.Once you’re comfortable with using it by yourself, then I suggest running something like
forgejolocally to be your own code server. Then you can play and learn how the two parts work together.Generally, you need to give yourself a little time. You need to do the work. Be efficient…sure, but don’t try to force it to be quicker than the time you need to learn.
Best of luck to you!
I’m trying to understand Git, but it’s a giant conceptual leap.
Git is not that different from svn (I mean, the biggest hurdle is going from a shared folder to any version control system)… I’d say the main difference is that branches live in a different namespace than files (ie. you don’t have trunk/src/whatever but just src/whatever in the main branch). On top of that there’s that commit and push are two different things (and the same with fetch and checkout) and that merges are way easier than in svn (where you had to merge stuff manually).
If you create a repo locally and clone it twice in two different directories, you can easily simulate what would happen when you and a coworker collaborate via a centralized repo (say, github) - do a few experiments and you’ll see it’s not as complicated as it seems (I’d recommend using the CLI instead of some GUI client: it’s way easier to figure things out without the overhead of learning to differentiate between git concepts and how the GUI tries to help).
Just remember: imposter syndrome is real. Everything you learn exposes you to ten things you don’t yet know. Successful devs are comfortable with this reality - the job is one of constant learning. Best of luck!
