Decoding Git Guidebook for Developers: Boost your dev skills by learning how Git's code works

Hi Git enthusiasts! A few years ago I was playing around with Git and realized that being a version control system, Git is used to track its own code. I proceeded to clone down Git's codebase and poke around. Out of curiosity, I decided to list Git's commit history in reverse order using the command "git log --reverse", which showed that Git's very first commit was made all the way back in April 2005. I checked out that commit ID into my working directory, and to my amazement, there were only 9 code files in my working directory containing just ~1000 lines of code. Granted it was C code, which I wasn't super familiar with, but being a decent Python and Java dev I felt that Git's initial codebase was small enough that I could actually understand it directly from the source code. After brushing up on my C coding skills I spent a few days perusing the code and realized that the most popular version control system on the planet had very humble beginnings. Not only is Git's original codebase manageable in size (small), but its simplicity makes it an _AMAZING_ learning resource for developers. I want to share everything I learned about how Git's code works under the hood, so I wrote the Decoding Git Guidebook for Developers. The best part is that these concepts all still apply to Git's modern version. Part 1 of the book covers Git's underlying concepts, the components that make up a Git repo, and the usage of Git's original 7 commands. Part 2 dives into each of Git's original C source code files (.c files and .h files) and uses code extracts/snippets to fully explain how Git's code works. All feedback is appreciated and let me know if you have any questions! Best, Jacob Stopak Creator, initialcommit.com jacob@initialcommit.io