Nick Tune 🇺🇦<p>Should you create a separate team to work on modernizing the legacy monolith while other teams focus on building new features outside the legacy?</p><p>This is a topic I've discussed on multiple occasions recently, and it's not an uncommon modernization question in general.</p><p>I'm generally cautious of this approach because...</p><p>1/n</p><p><a href="https://hachyderm.io/tags/architectureModernization" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>architectureModernization</span></a> <a href="https://hachyderm.io/tags/legacyRefactoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>legacyRefactoring</span></a> <a href="https://hachyderm.io/tags/softwareArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>softwareArchitecture</span></a> <a href="https://hachyderm.io/tags/ddd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ddd</span></a> <a href="https://hachyderm.io/tags/domainDrivenDesign" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>domainDrivenDesign</span></a></p>