There's nothing wrong about "debugging with print statements".

If anything, if you're any good at it, it shows better knowledge of your program's behavior than blindly looking around in the stack on a debugger.

In fact some of the biggest name programmers use just that -- including the very people who created .

At best it's "hardcore" -- but not "bad" or anything like what's in the list. Here's some appeal to coding authority for ya:

"The most effective debugging tool is still careful thought, coupled with judiciously placed print statements." Brian Kernigham

"I don't like debuggers. Never have, probably never will." — Linus Torvalds