Technical Debt

Home/Tag:Technical Debt

Technical Debt – What it is and what to do about it

In spite of all that's been written on the subject of technical debt, it's still a common occurrence to see it defined as simply "bad code". Likewise, it's still common to see the solution offered being "stop writing bad code". Technical debt encompasses much more than that simplistic definition, so while "stop writing bad code"

Love Your Architecture

(Repost from: By Alexander Von Zitzewitz The single best thing you can do for the long term health, quality and maintainability of a non-trivial software system is to carefully manage and control the dependencies between its different elements and components by defining and enforcing an architectural blueprint over its lifetime. Unfortunately this is something that is rarely done

Microservice Mistakes – Complexity as a Service

Technical Empathy - the ability to see the system from the point of view of the caller of your code, not just the point of view of your code— Michael Feathers (@mfeathers) January 26, 2015 Michael Feathers' tweet about technical empathy packs a lot of wisdom into 140 characters. Lack of technical empathy can lead

Laziness as a Virtue in Software Architecture

Laziness may be one of the Seven Deadly Sins, but it can be a virtue in software development. As Matt Osbun observed: I often refer to myself as a lazy developer. Occurred to me that people might not get the reference.— Matt Osbun (@MattOsbun) February 6, 2015 Robert Heinlein noted the benefits of laziness: