While many of you were blown away by Matthew's introduction to Git, some of you asked for more. You ask, we deliver. Matthew McCullough from GitHub is back, this time to take you into the depths of Git!
Git is a version control system. We can look at it from that high level. Git is a content tracking system. Some teachers advise us to look at it from that lowered elevation. But I will...
[read more]
While many of you were blown away by Matthew's introduction to Git, some of you asked for more. You ask, we deliver. Matthew McCullough from GitHub is back, this time to take you into the depths of Git!
Git is a version control system. We can look at it from that high level. Git is a content tracking system. Some teachers advise us to look at it from that lowered elevation. But I will take you to the very bottom. The floor. The code. The algorithms. The directed acyclic graph of hashed bit sequences made efficient through LZW compression and deferred garbage collection determined by node reachability via hash relationships.
âBut why?â, you may ask. âWhy go this deep?â" Git is a tool that works so well for so many. It mystically corrects anticipated `merge` conflicts. Itâs âwhere did code come fromâ results from `blame` are impressive. The ability to re-write history through `rebase` is awesome. The globally unique identifier nature of a hash-produced ref is revolutionary.
Uber-geeks are magic-slayers. We want and need to know precisely how things work. Like a hard 50 push-up workout, this study will make working with Git at the daily developer level a fraction of the effort â