Anti-patterns and Malpractices in Modern Software Development (2015)
I generally agree with the author, but as a software developer, I try to stay much less emotionally attached to the end-result.  If I have concerns about the long-term stability and viability of a code base, I'll raise my concerns with the project manager or whomever's making the decisions on what to prioritize.  But if they don't want to, that's their prerogative.  They're higher on the chain of command than I am.  I'm certainly not going to lose sleep over it.  When the house of cards does come crashing down and it takes two weeks to add a simple feature due to tech debt, or worse, some bug surfaces that takes down a production deployment and takes more than an hour to fix, my ass is covered.  I have an email trail raising concerns that went ignored.