Less the time on debugging, but more on reading the changes
In this morning, I fell into a defect. And I assume that something is wrong in the framework since my changes is so simple. A hour past, the reason for this defect was still unresolved. I am so tried that I had to stop to take a break.
When I come back, I know I should go with another way: having a further review on my change. When I read the change, I realized there was a typo in the change which is the root of the defect.
Following are what I think out from this case:
- Debugging is not the only way to solve the issue, and it is more expensive than review (reading) the implementation. So reading the implementation before debugging.
- Don’t assume the framework is wrong before ensure your changes are right. Trust your dependence.