4 ms·
Taking a week to learn a computer utility seems insane to me, I think that's one of the problems. People just want some version control, they don't want to lea
by crazygringo 14y ago
Taking a week to learn a computer utility seems insane to me, I think that's one of the problems.
People just want some version control, they don't want to learn a whole programming language to have to do it.
Imagine if I had to spend a week learning how to configure my screensaver, set up hard drive backups, or install Dropbox? Forget about it.
Now if git were only popular among super-power-hard-core programmers, then I don't think there would be any criticism. But it's the fact that it seems like pretty much everyone has switched to git now, because its advantages are fantastic, but it takes 100x longer to learn than any other tool I've ever used.
- hasenj 14y agogit is not just some other utility. The comparison to screen savers is not adequate. git is an advanced system tool meant for software engineers. That's why I compare it to a programming language or an operating system. Also, the return on investment is huge. I think that time spent learning git is time well spent.
- chris_wot 14y agoI would argue that you aren't learning a computer utility, but rather learning how distributed version control works. I honestly can't find anything in the author's post that doesn't make sense for DVCS.
- MBlume 14y agoOh come on. Your language, your editor, and your source control. Three things worth knowing backwards and forwards if you're going to call yourself a developer. Three things easily worth spending a week grokking, if necessary.
- aneth4 14y agoAnd then there's the thousands of libraries, debuggers, versions, deployment choices, design strategies, etc etc. Development is an endless path of learning, and git is barely learnable. And editors don't take a week to learn because you don't have to learn everything to use them. Even vi works quite well with just a few commands, and you will never NEED anything other than those, only optimize your usage.
- chris_wot 14y ago"git is barely learnable" - hardly!
- aneth4 14y agoThe fact that even experts admit they don't understand the array of options and implications for commands like reset and rebase would tend to support me here. And there is always dispute about the best way to do something as simple as back out a commit or clean large old files from a repository (very difficult with a large team). The series of incantations to do such things is always ridiculously obtuse, with non-intuitive flags and symbols. Sure the basics are learnable, and google can often reveal solutions (though rarely definitively), but I know no one with a comprehensive understanding of the majority of git fundamentals.
- chris_wot 14y agoI wouldn't be calling someone an expert if they don't understand what a rebase is.
- retrogradeorbit 14y ago"git reset is probably the most confusing command written by humans. I've been using Git for years, even wrote a book on it and I still get confused by what it is going to do at times." -- http://gitref.org/basic/#reset http://gitref.org/basic/#reset
- ryanpers 14y agosource code management is way beyond 'a computer utility', but since you brought it up, here are some other computer utilities: - dd - bash - find Most of those require quite a bit of time to master. Now, moving past that, git isn't merely a computer utility, its a foundational element in programming. It's actually more primitive than a programming language itself! The thing that separates the high school students from the "professional" programmers is SCM, and mastery of it. Having seen hardcore dev done on 10m loc code bases in perforce, you need some perspective on how hard git is and isnt. One of the biggest problems I find is that people attempt to understand git via the lens of SVN. Once you free yourself from the past and understand the basic fundamentals of git, and cast aside your svn-isms you will be zen. I for one wouldn't hire a developer who isnt intimately familiar with at least one SCM system. Zip files named v1, v2, v3 anyone?
- einhverfr 14y agoBut you aren't going to sit down and spend a week learning all the ins and outs of dd, bash, find, or, say, grep. You are going to skim the docs, learn the minimum to do the task at hand, wash, rinse, and repeat. My path at learning SVN was that way too. Heck I didn't even learn the merge command for a couple years until I really needed to, and then I realized how much I had been missing. I think the big issue that some of us have with git is it can't do all the same things that svn can do. Of course a big problem with svn is it can't do all the things git can do. I wouldn't set nails with a ball peen hammer either.
- chris_wot 14y agoIf you want to use git, here's a 10 minute primer: 1. Create the git repository: git init 2. To commit any changes, you type in: git commit -a -m "thing that I changed" 3. To branch, you type in: git checkout -b newbranch 4. To switch back to a branch, you just type in: git commit -a -m "changes made on branch" git checkout <branch> 5. To merge in a branch to the current branch, you type in: git merge <branch> 6. To push to a remote repository, you first add a remote repository by typing in the following: git remote add origin git@example.com:my_project.git (origin can be anything, but a good convention to use for the main repo that you are pushing to). Now to push your changes, you just use: git push origin <branch> Most often you will use: git push origin master
- pxlpshr 14y agoI understand, your argument is why I used Dropbox's primitive version control over SVN. I never had to think about it. But now I use git, and I don't even consider myself an engineer. I do front-end. Structurally speaking, git makes 10x more sense to me than SVN ever did.
- lloeki 14y ago> Taking a week to learn a computer utility seems insane to me I teach git at work. It takes me a grand total of 10 minutes to explain git's core concept to any dev. It takes me the better part of one hour to teach them how to use git. It takes them the rest of a work day for them to train basically without any intervention on my part, only man pages and a bunch of questions. After that they're basically without training wheels and hardly reach to me, except for the trickiest cases. That's assuming no one is stepping on the brakes, then one who does not want to learn, won't learn.