Git

(plus i make courses for them)

This is also the best way to support me is to support yourself becoming a better backend engineer.

[LuxFerre]

In my uni, Git was a single lecture. That seems about right.

[nesssel]

A whole course on it, hell no, but I'm absolutely in favor of introducing as soon as the first programming assignment is given. Builds good habits and is a life-saver so many times.

[marcsonic]

For us, we didn't specifically get taught git but our labs were stored in gitlab repos and had to be pushed back for us to mark it, and all we did was figure it out that way

[bob_kazamakis]

As an intern mentor, it would improve my sanity if they came in with this knowledge

[austinfinell]

I gave a 5-10 min breakdown of git when I was VP of the CS club at my college. I then had everyone create a quick test repo and push a change. Seemed good enough to start.

[malekith]

I taught myself Git during university(EE major) and made all my lab/work partners use it. It worked out pretty well for me. Ironically, I ended up in a job using Perforce... Use Git, and don't even dare to use SVN—save your sanity... Anyway A full-blown Git course might be overkill, but requiring students to use it for labs and class projects isn't a bad idea.

[SinCityGT]

This reminds me how many recruiters list 5 years of experience using git, on job postings. It takes a few days to just use it and memorize what you need to use.

[cheeseman]

My uni had a "Software engineering tools" class, where you learn AWS, basic CI/CD, Agile/Scrum, Git, and a bunch of other random tools. it was just 1 big projecr where you would add another infrastructure thing to a project. It was a great class and I think most SWE/CS degrees should offer it at least as an elective

[maxoumimaro]

During my studies it was mandatory to submit most of your project through git.
You would get some amount of lecture for it, not a lot and then you just have to use it.
Three benefits I see:
- you develop the knowledge of git when things matter less because loosing time in your actual job is way worse, plus git tends to be learned by error, where you understand the benefits of saving your work often only after loosing days/weeks of uncommited work.
- you learn early on that "making a project" should imply "having a git" which should be the default

[Zikos]

Should be thought as a primary tool, just like an IDE or a VScode is used for coding. It creates great habits and helps push (no pun intended) students towards building stuff themselves in a safer way

[circulardep]

When I was in uni in Sweden, Git was not a class in itself, but we had to hand in our programming assignments using Git and GitLab. That way we naturally became acquainted with the basics of it. Although I agree with Prime, you will eventually learn it at your first job.

[gamma]

I think that if you are going to succeed as a developer, you should be able to learn git on your own.
Personal hot take, take it or leave it, lol (there are enough resources/videos on the topic where experimentation should be enough, not to mention enough people who are enthusiastic enough to talk about it bc trees and nodes are a fun math concept anyway)

[Chill]

I had a 1 credit hour GIT course. Not difficult, did the job. Thankfully I was able to test out of it.

[heroclixrz]

We had student run Tech Talk lunches. Someone would volunteer to prep a talk on some topic, the uni gave us budget for lunch, and people would show up and learn something. We had at least a couple of those on git over the years. The professors were all CS theory, they didn't care what language we programmed in, let alone what version control we used.

[kalebbruwer]

We weren't taught git, but were expected to use it in our big practical module.

Which is fine, you can learn git in an hour or two from youtube. On that note, they didn't teach us Java either. They taught us C++ in 1st year with the rationale that once you know C++ you can pick up most languages with ease

[aaronskywarder]

We were never taught how the git works at my university, but we were expected to know how it works from the day 1 pretty much.

[eklipsed]

I agree with this but also I think the way our university does it isn’t bad. They make you take a lower level course early on that teaches people how to use Linux and they have some git practice in there. The class was a bit overboard but it makes sense from a standpoint of not wanting professors to have to teach those things every semester.

[Verruckt_Vidarr]

I still believe as part of Promotion requirements from junior to base engineer you need to be comfortable with rebase, revert and give me a tl;dr summary of how common merge conflicts can occur. Bonus points if you are comfortable with different branching strats and how to properly handle hotfixes in each. (Consultant here so I work with clients with every level of CICD maturity)

Not asking for in depth knowledge, not ask for it to be a pre req to get a job. But you should not get to avoid learning the basics within the first year of working.

For heaven's sake git's doco is sufficient and gives you enough to get on with the basics.

[ifiliketrains]

my study group tried to work with git for about two months, but something kept going wrong when it came to merging branches so we decided that in order to make sure the integrity of the program didnt fuck up, that it was easier to make copies of the entire project, upload them as seperate projects, then drag and drop files from each project into one main repository

[Reuschman]

As part of my under grad in computer science, we had to take a software engineering course and git was one lecture and we were given a cheat sheet. That's all you really need for it