Tech Debt
One of the main reasons legacy modernization projects are hard is because people overvalue the hindsight an existing system offers them.
Marianne Bellotti • Kill It With Fire
Yesterday's low quality is today's encumberance, or maybe I should say that todays technical debt means we have less technical capacity to spend every day until we pay it off.
Tim Ottinger • Platitudes Of Doom
Decisions motivated by wanting to avoid rewriting code later are usually bad decisions.
Marianne Bellotti • Kill It With Fire
Hickey drew a distinction between the concepts of simple and easy . Simple is the opposite of complex, where easy is something that’s familiar to us: the term he used to describe the concept of easy that I really liked was at hand .
Lorin Hochstein • Easy Will Always Trump Simple
Technical debt is a concept taken from software development. Let’s say you’re working on a big complicated program. Robust accounting software, for example. And you need to build a new feature rapidly because customers are up your ass about it. So you build it, and it works, but the build isn’t perfect. There are bugs, it doesn’t fully enmesh with... See more
Sasha Chapin • Review: Meditation from Cold Start to Complete Mastery
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))
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))
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