3 ms·
OP here, thanks for the comment. This topic is on my mind at the moment because I'm having to decide which features live and die as we migrate from a legacy pl
by anarchitect 13y ago
OP here, thanks for the comment.
This topic is on my mind at the moment because I'm having to decide which features live and die as we migrate from a legacy platform to a new one. We're very keen to avoid unnecessary technical debt in that process, and to put better decision-making in place around new features as they are introduced.
- lifeisstillgood 13y agoA 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.
- tenpoundhammer 13y agoI realized that, I think my comment just got a bit off track. I thought your post was thoughtful and appropriate. Even if design were a million years in the future and as good as it could get, we still have a finite amount of time and resources so decisions have to be made.