Showerthought: I watched a guy debug his code at the Kansas City library and it changed how I write my loops
I was at the downtown library in Kansas City last Tuesday and this guy next to me spent 20 minutes printing stuff at each step of his loop instead of using a debugger. He said the free library run club meets there and someone showed him print statements first, so that's just how he learned. Is it bad that I still do the print thing too, or should I finally sit down and learn the actual debugger?
I used to think print statements were just a beginner crutch and that real devs always use a debugger. Then I watched a senior guy at my old shop do the exact same thing you described, and it made me realize the goal is just finding the bug, not looking cool doing it. Learn the debugger when you actually hit something prints can't solve, but don't feel bad about printing if it still gets you there.