nottoohard

Hey, so, these are not problems unique to git, for what it's worth. And if people don't want to deal with problems, then maybe software development isn't for them, because this is like a plumber complaining about joining pipes. (And don't bother belaboring this analogy, because I will not respond.)

No, it's lazy developers or people who should consider a different profession. I'm not smart and I'm good at git.

Then don't use it.

It's also sad because the "lol I only know four git commands" people are the most likely to break something, or to make bad long-term decisions about how to manage a source tree (yes, it's possible to do it wrong). Amazing that we have programmers advocating for deliberately staying ignorant of the tools they're expected to know.

The only winning move is to learn your tools and develop a mental model of what they're doing. You know, like everything else a programmer needs to know.

Yeah, everyone complaining is either lazy or bad at what they do. I learned git the hard way (i.e. from the Git Book and then thinking my way through problems), and I've been fine ever since. Not a week goes by where someone doesn't post something bitching about git, or some new twee thing they've made to teach something that actually comes with a great manual.

I'm truly distraught if this is the state of the profession, where developers can't (and won't) grasp the basic tools of the trade.

If software experts can't be expected to learn a tool for software experts, then I don't want them writing code for me, either.

How long will we baby the people who are supposed to know what they're doing? How long will we excuse this utter incompetence?

I truly don't get it. All these supposed software engineers who can't seem to grasp the basics of the tools of the trade. It's like watching carpenters argue about a hammer every few weeks for ten plus years.

There's no excuse. Either learn git, or stop using it. If you can do neither, stop complaining, because plenty of people use it just fine.

And no, you really don't have to understand the internals to use git, but you DO need a mental model of what's happening: what a commit is, what a ref is, what a branch is, what merging/rebasing does, etc. These don't involve knowing the internals, but they do involve maybe reading the manual and actually THINKING about what is happening.

Too many developers confuse not wanting to think about something with that thing being difficult. I learned git one summer during a college internship 15 years ago, and I've been fine ever since. I am really, truly, not that smart, and if I can do it, so can you.

Everyone needs to just quit their bitching and actually learn something for once.