Door categorieën bladeren
Ontdekken
Fiverr Pro
Nederlands
$
USD
I will fix, upgrade and extend your existing PHP laravel application
Mark Atia
Over deze dienst
You have a Laravel application that works, mostly. Something is broken, something needs adding, or it is stuck on a version nobody wants to touch. That is the work I take on.
I work on existing PHP and Laravel codebases, including ones I did not write and ones with no tests, no documentation and a decade of history.
Typical work:
- Bugs that are hard to reproduce or have been living there for months
- New features built to match the conventions already in your codebase
- Laravel and PHP version upgrades, including the awkward jumps
- Query and performance problems in MySQL and Eloquent
- API integrations and endpoints
- Queues, jobs, scheduled tasks and mail
How I work: I read before I write. You get a short explanation of what was actually wrong, not just a patch, and a clean pull request rather than a zip file of changed files.
Senior full stack developer, 15+ years on production Laravel and PHP systems, including legacy applications still running on old versions. Currently working across e-commerce and retail platforms.
Send me the repo or the error and I will tell you honestly what it needs before you order.
Maak kennis met Mark Atia
Mark Atia
Senior Developer, Laravel PHP and Shopify
- Afkomstig uitAustralië
- Lid sindsaug 2026
Talen
Engels
Senior full stack developer with 15+ years building production e-commerce and web platforms. I work across two things: existing PHP and Laravel applications, including legacy codebases and version upgrades, and Shopify theme development on Online Store 2.0. Behind both sits deep Vue.js and MySQL experience and a graphic design background, so I care about the finish as much as the code.
Mijn portfolio
Veelgestelde vragen
Which Laravel and PHP versions do you work with?
Anything from Laravel 5 upward, including PHP 7.x legacy applications. Older versions are often where the interesting problems are.
Can you work on code someone else wrote?
Yes, that is most of this work. No tests and no documentation is normal and not a problem.
What access do you need?
Repository access is enough to start. For anything that needs a running environment, we can discuss what is safe to share.
What if the job is bigger than the package?
I will tell you before starting, not after. You get an honest estimate and a custom offer rather than a half-finished fix.
Will you push to my production branch?
No. I work on a branch and open a pull request. What gets merged and deployed is your call.
