Your mission, should you choose to accept it, is to support an application built on an older framework. Refactoring isn't an easy option. The code is untested and nowhere near best practices or standards. In this session, we'll talk about strategies for incorporating modern PHP coding practices to add features and functionality and retiring the older code in pieces. We'll review specific examples and code from a real project where we bootstrapped a legacy application that needed a lot of work to be helpful to its users and simpler for developers to maintain . We'll talk about strategies to leave the existing code in place until the new code is ready to replace it in whole or in pieces.


Comments are closed.


An absolutely great start to the session. I would like to have heard a lot more of the general principles. I got lost looking through the code examples and didn't make the connection how they tied back into the main principles.

Dani Ames at 10:49 on 17 Mar 2017

Excellent info on tools for legacy PHP apps.

Very thorough explanation of the both the business problems and the technical problems being addressed.

John K at 11:03 on 17 Mar 2017

Great talk and nice examples. Some good lessons to take to heart that are often ignored when you decided to update legacy code.

Brian Fenton at 12:52 on 17 Mar 2017

Walkthrough of how they migrated a tricky legacy app. Lots of useful tools mentioned with brief examples of each. Based on the talk name I expected this to be all about the Strangler Pattern, but it wasn't at all.

A number of acronyms and more advanced topics referenced though, possibly a middle-level talk instead? Some of the code samples assumed some framework knowledge.

Even as someone whose primary language isn't PHP, I walked away from this talk with solid action items and new knowledge. I appreciated her use of a real-world scenario to explain processes and pros/cons, and will be incorporating some of her lessons-learned the next time I work with legacy code.

Derek Binkley at 13:40 on 18 Mar 2017

I have worked with a lot of legacy apps so this talk for me was part confirmation of what I have done in the past and part a new perspective. Well done.

Woody Gilk at 15:05 on 18 Mar 2017

I think some of the container examples should come with a disclaimer not to use containers inside of applications, *except* when dealing with legacy apps. Besides that, the talk was well thought out and should really help people see how to do incremental improvement on legacy apps.

David Lim at 09:33 on 20 Mar 2017

I enjoyed hearing how another developer solved business problems alongside technical problems. I'd be interested if you touched on how to build technical wealth in addition to avoiding technical debt.

A fascinating analysis of how her team bridged the gap from a huge legacy application to modern code. I like the narrative approach Emily uses. It brings the concepts to life -- including the bumps and setbacks. Well organized and thorough.