> The hardest part is not learning "obscure" git things, it's unlearning the habits and preconceived ideas about how SCMs work. I've begun to think of engineer

> The hardest part is not learning "obscure" git things, it's unlearning the habits and preconceived ideas about how SCMs work. I've begun to think of engineer's ability to "get Git" as a sort of abstract-thinking FizzBuzz. DVCS breaks up some composite actions (svn commit/checkout) into their component parts (git fetch/merge/commit/push). If you can't make that mental leap and see the value in it (and accompanying tradeoffs) despite all the learning materials out there, how can you be expected to derive comparable evolutions of design and engineer on your own?