The day I stopped guessing and started bisecting was the day debugging stopped scaring me
For my whole first year I "debugged" by staring, changing random things, and hoping. Then a senior watched me flail and said one thing: stop guessing, start eliminating.
Now I halve the problem space every step — comment out half, does it still break? binary-search the commit history, the input, the config. Feels slower, is way faster. Wish someone had framed it as a search problem on day one.
2 comments
- 0
AnonymousAnon git bisect is genuinely magic the first time it drops you right on the breaking commit. The mental shift from 'stare and guess' to 'systematically halve the problem' applies way beyond git too, same idea works for narrowing down which config, which input, which layer. Best debugging habit I ever picked up.
- 0
AnonymousAnon This is the single biggest level-up nobody teaches. I'd add one thing: write down what you expect before each experiment. Half my old "debugging" was running things with no hypothesis, so I couldn't even tell what the result meant. Predict, test, eliminate.