Regarding 7, I think you should explicitly mention "git bisect" and similar tools. (Or, are you doing that step by hand?!) For me, when I run out of ideas, "gi

Regarding 7, I think you should explicitly mention "git bisect" and similar tools. (Or, are you doing that step by hand?!) For me, when I run out of ideas, "git bisect" is the most efficient debugging tool. On success, it allows me to pin down the exact commit that introduced the bug. It is very fast to do (binary search), and on success it narrows the bug down to a relatively small amount code to check. Of course, this only works if you have a clean code history: small commits and always a working state after each commit. That is, no intermediate crap commits, and no monster commits doing 3 things at once.