3 ms·

I'm more on the side of the author - I really enjoy hunting down and solving very difficult/odd/surprising bugs, at least every so often. It lets me exercise my

• jolmg 7y ago
  > very difficult/odd/surprising bugs I guess it's a matter of attitude or codebase. At least at the point where I find the cause, I don't often think, "wow, that was a difficult/odd/surprising bug", I think "Wow, that was a dumb mistake someone did (perhaps me, perhaps not)" or "Wow, such a mess of code. It's no wonder this mistake was so easy to make". That is, the end of the journey or the journey itself is often one of disappointment. That's what makes it frustrating for me. It's also a matter of how refactorings are prioritized in one's organization. In the journey I end up feeling like the observed bug is just the tip of the iceberg of what needs to be fixed, but technical debt may have low prioritization, so you end up feeling disappointed of only chopping off that tip of the iceberg and leaving everything else that's submerged. As time goes by, these tips pop up more and more often, and the ice below the surface also grows. I find that demoralizing. I'll try to enjoy the journey more. I know it can be done even for our codebase because I have a coworker that seems to enjoy the bugs just like the author here. Though, sometimes I think my attitude towards bugs is the healthy one.
  • hashhar 7y ago
    I agree 100% with you. Thanks for writing it out in a better way than I ever would. I think the main cause for how we feel is the lack of focus on refactoring things and repaying tech debt within our orgs.