If you are using the debugger you probably don't understand the code

- "If you're using an IDE you probably don't know how to code"

- "If you're looking for help on the Internet you probably don't know how to code"

- etc.

Someone should make a "edgy sentence generator" like this.

This is one of these sentences that sounds controversial, but is just common sense.

Yes, if I'm debugging my code, it's doing something I don't expect, therefore I obviously don't understand it. The purpose of the debugging process is to provide enlightenment, so I may realise my stupidity and then continue on my merry way.

I have some bad news for you. You do not understand the code. Because not all code is available.
E.g.: you might want to check the value of an input variable coming from a third party service without having to recompile to log it. You do not have the code of the service so you do jot understand it.
And even if you understand the code then there is reflection, virtual functions, runnables, packaged code, remote services, segfaults...

You know what? I don't know how often I lost sleep over programs outputting only "segfault" no way to understand where they do that because logs were not available. It's not nice but in such a situation you debug or you die.

@Jilano too much I think, also it’s not a bad thing to use it or not to understand the code

@SevenDeadlyBugs it’s not about not using it, debuggers are one of the best things we have, also it’s not a crime not to understand a code

@AlmondSauce I find funny how lot of people miss understood my post :) debuggers are cool, people are cool. Understanding that we are just people is also great

You shouldn't use debuggers preferably, you should read and understand the code. Debuggers are OK as last resort, not as first means.

Reeks oversimplification and elitism.

If you don't have to use a debugger you probably code just another Todo app...