# From CakePHP to Laravel: A Framework Memoir

My framework history is not a resume line. It is sitting in public on my [GitHub](https://github.com/guywarner), in the order it actually happened.

In 2014 and 2015, I was a [CakePHP](https://cakephp.org) developer. The repos from that stretch say it plainly: cakephp-phabricator-unittest, a cacher fork, forks of the CakePHP docs. I was working inside that ecosystem, writing tests against it, and learning how a framework holds together by reading its documentation closely enough to fork it.

Then the record changes. The CakePHP repos stop, and the long [Laravel](https://laravel.com) era starts. Ten plus years of Laravel in production. Not tutorials. Not a side project I touch twice a year. Production, every day, for more than a decade.

## What CakePHP gave me

CakePHP taught me convention. Put the file where the framework expects it, name the thing what the framework expects it named, and the framework does the boring work for you. Fight the convention and you pay for it on every request after that.

That lesson never left. I still get suspicious when code is clever in a place where it could just be predictable. Predictable code is code the next person can run in their head. Most production bugs I have chased lived in the clever parts.

It also taught me to read a framework instead of just using one. Forking docs and test tooling forces that. You stop treating error messages like weather and start treating them like directions.

## What Laravel changed

Laravel kept the convention and gave me a bigger toolbox on top of it. The service container, queues, events, and a package ecosystem that rewards building small, shareable pieces instead of burying everything in one application.

That is the framework I carried into MonitorBase, where I served as Chief Technology Officer (CTO) from October 2015 to February 2025, then VP of Development until April 2026. The platform handled more than 7 million queries a month for 10,000 clients, with a team of 12 plus developers. Laravel was not the whole system, but it was the framework I was in the weeds with while that system had to stay fast and stay up.

The proof of that era is also on [GitHub](https://github.com/guywarner). The laravel-singlestore-scout package from 2024 taught Laravel Scout to search [SingleStore](https://www.singlestore.com). The older, now archived laravel-singlestore-fulltext package used MATCH against full text indexes. Neither package exists if I only claimed Laravel experience. Both exist because a production problem needed a tool, so I built the tool in the open.

One clarification, because I keep having to make it in interviews. Laravel is built on [Symfony](https://symfony.com) components, and I know that layer well through Laravel. That is not the same as claiming years in the Symfony framework itself. My depth is Laravel. I will not inflate it into something else.

## Still Laravel, different problems

The framework stayed. The problems changed.

Today I run [Eco Moving Utah](https://ecomovingutah.com), a moving tote rental business in Salt Lake County, and I built [Bin X](https://binxhq.com), the bin rental CRM and scheduling software that runs it. [Eco Moving Utah](https://ecomovingutah.com) is operator number one on [Bin X](https://binxhq.com), so the software gets tested by real bookings, real deliveries, and real pickups, not by a demo script.

The scale is smaller than MonitorBase. The standard is not. A booking system that loses a delivery date costs a real customer on a real moving day. Laravel still earns its place there for the same reason it earned it before: I can build fast in it without guessing what it will do next.

If you want the short version of my PHP career, skip my bio and read [GitHub](https://github.com/guywarner) in date order. CakePHP in 2014 and 2015, then Laravel for the decade after that. Repos do not do nostalgia and they do not do inflation. They just show the work.

Pick one framework, stay in it long enough for production to teach you the parts no tutorial covers, and let the public record back up what you claim.
