Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That's not even kind of all it takes.

I'd been using git for a couple months on a project on my own with no problems. I felt comfortable with it. Then I got hired at a company using it.

I wasn't even remotely prepared for the difference (and for how little I actually knew about git: addressing commits, modifying commits to make them more clear to review, moving branches around, etc). I flailed for several weeks (coworkers were always happy to help, but I prefer to try to swim on my own) before the light bulb really went off (and I'm not new to VCS or DVCS, eitherm by any stretch of the imagination).

I don't think you can really learn git until you are working with a group of people, because its not until that point that its strengths and peculiarities really show up. Especially since the UI is so cryptic.

Fwiw, I was a big mercurial fan pre-hiring. I'm now very happy that BitBucket has a git interface (I prefer BB to Github for closed-source, personal projects) as, unless there is a requirement that history not be changed in the repo, I'll be using git moving forward.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: