Debugging: elaborate on fixing

[amyjko]

Something that I think the chapter can do a better job at explaining is fixing defects. I think that the chapter lacks in being more specific about the types of circumstances that they are trying to explain. The section list two examples of circumstances that can result in a difference in developer response in fixing defects, however, what I think could improve this is by giving a specific example of a personal example or company example explaining why developers would choose to either not fix a defect or wait until later. Maybe an example of a personal app being launched on the app store or a company re-launching their website.

This chapter does a great job of defining ways to debug step by step. One question I have is how developers decide whether to fix defects or not. In the reading it says that developers may know there is a defect but if they’re near a release they may not even fix it because it's too risky. How do they determine the harms and benefits to figure out what to do? Do they just not fix it because they hope that the defect may not actually be executed?