Something I’ve noticed about my work style: I’ll hotfix things where necessary, but I’m uncomfortable with treating hotfixes as solutions. I strongly prefer to ask why something happened and how we can change the system around it to make it impossible—all the way down to the system’s core design. (Of course, part of gaining maturity as an engineer is being able to weigh the benefits of changing a system with the cost of wranlging debt.) This is a useful way of thinking about and debugging organizational processes as well, and there you don’t have to worry about the cost of paying off debt.