Technical Debt: How do you get out of the bottleneck?
While the article delivers nice explanations for what kind of technical dept exist, it stays very generic and hand-wavy for the solutions. Bringing &quot;microservices&quot; into the room is definitely not helpful. Ownership and setting a quality bar..., sure but how does that look like? As I developer I maybe have an idea but I also need to sell that to management. As manager I have an idea too but I need to convince my developers to strive for quality and sustainability.<p>Sometimes I wish these articles would just state: Stop sprinting<p>Also: document your decisions! If you have to write down and justify your (prudent) technical dept, you maybe catch some stuff before it&#x27;s written in code. It also makes sure more people are aware of it. Additionally, it sometimes prevents CV driven development, which imho is a big problem in tech. Overall, documentation is a very underused tool.<p>Finally: teach everyone (especially marketing) that software development is expensive, so everybody thinks twice before wishing for nice to have features done quick.