Where This Fits
Laravel is my primary framework and covers most new PHP work — it's what I'd recommend for a new project unless there's a specific reason not to. This page exists for the PHP work that sits outside a fresh Laravel build: maintaining or extending an older PHP application, modernizing a legacy codebase, or working with a system that predates Laravel and can't be rewritten from scratch right now.
What I Build
New PHP Applications
Built on Laravel by default — modern, maintainable, and following current PHP practices rather than patterns from a decade ago.
Legacy PHP Modernization
Bringing an older codebase up to current PHP standards incrementally, without a risky full rewrite where one isn't justified.
Maintenance & Bug Fixes
Working inside an existing PHP application — fixing what's broken, extending what's there — without assuming everything needs replacing.
Security & Performance Fixes
Diagnosing and fixing PHP performance bottlenecks and security issues in applications that are already live.
Relevant Experience
Ecommerce work has included maintaining a large production Magento platform — Magento is PHP-based, and that work involved exactly the kind of maintenance-of-an-existing-system PHP work this page covers, not just greenfield builds. See ecommerce development for more on that. For new PHP work, Laravel development covers what I'd actually recommend building on today.
An Honest Note
If you're starting a new project, I'll build it in Laravel — there's no good reason to start fresh on anything else. This page is specifically for the PHP work that isn't a clean-slate choice: an existing system that needs to keep running while it's improved.
Frequently Asked Questions
Do you work with plain PHP, or only Laravel?
Both. New projects get built in Laravel. Existing plain-PHP applications, I work within — extending, fixing, or gradually modernizing rather than assuming a rewrite is the only option.
Should I rewrite my legacy PHP app or keep maintaining it?
Depends on the app. A full rewrite is expensive and risky; often the better path is incremental modernization while the system keeps running. I'll give you an honest read after looking at what you actually have.
Can you take over an existing PHP codebase from another developer?
Yes — this is a fairly common starting point. I'll need to review the codebase first to give you a realistic sense of its condition before committing to anything.