Hoorah! My code finally works! Now gotta remove those 1000 print statements I used to identify the bugs 😥

I usually make a stub function named debugThis(...) , then I just comment the print function once and viola!

Why not use Breakpoints. As in debugger.

@juneeighteen this is smart, but you still have remove debugthis () in the end

@zyxel oops! I should go clean up some more one day ;)

@juneeighteen I know that feeling, just today I must prepare 2projects to demo

How about to use an program that filters the statements out, like sed?

Some logging class is indeed the answer. The neatest way to set it up is a service like Sentry, Bugsnag, Rollbar, etc.

debugfunction(argument);

Then
/s/^*debugfunction(argument);*$//

I do this after finishing every class in my projects
😂

Just make your own logging method and use it. Also make some kind of config and then you can toggle logging on/off easily.
The next guy that comes to work on your code will appreciate it, especially if you use tags in your logs (related to method/task, I specify them in config).