> Debug like a boss
Okay.
"Bob, do you have cycles to take on this ticket? Customer says that the application is unresponsive."
Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
21–29 of 29 posts
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#22It's pretty crazy the number of times I've banged my head against the wall trying to fix something... and then I'll either step away for an hour, or just come back the next day, and I'll have it fixed in minutes. It really does work sometimes.
In my day, when you encountered a tough problem, you'd go outside and have a cigarette, and the solution would magically come to you. Thank God I quit that poison, and have since learned that a brisk walk can accomplish the same goal. But back then it was a joke amongst peers - cigarettes will solve your problems!
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#23None of these debugging tips involve the use of a debugger, arguably one of the most efficient ways to debug.
The article has slop slurping all over from it
I feel they might have replaced an AI-generated em-dash here: "Set up a short chat or team session to share your debugging tricks - what’s working, what’s not, where time gets lost."
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#24It's pretty crazy the number of times I've banged my head against the wall trying to fix something... and then I'll either step away for an hour, or just come back the next day, and I'll have it fixed in minutes. It really does work sometimes.
I was lead dev once and the unofficial "rubber duck." I'd always get called over when someone was stuck on a thorny problem, lean over their shoulder and ask them to explain it and it was always instantly "Oh! I see it now, thank you!" and I had done nothing.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#25Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#26Earlier quoted context omitted.
The article has slop slurping all over from it
The article is a bit of a "dog bites man", but itsobservations are valid. False assumptions are what caused > 50 per cent of my bugs, and for bugs in production, reasonable logging is what you need. The point with going away from the computer and letting your brain process things is good too, and the point about postmortem is spot on. I hate it when my colleagues say "fixed" without explaining how the error emerged i…
Sure, nothing in the article is wrong. But if someone has to be told most of these things, and they already are a professional developer? What were they doing when they were supposed to be learning their profession?
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#27Is it just me or is this yet more ChatGPT output?
It's like typical LinkedIn post made by tech evangelist.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#28Testers don’t debug anything. If you are a tester and you debug something, you are a developer and must be judged as a developer.
Testers investigate things, though.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#29Earlier quoted context omitted.
The article is a bit of a "dog bites man", but itsobservations are valid. False assumptions are what caused > 50 per cent of my bugs, and for bugs in production, reasonable logging is what you need. The point with going away from the computer and letting your brain process things is good too, and the point about postmortem is spot on. I hate it when my colleagues say "fixed" without explaining how the error emerged i…
Sure, nothing in the article is wrong. But if someone has to be told most of these things, and they already are a professional developer? What were they doing when they were supposed to be learning their profession?
I think it could be useful for youngsters fresh off the college, where you learn a lot of theory, but much less practice such as debugging.