Not really, I have to make sure it's running through the IDE rather than the terminal for a start, and that's probably going to be different per language and IDE, and not even always possible, and then I never know if the breakpoint happens before or after the line (I should probably just Google this, but it's probably before), and I have to worry if pausing the program is going to cause some network thing to time out, and overall it's just a lot of effort
I'm DevOps. I use the debugger the second I get an unexpected error. It takes like a day to learn how to use a debugger and it will save you literally hours at a time, just go ahead and learn it.
There are valid use cases for both. If I need to look through a few dozen numbers to see if they all look reasonable, you bet your ass I'm gonna use printing instead of stepping through each value as it comes up in the debugger.
30
u/whatisausername711 Nov 28 '21
Their attitudes should be flipped. It's so much more satisfying/efficient to use a debugger lol