Are you a Laravel developer? Then you've seen this.
You open a controller and it's 300 lines long. Validation, queries, emails, if-else blocks, all in one method. You open the Blade file and it's using $data , $items and $row . What's inside them? No idea. You have to go back to the controller to find out.
Then the client says, "Can this table refresh without reloading the page?" And suddenly you're writing a JSON API, adding a JavaScript framework, setting up a build step, and building the same table a second time in JavaScript.
I've been there. Many times. In my own projects and in client projects.
Over the years I fixed these problems one by one. First I wrote AQC for queries. Then ViewModels and DTOs for views. Then the Blade Partial API for partial page updates. Then events and observers for everything that happens after a save.
One day I looked at all of them together and realised something. They all follow the same rule.
That's when I gave it a name: Atomic Laravel .
Grab a coffee.…