3 ms·
Yep, that's a good one! My first time seeing it was on http://bash.org/?950581 http://bash.org/?950581 It comes with a nice follow up after the first 6 rules:
by hitekker 11y ago
Yep, that's a good one! My first time seeing it was on http://bash.org/?950581 http://bash.org/?950581
It comes with a nice follow up after the first 6 rules:
< MatthewWilkes> 7. svn blame
< miniwark> 8. one day we will write tests
- golergka 11y ago> < MatthewWilkes> 7. svn blame Am I the only one who runs git blame (for the commit, not the author) 20 minutes into investigating the bug and git bisect an hour in? They are excellent tools to find when and how did the bug first occur
- brad0 11y agoI do this as well. Unfortunately we're far and few between.
- klibertp 11y agoIn the "Beautiful Code" book, there is a "Beautiful Debugging" chapter. The author describes how things like `git bisect` work. I had some success convincing people to use bisect at work by pointing them to this chapter.