7 Debugging Tips, to Save You Hours of Troubleshooting:🧵👇
1. Understand the Data Flow
- Debugging could be a nightmare without understanding the code and how data is flowing within the system
- So understand it thoroughly before jumping into debugging
- Debugging could be a nightmare without understanding the code and how data is flowing within the system
- So understand it thoroughly before jumping into debugging
2. Pen & Paper Approach
- When debugging any complex functionality, take out a paper and write down each & every step, its input and output along with the expected outcome
- This will help debug all scenarios without losing track
- When debugging any complex functionality, take out a paper and write down each & every step, its input and output along with the expected outcome
- This will help debug all scenarios without losing track
3. Remove Unnecessary Complexity
- Complex input might lead to confusion and time wastage, that's why use the simplest form of input to debug the issue
- If required, step by step increase the complexity of your input to reach to the core issue
- Complex input might lead to confusion and time wastage, that's why use the simplest form of input to debug the issue
- If required, step by step increase the complexity of your input to reach to the core issue
4. Divide and Conquer
- Breakdown each aspect of the functionality into different parts and test them individually
For eg:
- Divide, frontend, backend, and DB logic into parts
- Test them separately to identify which part has the issue
- Focus on that part solely
- Breakdown each aspect of the functionality into different parts and test them individually
For eg:
- Divide, frontend, backend, and DB logic into parts
- Test them separately to identify which part has the issue
- Focus on that part solely
5. Online Help
- Mention the proper keyword of the error
- Read the StackOverflow (or similar sites) question properly
- See if it matches your case and then applies the solution
- Sometimes, accepted answers do not solve your question so read the comments for any hints
- Mention the proper keyword of the error
- Read the StackOverflow (or similar sites) question properly
- See if it matches your case and then applies the solution
- Sometimes, accepted answers do not solve your question so read the comments for any hints
- Try other unaccepted answers (if they match your situation)
- If required refer, to the official documentation
- If you work in a team, then calling for help within the team is again the best approach to save time
- If required refer, to the official documentation
- If you work in a team, then calling for help within the team is again the best approach to save time
That's a wrap!
Every Mon, Wed & Friday - I tweet a thread on Backend Development.
Follow me
@vikasrajputin
to read all my future threads.
Every Mon, Wed & Friday - I tweet a thread on Backend Development.
Follow me
@vikasrajputin
to read all my future threads.
Before you go, do you know?
I've also started writing on LinkedIn
I share some exclusive content there, which I never share here.
Follow me on Linkedin to stay updated with Backend content:
linkedin.com
I've also started writing on LinkedIn
I share some exclusive content there, which I never share here.
Follow me on Linkedin to stay updated with Backend content:
linkedin.com
جاري تحميل الاقتراحات...