Three Kinds of Good Tech Debt
Two points I really enjoyed:<p>> Not Fixing All the Edge Cases<p>We’ve all seen bugs that occur so rarely, and fixing requires destroying some part of the original design architecture. The ability to acknowledge these types of bugs as not worth fixing is liberating.<p>> Err on the side of building too little because you can always build more later. Build things to be easy to throw away and replace;<p>I find developers tend to really dislike throw away code or temporary solutions knowing they might break in the future. If the quick hack is well documented, written in a very encapsulated and removable way, who cares about removing it later.