I have a similar process myself. What I find to be helpful is to ask myself what, in particular, went wrong. If I have a handful of cases where "some api was us

I have a similar process myself. What I find to be helpful is to ask myself what, in particular, went wrong. If I have a handful of cases where "some api was used wrong", then I take that as a sign of a need for refactoring to make the callee easier to use. Another that I like to ask myself, is how I can use the compiler and its type checking to my advantage. As in, how can I make it more difficult for myself to make this bug again in the future? But I agree with the author's point: Nearly every bug is an opportunity to learn. You should not just fix bugs, but also to understand why they happened.