Pulling Up Your Legacy App By Its Bootstraps

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.

  1. Triangle PHP, March 2016
  2. NCSU Campus Developer Group, April 2016
  3. Peers Conference, April 2016, (slides)
  4. Dayton PHP, May 2016, (slides) (video)
  5. Open Source Bridge, June 2016, (slides) (audio)
  6. Chapel Hill PHP, Sept 2016, (slides)
  7. Connect.tech, Oct 2016, (slides)
  8. Sunshine PHP, Feb 2017, (slides)
  9. Midwest PHP, March 2017
  10. Lone Star PHP, April 2017
  11. Madison PHP, September 2017


What’s Your Skateboard?

User Story Mapping is a strategy where you form a team of customers, developers, and users around your project to discover the full details of your project. Your team diagrams the story of the business process and all of the events happening around it. Once you have completed discovery of these stories, your team uses strategies to view features alongside the problems they solve. It is a powerful approach that allows your team to prioritize features, based on everyone’s needs and motivations. Instead of planning our project as a building that we must build with a strong foundation, we learn to plan as if it were a vehicle. This focus delivers the Most Valuable Features to the customer by answering the question, “What’s Your Skateboard?”

  1. Madison PHP, October 2016
  2. OSCON, May 2017
  3. Workshop @ PHP[tek], May 2017
  4. We Rise, June 2017
  5. Workshop and Talk @ Dutch PHP, June 2017
  6. php[world], November 2017

Status Change: Now Using Event Sourcing

Being flexible to changes in business process makes our jobs easier, and it helps our applications adapt to those changes with minimal code changes. One of the biggest adaptations in our applications has been the addition of Event Sourcing to make a note of an Event that happened in the system. With these Events, we can affect change immediately, or even later. This is most helpful in our reporting interfaces. We can build, change, and throw away our reports very easily. This is easier than our older reports being generated by large SQL queries.

  1. Midwest PHP, March 2017
  2. Lone Star PHP, April 2017
  3. PHP[tek], May 2017
  4. PHP South Coast, June 2017
  5. Pacific Northwest PHP, September 2017