Regarding understanding unix history. I actually think that knowing the history of whatever you're working with, is good and really valuable. If you don't kno

Regarding understanding unix history. I actually think that knowing the history of whatever you're working with, is good and really valuable. If you don't know the history, you don't know how things came to be and why things are the way they are. This applies to language, code, product, organization, tools, etc. You can treat things like a blackbox and use them. They'll work for a while but every time you see something that doesn't work, you'll spend time and more time trying to figure things out. Do/Learn things once. Ask questions. Sit with people that know. Ask smart questions - http://catb.org/~esr/faqs/smart-questions.html http://catb.org/~esr/faqs/smart-questions.html I've been using git for years. But I decided to really dig into it to find out how things work. These are good links and there are actually many more good ones about git internals out there. - https://git-scm.com/book/en/v2 https://git-scm.com/book/en/v2 - https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco... - https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Po...