8 ms·
the vast majority of rewrite movements I've observed or been part of are clearly, unambiguously due to the fact that: - the legacy system is a spaghetti code n
by joeblow9999 9y ago
the vast majority of rewrite movements I've observed or been part of are clearly, unambiguously due to the fact that:
- the legacy system is a spaghetti code nightmare
- with arcane and manual deployment process
- years of band-aid hacks layered over every component
- inseparable two-way dependencies across all bounded contexts
- inscrutable data structures
- nearly impossible to debug
- utterly fragile and mostly undocumented
- riddled with dead code and unused components that merely confuse the poor soul tasked with debugging
- often so intertwined with dependent systems that there's a dev "environment" shared across programmers because no one can develop on their machine.
THIS is why your programmers fantasize about a big rewrite. Every time.
- devmunchies 9y agoBoils down to not keeping entropy in check until it’s unweildy. Maintainence is as important as new feature development.
- itomato 9y agoScholars should begin emphasizing the need to refactor a number of times during the lifecycle of the software project. We're not punching decks or estimating effort in terms of KLOCs, but MIS students still learn a linear model.