Red Flags Signaling That a Rebuild Will Fail

Re:Red Flags Signaling That a Rebuild Will Fail by hvidgaard on Thursday July 12, 2018 @03:20AM (#17512807)

> I’ve always been a big believer in rebuilding your product from the ground up. I think it’s something you should always have going on in the background. Just a couple of devs whose job it is to try and rebuild your thing from scratch.

Their time is much better spend working on improving the "legacy" codebase. Simple refactoring and splitting the codebase in a modular fashion, mean you can work on limited parts of the system in isolation. This makes incremental improvements and switch to new tech much easier, and certainly less risky than a rewrite.

[ Parent | on HN ]

Re:Red Flags Signaling That a Rebuild Will Fail by spronkey on Thursday July 12, 2018 @07:49AM (#17513637)

Depending on how heavily coupled the legacy codebase is, "Simple refactoring" really may not cut it.

I mean, you can write a bunch of pinning tests, then try to prise out various bits and pieces, sure.

But what if all the stuff you're trying to prise out can now be accomplished with a few open source libraries that didn't exist way back, with a very simple rewrite of your business logic on the top?

That's a situation I've encountered quite a few times - a lot of legacy code that's largely boilerplate, with business logic drizzled over the lot, oozing into the little cracks.

[ Parent | on HN ]