Tech Weekly

About seven years ago, when I left the hustle and bustle of Hanoi to move to the outskirts and start working remotely, I built my personal portfolio using a “strange” CMS. It was all about static files and Markdown; build it once, and you get a lightning-fast static site. I.

In the world of software engineering, the best technical decision isn’t always the one backed by the most marketing budget; it’s the one that actually stays up when your users need it. For the past few months, I’ve been deep in the trenches building Mokey.me, experimenting with various AI models.

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.