Cruft and Technical Debt: A Long View
Cruft is inevitable. Whether you’re working around a bug in Internet Explorer, Heroku or Ruby 1.8, our libraries and applications quickly diverge from the platonic ideal of software. In the short-term, there’s no point in fretting. Rather than an indication of a development process gone awry, the technical debt merely …