Use Your Targeting Computer, Luke
I use GitX in almost every coding session. GitX behaves like a web browser in one very important way: it won't immediately reflect changes to your repository—you have to hit Cmd+R to tell it to (R)efresh its view.
You can use this to your advantage. Here's how: when you've done something on the command line, switch back to your visualizer, but don't refresh right away. Instead, try to predict how what you did will change its view. (You can even try drawing out the graph on an index card.) Then, refresh the visualizer and ask yourself: did it change in the way you expected?
If the answer is YES: Congratulations! You just learned something!
If the answer is NO: Congratulations! You're about to learn something!
Repeat this process several thousand times, and eventually you won't need to refer to the visualizer as often. (For those of you who like bad sci-fi movies, think of it as less "Use the force, Luke" and more "Usul no longer needs the weirding module.")
- About This Site
- Git Makes More Sense When You Understand X
- Example 1: Kent Beck
- Example 2: Git for Ages 4 and Up
- Example 3: Homeomorphic Endofunctors
- Example 4: LSD and Chainsaws
- The Internet Talks Back!
- Graph Theory
- Seven Bridges of Königsberg
- Places To Go, and Ways to Get There
- Nodes and Edges
- Attaching Labels to Nodes
- Attaching Labels to Edges
- Directed Versus Undirected Graphs
- Graphs and Git
- Visualizing Your Git Repository
- The Reference Reference
- Making Sense of the Display
- Garbage Collection
- Experimenting With Git
- References Make Commits Reachable
- My Humble Beginnings
- Branches as Savepoints
- Use Your Targeting Computer, Luke ←HEAD
- Testing Out Merges
- Rebase From the Ground Up
- Cherry-Picking Explained
- Using 'git cherry-pick' to Simulate 'git rebase'
- A Helpful Mnemonic for 'git rebase' Arguments
- The End