✋ My 5-step process to debug any issue (I am faster than anyone else)
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
Debugging something broken is hard, boring, and tedious.
Many people would approach this like kids approach math problems. You hold your head with your hand. You write numbers on the paper without understanding why…
I suggest something better: Approach debugging like a scientist working in a lab.
#1 - A scientist would read the work of other researchers, rather than reinvent the wheel
When debugging a problem, don’t assume you are the first human on earth facing this kind of issue.
If you have a problem at hand, check forums like stack overflow. Check your company’s Slack channels. Also, check in search engines and LLMs.
And when you don’t have a problem at hand, keep up to date reading about the problems other companies are facing. The problems other teams in your company are facing…
Books are one of the best ways to learn patterns of what many companies face. In the system design space, I recommend the books of Alex Hu: V…
Keep reading with a 7-day free trial
Subscribe to Strategize Your Career to keep reading this post and get 7 days of free access to the full post archives.