-
Why do some projects get to a point that they need a full refactor? 🤔 In this post, I explain how Customer Value and Technical Debt relates plus how to maintain it in a manageable state. I modeled this the problem as a system Feedback is welcomed! 😄 learnings.aleixmorgadas.dev/p/delivering-customer-value-meanwhilePermalink On twitter.com
♻️ 2 Retweets ❤️ 26 Favorites Mood 0
-
You can play with the system and simulation here insightmaker.com/insight/233175/Engineeing-Effectiveness-vs-Technical-DebtOn twitter.com
-
Twitter Thread explaining how I got into that model 👇 @aleixmorgadas/1429113218744700936?s=20Permalink On twitter.com
-
I've to admit that the post is more complex than it should be. I still need to find the real things I want to explain to simplify it. I would say that this post contains a considerable amount of accidental complexity 🤣 Will refactor as I become more proficient in the domain 💪Permalink On twitter.com
-
This thread relates a lot to Scenario 4 of the post. When Technical Debt is no longer manageable, then we start with the “Full Refactors” killing Continuous Value Delivery @johncutlefish/1429503988198625280Permalink On twitter.com