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

  • For getting a grip in current web development, I would recommend fullstackopen.com - it’s a free online course by the University of Helsinki and starts from basically zero, and gives you a lot of insights into web dev.

    It may take some time, but it’s really worth it and an overall great course.

  • When I stopped, subversion was what we used. I’m trying to understand Git, but it’s a giant conceptual leap.

    It’s probably not ‘that much of a leap’ as you imagine. If you’re looking at Git tutorials, they’re usually covering all kinda complex scenarios of how to ‘properly use Git’. But a lot of people barely care about ‘properly using Git’ and they just kinda use it as a substitute for SVN… You create branches, you merge them back and forth, and that’s about it.

    Like if you want to contribute to an open source project, all you have to do is create a fork (your own branch in SVN terms) - commit some stuff to it, and create a pull request (request to have your changes merged) back to the original branch. git pull is just svn update - getting someone elses commits

    Not saying there aren’t more complex features in git, or that learning git properly isn’t worth it, just saying, I don’t think you have to see it as a ‘giant conceptual leap’ that’s preventing you from jumping back into programming. Easiest approach just to get started would be probably to just download a GUI like Sourcetree or Fork, and you just kinda pretend you’re still using SVN - approach wise

  • Someone will probably shoot me down for this but I actually find ChatGPT good for explaining concepts to me. Especially when I just want a high level understanding of a concept as I try to understand another one without getting too bogged down. A lot of Google results go into way too much detail.

    • It’s also great for solving issues when you’re stuck. Not because of its superior reasoning skills but it can solve beginner issues and write you a list of things to try when it doesn’t know the answer right away. It’s like a rubber duck that will talk back.

    • A few months back I would have said the same. Lately, however, ChatGPT very often returned very incorrect information on very basic topics. Each wrong answer erodes my trust a little bit more. Lately to a point where I consider googling first instead of asking ChatGPT

  • First of all, you can totally do it! The field is massive, but also full of very bad programmers, and seeing how you were able to write a coherent text of three paragraphs, that already puts you ahead of the curve. Determination and perseverance is key.

    I would suggest to play to your strengths. Java is still Java. Most of the progress since the 1990s was in the libraries and tooling, which only recently have become passable. The language itself also evolved somewhat, but there’s nothing that you won’t pick up in a couple of days of working with it.

    Start with [1], work through all the boxes that are unfamiliar to you, practice a little on a pet project, or an open source project, and you’ll land a job in no time.

    [1] https://roadmap.sh/java

  •  wewbull   ( @wewbull@feddit.uk ) 
    link
    fedilink
    English
    4
    edit-2
    11 days ago

    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 add files with changes inside before you commit them.

    Once you’re comfortable with using it by yourself, then I suggest running something like forgejo locally 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.

  • 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.

    You might check job listings in your region/country to figure out what languages and technology stacks are in high demand, as where you are seems to matter a lot.

  • Get a book on Spring Boot and jump back inro Java web development.

    With git, you don’t need to master it, just find some subversion to git howto and start using it. It’s half a page of text. Once you learn the basics you can learn more as you go. There are many otherwise competent programmers who don’t know git too well, I know because I support them from time to time.

  • As for git, many basic concepts (e.g. staging area) clicked for me after reading some articles that Atlassian (people behind BitBucket) wrote. Other than that, I’d recommend adamj.eu 's book “Git DX” which is on gumroad. Haven’t read it, tho. But I read his Django DX and like 90% of it was stuff I had to learn on my own, and thought: oh, how come I didn’t find this book earlier…

  • So the big important part of git is that it’s a collection of commits. A branch is just a labeled commit and each commit is a list of what changed from the parent. Rebasing (the most confusing one for people) is when you fiddle with a commit from underneath yourself. Or in even more simple terms editing a parent commit. Rebasing is extremely powerful but most useful for when you notice a bug you wrote a couple commits ago. Fixing such issues via rebase (or !fixup commits you auto squash at the end) keeps your history clean. It’s as though you never wrote the bug. The other thing you do a lot with rebasing is moving your branch up in the history cause somebody updated the remote.

    • I mean, this could be useful, but I need a much higher level of understanding. When I was a dev, all we used was basically version control. There was no concept of commit, pulls, etc. I’m having to understand this from a standpoint of no understanding whatsoever. For most devs, they’ve done this for at least a decade with Git. Git is so much more complicated than a simple version control. I understand why it’s necessary for large teams, but I still see it lke this:

      • You likely have a mental model of Subversion, so what I would suggest is to try to forget as much of it as possible first, as Git is very different.

        Take a tutorial that is aimed at Git beginners, e.g. [1]. This will help you start building a new mental model as well as get first practical experience.

        After that, read the official docs starting wtih the object model[2]. The reason why many people struggle to get into git, especially after using other VCS, is that it was built from the ground up, without much regard of the established conventions and terminology. Linus Torvalds once mentioned that he used his experience designing file systems when developing git.

        So the object model of git is very simple, but also not intuitive. However, once you understand it, everything will start making sense, including the xkcd you’ve linked.

        [1] https://gitimmersion.com/ [2] https://git-scm.com/book/en/v2/Git-Internals-Git-Objects

    •  ulkesh   ( @ulkesh@beehaw.org ) 
      link
      fedilink
      English
      211 days ago

      Yeah Spring wasn’t 1.0 until 2004. We had XML files upon XML files just to describe one single Java “Bean”. I did java programming from 2001-2002 and the again from 2011-today. Things dramatically changed (framework-wise) in that short decade I was away from it.

      I would agree, Spring Boot and Spring are very useful to learn. React, despite having its origins in Facebook and still with Meta’s hands on it, is a good web framework especially if you use it with Typescript.

    • No, we didn’t use that. I did both front end and back end in a sense. I developed the web UI for the customers and managed the PHP and SQL back end since it was purely a web interface. Yeah, yeah, I know that’s not true back end but that’s where we were at that point.

  •  mox   ( @mox@lemmy.sdf.org ) 
    link
    fedilink
    3
    edit-2
    11 days ago

    I’m trying to understand Git, but it’s a giant conceptual leap.

    In that case, I suggest learning Mercurial first. Its underlying design is very similar to Git, but the interface is more consistent and does a much better job of presenting the concepts to humans (especially those already familiar with traditional version control). Then, once you’re comfortable with the concepts and commands in Mercurial, learn Git, since it’s everywhere nowadays.

    Consider learning at least one new language, if not immediately (since you’re in a hurry) then in your free time. Java is only one of many (and not even a particularly nice one IMHO). Try to find a language that you enjoy using; your programming life will be better for it. If you want something flexible and productive, consider Python. For more structure than that, maybe Go. If mobile apps interest you, there are Kotlin (Android), Swift (iOS), and Dart (both). If web development appeals to you, along with lots of job openings and lots of competition for those jobs, JavaScript. If you fancy the esoteric (and well-paying), Elixir and Erlang are worth a look. Lower level languages are in demand as well (e.g. C++, Rust) but they come with various kinds of pain that I wouldn’t recommend to someone in your situation.

    Above all, please make sure you’re reserving time for things that make you happy, sleep, and (if still possible) some kind of exercise. Your own physical and mental health are important. If you endure a bad working environment or wear yourself thin for too long, you will burn out, which won’t help you provide for yourself or anyone else.

    Take care, OP.

  • Start with a git GUI application. I use git extensions on windows.

    You’ll be able to get a feel for how it all works and it actually shows you the commands it’s running.

    I also use bingai a lot when learning. The more specific your question the more likely you are to run into hallucinations and that. But for explaining basic concepts or query things that are well documented it’s really good.

    It also sources it’s answers so you can follow the link for further reading if needed.

    Just don’t trust it to generate large amounts of code.

  • It sounds like you already have a foundation to build on. If suggest using chatgpt or something similar to explore concepts you struggle with. “explain git to me as if I knew SVN 10 years ago but have forgotten a bit”