In this era of “move fast and break things,” organizations often fail to consider the long-term costs of decisions made for short-term gains. When projects cut corners, lack documentation and/or tests, and are regularly changing it’s not uncommon for them to quickly become too expensive to maintain or, at the very least, technical pits of despair. Software doesn’t need to be painful, however, and a little pragmatism goes a long way towards mitigating so-called “technical debt.”