|
|
|
|
|
by ajross
526 days ago
|
|
Not to complain about bisect, which is great. But IMHO it's really important to distinguish the philosophy and mindspace aspect to this book (the "rules") from the practical advice ("tools"). Someone who thinks about a problem via "which tool do I want" (c.f. "git bisect helps a lot"[1]) is going to be at a huge disadvantage to someone else coming at the same decisions via "didn't this used to work?"[2] The world is filled to the brim with tools. Trying to file away all the tools in your head just leads to madness. Embrace philosophy first. [1] Also things like "use a time travel debugger", "enable logging", etc... [2] e.g. "This state is illegal, where did it go wrong?", "What command are we trying to process here?" |
|