What a Legacy PHP Code Audit Should Deliver
A legacy PHP code audit should deliver evidence, prioritized risks, reproducible findings, and a modernization roadmap tied to business outcomes.
Writing
Page 2
Async Decision-Making for Remote Development Teams
Make async decision-making work for remote development teams with clear owners, proposals, response windows, and final records. Resolve decisions without endless comment threads.
Why I Switched mikelopez.com From WordPress to a Static Site
My WordPress to static site move gave mikelopez.com a $0 hosting bill, simpler maintenance, a smaller attack surface, and fast Cloudflare Pages delivery, with AI remaining optional.
Software Delivery Estimates: Plan Beyond Coding Time
Build software delivery estimates that include reviews, testing, dependencies, and release work. Use a practical worksheet to separate effort, waiting, assumptions, and forecast changes.
Legacy PHP Modernization: Refactor, Replatform, or Rewrite?
Choose a legacy PHP modernization strategy with a practical decision matrix for incremental refactoring, replatforming, and full rewrites.
How to Spot a Slipping Software Deadline Early
Spot a slipping software deadline through aging work, missed evidence, and unresolved dependencies. Use a practical risk review to make scope and date decisions while options remain.
How to Upgrade Legacy PHP With Rector One Version at a Time
Upgrade legacy PHP with Rector in controlled version steps, using dry runs, tests, static analysis, small commits, and a clear rollback path.
Remote Team Status Meetings: Cut Updates, Keep Connection
Redesign remote team status meetings around decisions, useful updates, and human connection. Test a lighter meeting rhythm that protects focus without leaving colleagues isolated.
How to Add PHPStan to a Legacy PHP Codebase
Add PHPStan to a legacy PHP codebase without blocking delivery by choosing a useful starting level, creating a baseline, and reducing it in CI.
Track Remote Development Progress Without Micromanaging
Track remote development progress with accepted outcomes, visible blockers, and useful forecasts. Build a lightweight weekly report that helps managers act without monitoring every developer.