Don't overcomplicate it.
In most case, the solution is actually quite easy.
Try simplest solution first.
Understand the problem/environment first
Understand the problem.
-- Look carefully at the logging, the symptom.
Think about it first before google search otherwise it may just lead you to totally wrong directions.
Make sure you understand the root cause and the final solution.
Troubleshooting problem is thinking what may go wrong
- how it's likely caused by this?
- how easy we can verify the assumption?
- if not likely and not easily to verify it, try/list other possible root cause/approaches first
Try different approaches
Try to ask different questions (probable solution) and google it.
Track what change you have made
Check when it stops working, and what change u have made.
But be sure to understand the problem and have tried to fix by yourself.
Provide log or any information that may help others understand the problem.
When work with others
If you are trouble shooting problems together with others, communicate with them, know each other progress, doubt, what u will try next etc. They may try different approaches that may help to get final solution.
If no progress and too late or tired, go to rest and try it later or talk with others.
Solve problem quickly and Learn from it
Solve the problem first (so the project or others can move on) then try to learn related stuff later.
Write down what to check or learn later.
Take the chance to expand your knowledge.
Think More
Think over the code/problem, try to find better solution even it's already "fixed"
Check whether the problem also happens in other places(code, different server etc), if so, fix them.
Misc
Check configuration
-- If it works in dev-line, but fails in product line.
-- Happy hacking
In most case, the solution is actually quite easy.
Try simplest solution first.
Understand the problem/environment first
Understand the problem.
-- Look carefully at the logging, the symptom.
Think about it first before google search otherwise it may just lead you to totally wrong directions.
Make sure you understand the root cause and the final solution.
Troubleshooting problem is thinking what may go wrong
- how it's likely caused by this?
- how easy we can verify the assumption?
- if not likely and not easily to verify it, try/list other possible root cause/approaches first
Try to ask different questions (probable solution) and google it.
Check when it stops working, and what change u have made.
When help others
Ask what related change they have done
Ask help from others.Ask what related change they have done
But be sure to understand the problem and have tried to fix by yourself.
Provide log or any information that may help others understand the problem.
When work with others
If you are trouble shooting problems together with others, communicate with them, know each other progress, doubt, what u will try next etc. They may try different approaches that may help to get final solution.
If no progress and too late or tired, go to rest and try it later or talk with others.
Solve problem quickly and Learn from it
Solve the problem first (so the project or others can move on) then try to learn related stuff later.
Write down what to check or learn later.
Take the chance to expand your knowledge.
Think More
Think over the code/problem, try to find better solution even it's already "fixed"
Check whether the problem also happens in other places(code, different server etc), if so, fix them.
Misc
Check configuration
-- If it works in dev-line, but fails in product line.
-- Happy hacking
