
Modernizing Legacy Applications in PHP
by Paul M. Jones · first published 2014
8mentions
6recommended by
6HN commenters
2014–2022first – last mentioned
100% recommend
Why HN recommends it
Walks through improving a large existing PHP codebase in small, concrete steps, with examples drawn from a real project; especially useful for organizing code and getting an old application under control.
Summarised by Claude from recommending comments
Affiliate links. As an Amazon Associate I earn from qualifying purchases.



Are you already using a framework? If so which one? If not, I would check out the book Modernizing Legacy Applications In PHP by Paul M. Jones http://bit.ly/1FQjpby
on “Ask HN: PHP Directory structure and code organization” ↗While not free, Paul M Jones book Modernizing Legacy Applications in PHP has really helped me get control of a large old codebase. https://leanpub.com/mlaphp It gives examples and goes bit by bit through the process of organizing code. I'm using its suggestions along with…
on “PHP 8: Before and After” ↗First read the book: Modernizing Legacy Applications In PHP Get your code under control in a series of small, specific steps By Paul M Jones https://leanpub.com/mlaphp
on “Ask HN: Inherited the worst code and tech team I have ever seen. How to fix it?” ↗I've worked with Paul Jones in the past and he has actually modernized one of my own legacy PHP codebases. He wrote down his experiences and advice in "Modernizing Legacy Applications in PHP": https://leanpub.com/mlaphp It might be worth your time. (Edit: noir_lord also recommended the same book in this thread.)
on “Ask HN: Good resources about legacy code?” ↗There's also "Modernizing Legacy Applications in PHP": https://leanpub.com/mlaphp (but leanpub seems to be down right now lol)
on “PHP 8: Before and After” ↗It's PHP, but my book [Modernizing Legacy Applications in PHP](https://leanpub.com/mlaphp) may help -- deals with code improvement, especially the organization of that code. The examples are taken from a real codebase, though the names have been changed to protect…
on “Ask HN: A Book or Course to Learn Code Quality/Structure?” ↗I wrote Modernizing Legacy Applications in PHP for exactly this situation. https://leanpub.com/mlaphp And it's (still) free!
on “Ask HN: Inherited the worst code and tech team I have ever seen. How to fix it?” ↗…without version control is astounding. FTP-ing an entire codebase to a production directory, with the files named ".bak.1", ".bak.2", etc. is still a common thing. (For what it's worth I wrote a book on Modernizing Legacy Applications in PHP https://leanpub.com/mlaphp so this subject is close to my heart.)
on “Refactoring Large Codebases” ↗