4 ms·
even if its not timely to implement - design the replacement right away, and update it if necessary. this helps scope the work, understand what other components
by convolvatron 9y ago
even if its not timely to implement - design the replacement right away, and update it if necessary. this helps scope the work, understand what other components are being effected, and allows related systems to be written with an eye towards the fixed version instead of the damaged one.
- j45 9y agoThat's a really good idea. We make the technical debt ticket anyways describing the problem, taking a few more minutes to describe "how it should be" so a design process can begin... it will be much easier to pick it up later on... maybe even tie it to an ongoing Technical Debt Roadmap that can be tied into the main product roadmap.
- convolvatron 9y agoi forgot the most important part, this helps makes the decision of when to actually commit to making the change. instead of setting aside bandwidth to address debt just on principle, you can make a reasoned argument that says 'new feature y would fall out naturally if we reworked x, and is going to be a disaster if we don't, so maybe we probably should'