4 ms·

I don’t disagree with your principals of good code quality. I disagree that by following those principals you no longer need to use a debugger or to develop deb

I don’t disagree with your principals of good code quality. I disagree that by following those principals you no longer need to use a debugger or to develop debugging skills. Your post is harmful because it suggest to junior developers that if they must use a debugger they must be developing their software in a poor fashion. This is not true. There are many good reasons to use a debugger, including to develop software or to explore a codebase and to debug your code.

hannofcart 8y ago
> I disagree that by following those principals you no longer need to use a debugger or to develop debugging skills. Using a debugger (as in, software where you step through code) and developing "debugging skills" are entirely different things. I was only commenting on the former. > Your post is harmful because it suggest to junior developers that if they must use a debugger they must be developing their software in a poor fashion. Would it be better if I said: "if you need a debugger, you have are either mucking around in poorly written code that you inherited or you're probably doing it wrong"? > There are many good reasons to use a debugger, including to develop software or to explore a codebase and to debug your code. I concede that exploration of a codebase is a valid use of a debugger.