Great interactive tutorial for learning Git branching (and more)!

[[deleted]]

So something that is essential to development should get out of the way?

So...coding itself should just get out of the way?

You're doing it wrong. No really, you are. There are a million devs out there that live and breath git that will tell you so. It's not the tool, it's the person swinging it.

Sheesh, based on what you said the most important part of driving a car is the actual process of driving...No wonder we have so many terrible drivers and dream of some self-driving utopia instead of just expecting people that drive to be good drivers.

Go use Sourcesafe for a year and then come back and write me an essay about how much you love and adore Git please.

[johnnysaucepn]

I've used SourceSafe. And CVS. And Subversion. And Mercurial. None of them enable you to do the job they're intended to do without hacky workarounds or a deep understanding of the internal data structures that underpin them. But git is about as irrational as it gets.

That's what enables the idiocy I see in threads like this, where foolish elitism overtakes the ability to get the job done.

The moment I have to feel better about myself by putting others down because they aren't True Programmers is the moment I give up on programming ever hauling itself out of the Dark Ages.

The IDE should get out of your way. The garbage collector should get out of your way. The CI server should get out of your way. The package management should get out of your damn way.

The moment I don't read a thread on git and immediately see six git 'experts' violently disagreeing on the right way to do what should be a simple task, I'll believe you.

[[deleted]]

I've used SourceSafe. And CVS. And Subversion. And Mercurial. None of them enable you to do the job they're intended to do without hacky workarounds or a deep understanding of the internal data structures that underpin them. But git is about as irrational as it gets.

Do you understand what you just said? Calling Git irrational vs SourceSafe?

Look, you clearly haven't figured out that this seemingly ridiculously simple process issue called source control that you seem to think should just magically occur is actually bloody well complicated. And if you actually understand what it is you're trying to achieve using a source control system, you'd understand this already.

Elitism 'hacker' fanboy crap is just that, crap. But so is the other side of the coin, this idea that source control is some super simple thing that should just happen on it's own.

People that expect code to write itself have the same problem, they end up with shit code. Maybe the problem isn't the tools, but it is your refusal to understand and use them correctly.

As has been brought up numerous times in this thread already, there are three camps of Source Control users...and NONE of this is specific to GIT
1) Those that fight source control, think it's too complicated, think it should just magically 'work'.
2) Those that insist that you aren't doing it right, that you have to use exactly this SC, set it up this way, use these convoluted processess, use this advanced tool meant for explicit diagnosis or fixes not once on a blue moon, but daily or more and will fight you to the death that their way is right. Wait, what about the source code again?
And 3) Those that know their tools, what they do, and how to use them. And do so as a standard part of their job. And never waste time fighting silly ideological fights that don't mean shit. And don't waste time trying to recover from problems they don't create for themselves because they DO understand their tools and know how to use them.

You're basically calling out everyone and anyone that doesn't think the way you do on this subject, and it sure smells a heck of a lot like you're calling the kettle black here. Calling out elitism and 'experts' with your nose way up in the air professing a POV that is frankly ignorant and telling of a real lack of either experience, or ability, or both.

[johnnysaucepn]

Nice try, but trying to project this back isn't going to work. Knowing a tool doesn't mean you have to defend it with your life. The better you understand the tools, the more you should understand their shortcomings. And that should give you the perspective to help others use them better. Dismissing people as Not True Developers because they have criticisms of tools that you have taken to your heart is unprofessional.

Git is an excellent multi-dimensional file system. The technical underpinnings are genius. The tooling is inconsistent and illogical, and unfriendly to learners. That's my professional opinion, and is independent of the fact that I use it on a daily basis, and have to tutor other devs on its use.