This article describes a way of implementing Strategy design pattern using a database-based runtime configuration. The approach allows to dynamically (re)configure class behavior without requiring code-based rearrangements.

Classes with a lot of lines of code are generally bad. Too many responsibilities, low cohesion, or both. However, sometimes it is not possible to make functions smaller. Reasons could be various. What can be done in this circumstance?

This page contains all the material related to the meeting series about Laravel Development held at Magneti Cowork, Palermo, Italy.

In this tutorial I will show how to define a Laravel validation rule providing a custom alias string to use in custom validation classes.