I hear the "you shouldn't have to learn how your engine works just to drive a car" argument often used to counter my insistence on learning git's internals to understand its externals.

My response: git is a tool for professionals. Racecar drivers should definitely understand how engines work. Amateur users of version control systems are using the undo and redo buttons in a Google Document. Git is a professional tool and if you're a professional then you have a professional obligation to learn your tools properly.


@sir Your arguments are sound. But not every use case calls for this kind of understanding. It would be useless for my project: I am the only one who works on the code. So git is just archival for me. There are no other developers and no users and no release cycle.

@harrison_partch disagree. An understanding of the internals of git are still very useful for solo developers. Many of the higher level tools of git are extremely helpful in a lot of different circumstances and are much easier to understand with the fundamentals in hand.

Sign in to participate in the conversation