-
@mrksdck @kaeff I can empathize with the situation a lot. The dead middle where you cannot delete but also no huge incentive to keep investing from the business perspective. Fear is the problem here. Because it leads into different behaviours that can be more damaging than beneficial.Permalink On twitter.com
❤️ 1 Favorite Mood -10 🙁
-
@mrksdck @kaeff Some behavior that come to my mind is: - Let's invest more here in "quality" and clean code just in case. So, we start treating everything as "core" and therefore slowing down business innovation because of the exception and not the norm. This only leads into more pressurePermalink On twitter.com
-
@mrksdck @kaeff There are ways that we can minimize the outcome enough: - Clear feature boundaries so that that non-fully-core functionality is enough isolated to not disturb or affect real core. - TDD also helps a lot in this regards - Making the problem visibile for Product and businessPermalink On twitter.com
-
@mrksdck @kaeff I would start investing in cleaning when I see that it directly impacts other important stuff like - our speed in this core functionality is reduced this much because of this technical debt. We should consider cleaning it up first so that later we can go fasterPermalink On twitter.com
-
On twitter.com