5 ms·
A gratuitous comment if you don't mind - I would try dropping the term legacy. It tends to set an existing system in concrete and creates a mindset of leaving
by lifeisstillgood 13y ago
A gratuitous comment if you don't mind - I would try dropping the term legacy. It tends to set an existing system in concrete and creates a mindset of leaving it to pasture instead of actively refactoring and rewriting all the code existing and new, as architecture and sanity demand
in short: rip a little functionality out of the existing code and refactor everything like mad to make it a sensible cut. I have found about As much effort goes into fixing up the existing code that just got damaged as writing the new.
- anarchitect 13y agoFair comment, but in this case the situation you describe is fairly accurate as it's a system that for various reasons my team don't have full control of.