Revision control, in general, turns 2D code into 3D code. Git turns 2D code into 4D code. With great power comes great responsibility. And you have to impose ru

Revision control, in general, turns 2D code into 3D code. Git turns 2D code into 4D code. With great power comes great responsibility. And you have to impose rules on yourself regarding which areas of that power landscape you should explore and which areas to stay away from (to keep your sanity, productivity, keep the complexity under control, etc, etc). Flight rules, process workflows, protocols (both network protocols, and protocols of mission critical human activity), they all belong to the idea of limiting yourself to a set pattern of activity when dealing with something that can practically give you infinite possibilities. Because infinite possibilities give decision fatigue and analysis paralysis. By 2D code I mean code in a text editor: the two dimensions of lines and columns. By 3D code I mean: lines, columns, time (meaning commit timestamps) By 4D code I mean: lines, columns, time, time travel (you can go back to older commits and rewrite your revision history).