4 ms·
"...but are somehow overwhelmed by the basic task of finding a good Git tutorial." Ummm.... when you don't know the tool, you're not in a good place to judge w
by mgkimsal 14y ago
"...but are somehow overwhelmed by the basic task of finding a good Git tutorial."
Ummm.... when you don't know the tool, you're not in a good place to judge what a 'good' tutorial is. This is the same reason we've got generations of bad PHP developers out there - they can't tell what's good or not.
"scores of software developers out there who have learned their craft enough to want source control"
How many people 'want' to learn source control, and how many people are told 'this is what we use here, go learn it'? I suspect far more of the latter, especially with git. People would not flock to git purely based on the documentation quality. Further, I suspect that had git just been written by some random dude off the street with no major project behind it, it would have never taken off. Using it for Linux kernel work has ensured a sizeable number of people are going to have to use it, whether they like it or not.
- encoderer 14y agoHow many kids want to go to school and how many are told by their parents that 'this is what you do so you can be happy and successful later.' I suspect more of the latter. But like leaning Git, earning your education will pay off. Does that mean Git is without flaws? Of course not. And if you want to work to improve it, and release a better version, go for it. But anybody that sticks with SVN and refuses to learn modern DVCS is not somebody I'd hire. Maybe this is a problem on IT-department, line-of-business teams (where most software developers work) but if Bay Area tech companies are a leading indicator, a big majority of Engineers I work with use and love DVCS's like Git and HG and there's not this groundswell of resistance. And while this isn't related to my previous comments: To anybody who has tried Git and ended up "losing work" because of a misunderstanding of the commands, let me assure you: It's actually a lot harder to lose work than you think. Anything you add to the Index (eg git add foo.py) or commit is stored in the Reflog (which is just a DAG). The reflog is garbage collected periodically -- see below for details. Within that window, you can recover any lost state from the reflog. So how long does Git keep things around by default? Intermediate products of conflicted merges - 15 Days Unreachable commits (do a git reset --hard HEAD~1?) - 30 Days Intermediate products of a resolved merge conflict? - 60 Days Everything Else? - At least 90 days.
- manveru 14y agoI almost had an heart attack after doing `git push --mirror`. It deleted 95% of branches locally and on origin without leaving much of a trace, or any way to undo (well, none that i know of). Good thing I had a clone on a machine at home, so I drove home, made local branches for each remote branch and then pushed each. So yeah, there might be a way to get that stuff back, and I don't even have experience with non-DVCS, but the lesson I learned a long time ago with darcs is that you better have up-to-date off-site backups of your repositories, never trust yourself or your DVCS too much. The upside is that keeping backups is easy, and good practice anyway, so if you're not doing it yet, don't wait.
- qu4z-2 14y agoMy worst experience on that front was with jekyll. Running jekyll without parameters compiles the source in the current directory, putting the output either in $PWD/_site, or wherever the config file for the project says. I was in the parent directory, and thought I'd try to run jekyll projectname rather than having to cd in and out of the project. The end result? It tries to compile the project in the current directory, writing output to the directory specified. As an added bonus, it completely nukes the target directory, including the .git subdir. And to add insult to injury, $PWD didn't even contain a valid project, so it error'd out immediately after wiping out the entire source. The morale of the story: Always keep offsite backups.
- flatline3 14y ago> But anybody that sticks with SVN and refuses to learn modern DVCS is not somebody I'd hire. You wouldn't hire me. I'm OK with that. I use git (required for an assortment of OSS projects), but for my own work, at at work, I use SVN. I'd never willingly choose git. It's complex, involved, powerful, and incredibly distracting from the actual thing I want to do, which is write software. The minute someone says something like this, my eyes glaze over: "Anything you add to the Index (eg git add foo.py) or commit is stored in the Reflog (which is just a DAG)." Not because I don't understand git's fundamental model, or I'm unfamiliar with a DAG, but simply because I SHOULD NOT HAVE TO CARE. My job is to write software, not operate heavy revision control machinery to some arbitrary level of dvcs revision control fetish perfectionism. I don't want to hide my work from my coworkers, I don't wind to hide my work history from my coworkers, and I don't want to maintain wildly diverging branches (the cost of branches is primarily found in code divergence, not SCM headaches). Git isn't for me.
- deleted 14y ago[deleted]