> Sometimes though, the path it takes for the code to reach the part I'm interested in can be pretty obscure. It's in these cases that the debugger truly shines

> Sometimes though, the path it takes for the code to reach the part I'm interested in can be pretty obscure. It's in these cases that the debugger truly shines. I feel that it is the opposite. It is where the path is obscure that logging works really well. It can be iteratively refined and repeated.