4 ms·
it's also pretty common for naïve developers, when faced with maintaining an antiquated codebase, to advocate for tearing the whole thing out and replacing it w
by adamrezich 4y ago
it's also pretty common for naïve developers, when faced with maintaining an antiquated codebase, to advocate for tearing the whole thing out and replacing it with something new and unproven. how often is this the correct decision? well, take that logic and scale it to something the size of the economy of the United States—still think it's a good idea?
- kqr 4y agoI think it was Boeing who actually worked this out at some point in the '70s or '80s: when you need to make changes to more than X % of the software, you're better off rewriting it from scratch. I don't remember what the X was, and I can't find the reference right now, but I want to think it was somewhere in the span of 30–60 %.
- EddieDante 4y agoSo, there really is a Ripley Threshold, a point at which it's better to just take off and nuke the entire site from orbit?