The post tries to take a Luddite approach of avoiding a debugger and chuck it up to experience. I used print debugging in platforms where debuggers suck (mobil

The post tries to take a Luddite approach of avoiding a debugger and chuck it up to experience. I used print debugging in platforms where debuggers suck (mobile, embedded). I also understand other developers of kernels, language runtime, etc. that take that approach. In the cases I used that it was due to lack of options. Tracepoints are almost always superior to print debugging: * You can't forget them in the code before commit * You can chain them with breakpoints and each other * You can use conditional tracepoints * You don't need to recompile/restart Logging is great but it's not print debugging... It's a long term strategy and is committed to version control. * Y