Whether we’re an industry veteran or a newbie to a company, we all have to deal with the legacy system that No-one Knows, Just Works and Ain’t Broke so Don’t Fix It. But what happens when it does go wrong, or the server falls over, and suddenly that old single point of failure becomes a business priority? In this talk, Christopher will cover a variety of techniques to help you understand the cruft and ensure you can modernize it efficiently and without (much) fear.
Last active
August 29, 2018 10:40
-
-
Save choult/e0a216472cfee9ed3a295efcdc2a7711 to your computer and use it in GitHub Desktop.
Orchestrating Manoeuvres from the Dark
@luijar thanks for the tips; I was definitely going to cover Strangler, so Martin Fowler is certainly on my radar :D
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@choult I agree with the other points about distinguishing yourself from other legacy system talks. Abstract seems very broad, perhaps also offer some of the main takeaways? Also, you probably are already aware, but to me, the two bibles when dealing with legacy systems are Martin Fowler's Refactoring and Micheal Feathers' Working Effectively with Legacy Code. Perhaps those are worth a skim and see if there's something of interest.