This is one of those things I don't understand about about software engineering and developers lacking professionalism. Articles and handwavy comments tend to

This is one of those things I don't understand about about software engineering and developers lacking professionalism. Articles and handwavy comments tend to dismiss technical debt as a shrivelling pesky geek who keeps waxing on about how vi is better than emacs. (Someone who doesn't have a lot of influence, nor as important). Pushing techincal debt to be managed by the PO, Scrummaster, busuiness, and/or managers creates major concerns and problems with what you're producing. The passive agressive response: "well convince them" is naive and wrong. They don't care. If we've seen anything from the experiences below, they just end up hoping those days won't come. Examples: 1. Experian- I'm fairly confident that they had at last one engineer there that bitched about how much the dependencies were falling behind. If they have good ones, there would have been talk about how to automate that process. 2. Half baked products/data loss bugs - (See mongo) 3. Frequent "redesigns of projects" - There are major companies out there that have had to redo their entire product range due to this. It can't possibly be affordable. I'm sure theres lot's of lessions on the migrations. But it's a lot more expensive in the long run. Side rant: I guess if you believe that you're going to go out of business tomorrw, this is justified. My point: 1. Be a professional developer, get deep knowledge on frameworks 2. Take your time and develop correctly at the start 3. Build experience with engineering, not the latest JS library that ignores experience. 4. Actually give a shit. Venkat Subermanian made a great qoute at one time: Your code quality is a reflection about how you feel about yourself and your coworkers.