In other words: though I acknowledge that the phenomenon described in the article is real, I sometimes feel it's just because developers accept a reality that doesn't need to be accepted.
In other words: though I acknowledge that the phenomenon described in the article is real, I sometimes feel it's just because developers accept a reality that doesn't need to be accepted.
So unless you are overworking (e.g., you work in your jira tasks AND on top of that you fix bugs) I don’t see it.
I would love to work on things that make sense like stabilising the system and all, but I work on whatever sells or whatever the EM/PM wants. These days unfortunately, shipping >>> fixing.
2. Merge the resulting fix in as part of another MR
3. In the unlikely event anyone questions you, say that you needed to make changes in that area anyway, and it'll reduce the support burden.
I don't say this to scold you, but I think most of us should keep in mind that even simple code changes incur risk and add testing requirements.