Amy J. Ko

> I think it would be beneficial to provide concrete examples of each debugging technique. I know some were provided, but perhaps a running example on the same project could...

> Something I want to learn more about is Failures. The article separates failures from defects and faults by defining failures as: "a failure is a program behavior that is...

> This final chapter of the textbook on debugging was very well explained and detailed. Amy explains very well when it comes to what debugging is and the various strategies...

> 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...

> I would have liked to know more about the pros and cons to the different ways of debugging.  Is there a time the slower method would be preferred and...

> One thing I was curious about is how might a company encourage custom service interactions when something goes wrong? In the reading, it seems like companies mostly rely on...

> After reading the chapter, I am curious if there are ethics software developers should think of when creating systems to monitor applications. Are there situations where monitoring is more...

> As I read the chapter, I began to wonder how monitoring would have solved the problem presented in the first few paragraphs. I may have misread the chapter, but...

> After reading the chapter, the critique that I would like to give to this chapter is how monitoring could be easier for smaller companies? I could see how big...

> A question I would like the chapter to answer is how to train people to produce reliable, precise information for failure reproduction. I feel like the chapter skims through...