Switching off legacy code using one Symfony command at a time

Transcript

1. Switching off legacy code using one Symfony command at a time
2. Greetings
3. Hellcome Guillaume Loulier / @Guikingone Lead developer @SensioLabs Works mainly with PHP and Rust Sometimes, I break things, especially legacy ones (and I like that)
4. Summary 01 - Legacy code is fun 02 - Migrating, a far far away dream 04 - Symfony to the rescue 05 - Wrapping up 01
5. Legacy code is fun
6. Well, it should
7. Diving into the joke Refu*toring - The process of taking a well-designed piece of code and, through a series of small, reversible changes, making it completely unmaintainable by anyone except yourself. Jason Gorman
8. Let the fun begin A legacy code is just an abandoned one that generate revenues Maintaining legacy code should be easy At least, until it breaks Never needed to migrate PHP 5 code?
9. Dealing with technical debt Technical debt is ambiguous Yesterday code is already outdated, sorry Need to migrate it? Bon chance
10. Keep dreamin’
11. I made a dream
12. Time for a wishlist Tracking, being aware of changes, updating and deleting A new interface? For which use case? What about this method arguments type? Code spread across repositories?
13. Sadly What about using a dedicated channel? Or using trigger_error? Or tools like Sentry, OpenTelemetry and many more? What if we’re in a special architecture?
14. Symfony?
15. Well…
16. The full experience Symfony brings a lot of components Could we bring them together to help us? Look at Rector, PHPStan and more! What if we could “track & switch off” files?
17. Time to “Switchoff” Built on top of Symfony components and nikic/PHP-Parser (chief kiss) Attributes for the win! Analyze, check, switch off, repeat Could be used via the CLI / CI
18. Want a demo?
19. What’s next?
20. To sum it up Handling migration is hard, not to say boring Symfony could ease the process but lack of tools Relying on a framework is a recipe for failure Each project has its own rules / flaws
21. What about switchoff? Not fully stable (for now) A Symfony bundle? (Already planned) An HTML dashboard What about a PHPStan / Rector bridge?
22. Wrapping up