This post introduces a systematic method to tackle software bugs by leveraging proven techniques, just like a researcher would. This is how to become more effective and efficient software engineer
I am a serious mascot for getting tunnel-vision, I sometimes call it code blindness, because I am staring it at so much, that I forget what problem I am even trying to solve, so I will try to remind myself to follow point 4 and talk to people when I have been head down for too long.
I also need to do more of point 5 and share my learnings, I too often run off to the next problem
Systematic debugging, learning, training, or doing most things where you have a starting point and an end goal is my go-to strategy.
I tried otherwise and it never worked out: training only when I felt the need for it, learning when I felt lagging in my career development, etc. Thanks for sharing your approach Fran!
I like your high-level process to debugging! Writing tips on debugging is hard because you need to pick which level you're going to share at. There's a million different tools out there, but it also takes a step-by-step understanding of where you're at in the process to even know which one to use.
I am a serious mascot for getting tunnel-vision, I sometimes call it code blindness, because I am staring it at so much, that I forget what problem I am even trying to solve, so I will try to remind myself to follow point 4 and talk to people when I have been head down for too long.
I also need to do more of point 5 and share my learnings, I too often run off to the next problem
nice tips, Fran.
I like the book 'why programs fail' by Andreas Zeller.
It taught me systematic debugging.
I haven't read this one. I'll check it out.
Thanks for sharing, Neo!
Systematic debugging, learning, training, or doing most things where you have a starting point and an end goal is my go-to strategy.
I tried otherwise and it never worked out: training only when I felt the need for it, learning when I felt lagging in my career development, etc. Thanks for sharing your approach Fran!
I remember the advice for people looking for a job: "Apply to jobs like it's your job".
We have to take things seriously when we want to see results!
I like your high-level process to debugging! Writing tips on debugging is hard because you need to pick which level you're going to share at. There's a million different tools out there, but it also takes a step-by-step understanding of where you're at in the process to even know which one to use.
Thanks for the shout-out as well, Fran!