Tech Debt
Planning too far ahead will lead to conflicts in goals and execution. Going too far too fast can lead to purposely overlooking debt or forgetting to record it. When under heavy pressure, the team might fail to care for debt sooner than later.
Vaughn Vernon • Strategic Monoliths and Microservices: Driving Innovation Using Purposeful Architecture (Addison-Wesley Signature Series (Vernon))
Know your technical debt, the understanding and management of which is key for a sustainable architecture. Lack of awareness of technical debt will eventually result in a software product that cannot respond to new feature demands in a cost-effective manner.
Murat Erder • Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps (Addison-Wesley Signature Series (Vernon))
David Pierce • Evernote’s CEO on the company’s long, tricky journey to fix itself
Tim Ottinger • Platitudes Of Doom
If someone’s complaining about legacy systems, that means they’re deep in the weeds about to start the most heinous job in web services.
Dealing with legacy systems is like swimming through maple syrup. No one’s legacy systems are in good shape. They’ve been cobbled and duct-taped together for years. The previous redesign probably entailed a quick f
Mike Monteiro • You're My Favorite Client
You’ve just described ‘technical debt’ that is not being paid down. It comes from taking shortcuts, which may make sense in the short-term. But like financial debt, the compounding interest costs grow over time. If an organization doesn’t pay down its technical debt, every calorie in the organization can be spent just paying interest, in the form o
... See moreGene Kim, Kevin Behr, • The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win
How many trips to the well we have when it comes to tech debt?
Sasha Chapin • Review: Meditation from Cold Start to Complete Mastery
Ideas related to this collection