Tech Weekly

After years of developing with Laravel, I noticed a frustrating pattern. No matter how unique a project seemed, the foundation remained the same: Authentication, Dashboards, Tables, Forms, and Permissions. I found myself rebuilding these structures over and over. Sometimes I did it faster, sometimes cleaner—but I was still rebuilding. Eventually,.

For years, working with Eloquent models in Laravel meant relying heavily on configuration arrays like $fillable and $casts. They worked, and they became part of how most developers approached model design. But if we’re honest, they always felt a bit disconnected from the language itself. They weren’t really code. They.

PHP still gets mocked at tech conferences. At the same time, PHP still powers around 77% of websites that use a known server-side language. Both of those things are true in 2026. And that gap says more about perception than reality. A 14-Year Perspective I’ve been writing PHP for more.

Recently, Cloudflare introduced a new open-source CMS called EmDash, describing it as a “spiritual successor” to WordPress. That alone is a bold statement, especially considering WordPress still powers more than 40% of the web. But what caught my attention wasn’t the ambition. It was the reason behind it. The Problem.

Over the years, I’ve deployed a lot of projects. Small client websites, Laravel apps, WordPress installs, internal tools… and almost every time, the process looked similar. Spin up a VPS, install a stack, configure domains, set up backups, tweak security, and repeat. It worked, but it was never smooth. Every.