Matthias' book: [ Ссылка ]
Slides: [ Ссылка ]
Legacy code bases can be improved by applying any number of refactoring techniques. You can spend hours and hours fixing the code in many ways.
You may end up with nice, clean code, but it may still not have the desired attributes of a maintainable application, like:
- The domain model should be decoupled from infrastructural implementation details, external services, and frameworks.
- All the domain logic should be easily testable, which mostly means testable in isolation.
In this talk I'll go over a few (maybe familiar) design patterns, like Entity, Application Service, and Event Dispatcher. These patterns can be used to improve the structure of legacy applications or modules. They will, even when used separately, contribute to the application's ability to evolve and be maintained in the long run. I'll show before and after code fragments, and give you practical suggestions that you can start applying immediately.
===
Matthias Noback is a professional web developer since 2003. He lives in Zeist, The Netherlands, with his girlfriend, son, and daughter. Matthias has his own web development, training and consultancy company called Noback's Office. He has a strong focus on backend development and architecture, always looking for better ways to design software. Since 2011 he's been blogging about all sorts of programming-related topics on matthiasnoback.nl.
He's published several programming books as well (most recently: "Object Design Style Guide" and "Advanced Web Application Architecture").
