What are your debugging tips?

#discuss #productivity

Oldest comments (23)

Gabriel Pedroza • Jun 1 '22

Run the same code 4 more times to make sure it’s a real bug. If it is, it’s time to get the rubber ducky🐥

Ivan Pozderac • Jun 2 '22

If ducky can't help, I just ask this senior web developer for advice!

Parker Waiters • Jun 1 '22

Get systematic: Remove possible variables in the code until you can isolate the problem. This is why it's important to be disciplined with your version control so you can freely delete swaths of code without complicating your life by being in the middle of some huge edits when you're trying to do it.

Maxi Contieri • Jun 1 '22

Add a failing test.

Debug it in isolation

Daniel Schulz • Jun 1 '22

I got a few:

Breakpoints for assignment problems, loggers for flow problems.
Document your bugs, you'll see them again.
Fix a bug, then write a test for it.
Does it break the product? It's a bug. Is it just inconvinient? It's a feature request.
Talking a walk outside is a valid bugfixing strategy.

Ishaan Sheikh • Jun 1 '22

Use breakpoints.

Cesar Aguirre • Jun 1 '22

Isolate your problem
Think out loud. Talk to your rubber duck
Find how others have solved the same problem

Paula Santamaría • Jun 1 '22

Isolate the problem
Focus on solving one problem at a time
Make sure you locate the real source of the issue and not just a symptom

Marinsborg.com • Jun 1 '22

I agree with what people already wrote here. Maybe good idea would be to take pen and paper and draw what code does on more abstract level and then start with rubber duck method.