tcopeland

Another scenario is when an acquisition occurs for the data a company has collected and so the codebases are quietly retired. In that situation there's still some value in paying down some technical debt - security updates on libraries and whatnot - but there's a point at which the decommissioning effort becomes the primary driver.

That's the truth. I had a thing come up the other day where a client wasn't including a content type header and thus the body was being interpreted as application/x-www-form-urlencoded. Rack middleware to the rescue on that one.

> I'd definitely include "Kill your dependencies" as a bullet point

Or at least your monkeypatches!

That looks great, and my local library has a copy, thanks for the pointer!