Git does have a high learning curve. And the command line tools are opaque, even to developers. Also, it forces you to have a mental model of the underlying imp

Git does have a high learning curve. And the command line tools are opaque, even to developers. Also, it forces you to have a mental model of the underlying implementation to know how to use its tools. But underneath, the concepts are pretty simple, and because it's the right simple concepts, the things you can do with it are pretty flexible, and thus powerful. Git's interface can defn be way better for the default case. But everyone and every team's workflow is different, so the inherent flexibility will always involve a little bit more complexity. And oh, it seems that he hasn't yet discovered selective commits or stashing, so staging seems like an extraneous extra step. And rewriting history seems frivolous if you work by yourself. But it makes pull-requests on open source projects way easier to manage if your commits are clean. And if you need to rollback to a working version of your production code, it helps to have clear commits too.