The real confusion starts when building a project: When should I create a Trait? When should I use an Interface? Why do Abstract Classes exist? Can’t Inheritance do everything?
Traits are for sharing common behavior across unrelated classes (e.g., User, Product, and Order can all Log), avoiding misuse of inheritance and overcoming PHP’s single-inheritance limitation.
Traits are not a Laravel feature. They are a PHP language feature. A Trait is a way to reuse methods across multiple classes. Think of it as a copy-paste helper…
This blog post is a personal recap of everything I learned while building a custom PHP MVC framework using Composer packages.
If you’re building a standalone PHP MVC framework (not Laravel), one of the easiest ways to improve code quality is adding PHPStan. It helps you catch bugs before they show up in the browser or…
Here is the overall idea how we work with illuminate packages to create custom MVC.
When building a custom PHP MVC (Model-View-Controller) framework, there are several important aspects you need to consider: routing, templating, dependency management, database interaction, input validation, and more.
When using Composer’s PSR-4 autoloading, it’s common to place multiple classes inside the same src/ directory under a single namespace.
When you use composer packages (like a framework or a router library), they typically handle the underlying logic for routing, dependency injection (DI), middleware, and other essential features for you.…
In web development, middleware is a powerful concept used to handle HTTP requests and responses. Instead of calling each middleware one by one directly, the middlewares are nested inside each…