3 ms·
I agree with the author that a debugger is a poor fit for many systems. However, debugging is essential, and I think debugging by checking logs works very well
by henrik_w 8y ago
I agree with the author that a debugger is a poor fit for many systems. However, debugging is essential, and I think debugging by checking logs works very well in many cases (provided that the logging is good). Some of the advantages (over debuggers):
- Anybody can look at the logs, not just developers.
- The logs show the sequence of events, not just a snapshot.
- Feasible to do in a live system.
https://henrikwarne.com/2014/01/01/finding-bugs-debugger-versus-logging/ https://henrikwarne.com/2014/01/01/finding-bugs-debugger-ver...
- M_Bakhtiari 8y agoA debugger that doesn't support those three things is just a lousy debugger.
- seanmcdirmid 8y agoThere are many different kinds of debugging, and a debugger optimized with an interface for pinhole inspecting and stepping isn’t the best tool for logging and log processing, it is ok for them to be separate things.
- M_Bakhtiari 8y agoI never said not to log or look at logs, but a good debugger should be possible to attach to a running process, and reverse debugging can give you access to past events.
- seanmcdirmid 8y agoSure, but you are still dealing with a pinhole even if you can move that pinhole around. It isn’t a complete debugging experience, nor was it meant to be.