My biggest beef with git is that nobody thinks that it's important enough to teach. Whenever you go through a boot camp or even a college web design program, they only spend a day or two on it max and then move on. That leaves people to learn it once they're actually involved in a project, which is...not ideal.
College/uni is supposed to show what to learn on your own, rather than hold your hand all the way through. That is what's absolutely missing from being mentioned in any of the programmes.
Yeah I only pay tens of thousands of dollars for an impersonal impossible being to grunt and mutter phrases from a time and place so utterly absent and uncaring of human understanding that I receive nothing of value from it.
I already know what I need to learn. You could figure that out with a web search. Just see which skills employers are asking for in job postings. Why would I go to college for that?
Lemmy is very young and sensitive. This meme-y post got more attention that usual stuff.
I agree with your sentiment. I miss the time where RTFM was understood as "you've not bothered solving it yourself, why waste my time" instead of today's "fuck off". People can really be snowflakes at times.
LOL. Much respect of you're wizardly enough to just learn it from man git. Fortunately, there are plenty of more accessible learning tools for us mere mortals.
I'm sure you'll find some old devs who still prefer CVS over SVN. Don't underestimate the force of habit. Even in a field like development where you should always update your knowledge and skills, there are tons of people who are very reluctant to changes.
I don't prefer it, but I do prefer some things about it. Git overcomplicates certain things and uses bizarre terminology in places. But I'd still rather use Git any day
Generally speaking, people who prefer subversion spent a lot of time using it before got became the mainstream. It's not generally been an opinion formed from contemplation but that the workflows are so different that they are having to return source control management from scratch.
Developers typically don't want to be told they have to learn a new tool unless it was their idea.
I forgot about "porcelain," been so many years I don't even remember what it refers to. I do remember that it always reminded me that git is a toilet for all the shit code I had to deal with, so maybe that's why people stopped talking about it?
Also i feel like "merge conflict" could have been the center square, I just love walking newbies through that. "What did you do to generate this many?" "I was just cherry-picking all my commits and then tried to rebase master onto them?"
Just use magit as a git porcelain, I have used it because despite using git for 10 years I have no idea how it works other than only 5 commands since I just do not care how git works because I hate git and the cli is badly design. I don't know how magit is for rebasing though, but that sucks anyway and you should be merging instead, since a branch is just a pointer to a commit which is an immutable snapshot there is no point in switching branches.
Cool bingo grid (stars it on GitHub)
But there are a few things I donβt quite agree with, (pulls branch), and you choild change it (pull request send)
I'm sure you'll find some old devs who still prefer CVS over SVN. Don't underestimate the force of habit. Even in a field like development where you should always update your knowledge and skills, there are tons of people who are very reluctant to changes.