One of the things that make legacy code so difficult to change is the fact that there are so many unknowns. In normal code, we can often assume that component boundaries are inviolate or that certain dubious coding practices are never used but as a system is handed off from team to team those tacit assurances are no longer there. In this session, Michael will discuss ways of reducing unknowns in legacy systems and imposing general rules that everyone can count on; therefore making their work with the system far more deterministic.
Target Audience: Architects, Developers
Prerequisites: project and architectural experience
You will learn:
understand how to deal with legacy systems
understand ho rule-based architecture can support