Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
ministryoftesting.com
Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
1–10 of 29 posts
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#2These were the techniques taught to me in college in 1989 when I learned how to debug. We didn't have git back then. Sometimes taking a break helps if you get stressed out and stuck. I worked with a Marine in 1996-1997 at the ATCOM Army base who taught me that going to the snack bar and buying a soda and a bag of chips is the best way to refocus your brain on the problem. Take a walk as well.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#3It'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.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#4Is it just me or is this yet more ChatGPT output?
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#5These were the techniques taught to me in college in 1989 when I learned how to debug. We didn't have git back then. Sometimes taking a break helps if you get stressed out and stuck. I worked with a Marine in 1996-1997 at the ATCOM Army base who taught me that going to the snack bar and buying a soda and a bag of chips is the best way to refocus your brain on the problem. Take a walk as well.
Maybe the “go buy a bag of chips” is a way to force the walk to happen.
I tend to do the same though, walk away for a bit and then return to the problem. Sometimes longer breaks are needed though so I might pivot to a different problem for a while.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#6None of these debugging tips involve the use of a debugger, arguably one of the most efficient ways to debug.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#7Logging is a hack now ?
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#8It'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.
When I was trying to learn to code as a kid, I struggled for days trying to wrap my head around the concept of a variable.
I the concluded that programming isn't for me and left the bloodshed ide untouched.
Two weeks later, I was watching TV. And out of nowhere it just hit me. I finally understood what variables are! I ran to the computer to test my assumption, and it was spot on.
To this day, 20+ years later, I still remember the feeling of everything suddenly falling into place!
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#9Is it just me or is this yet more ChatGPT output?
Yea, it's full of AI slop like "It's not X, it's Y!":
> Half the bugs you chase aren’t in your code. They’re in your head.
> You’re not asking for their input, necessarily. You’re asking to have someone listen to you so you can think straight.
> The truth is in the path, not the punchline.
> The log is not your diary. It’s your surveillance system.
> Debugging isn’t just thinking. It’s re-thinking
> These 10 tips aren’t a checklist: they are a starter kit.
> Logs are your sidekick, not your saviour.
Re: Debug like a boss: 10 debugging hacks for developers, quality engineers, testers
#10Is it just me or is this yet more ChatGPT output?
Yeah I thought it was maaaybe human but this line made me think it's AI:
> Short sentence 1. Short sentence 2. That’s debugging like a boss.
No human writes like that. I suppose the average of all humans does, though :-)