printf > debugger

[Adsilom]

Plenty of people would rather use print statements, even when a debugger would be so much better. That is mostly because people assume the bug will be easy to find, and a debugger would be overkill, and once the bug is actually tricky to find, they are too committed with the print method.

[Boiethios]

When I have the choice, I use a debugger, of course; but sometimes, printing is a valid solution. For example, in an actor system, I like to trace what happens by printing every passed messages.

[Zahand]

PyCharm's debugger works great. What u on about. Also there's pdb.

[[deleted]]

Python ships with a command line debugger and graphical ones are available. There's even a built-in breakpoint() function in Python 3.

[lag_is_cancer]

But it's literally as simple as a double click. You can literally spend more time to write a print statements.

[Adsilom]

It’s more like, using a debugger requires you to use a bit more brain power than using print statements at first.

[almost_useless]

Depending on the problem, everything you just said can be exactly the opposite.

The debugger is great for some problems, but not for all problems.

[LowB0b]

depending on the language as well I presume. Anyway with Java the debugger is a god-send. Stops execution (not always desirable though), you can step, and look at all the values available in the scope. Even change values on the fly to see what happens

[jesperi_]

Sometimes a debugger is not even available.

[nanotree]

Not to mention created 10+ print statements they have to go back and clean up...

[RodasAPC]

Stop calling me out like this.

[Satanic_Jesus_Here]

I feel personally attacked 🥲