State pattern implementation of finite state machine (FSM) with Laravel
In the previous article TDD IMPLEMENTATION OF FINITE STATE MACHINE (FSM) WITH LARAVEL I discussed a basic approach for implement a Finite State Machine (FSM) on a Laravel model. In this article I will further discuss the topic by applying a more engineered approach. It involves the usage of the State pattern
My system is safe, it uses encryption. You heard/said this from time to time. Sure, but why and how is it safe? Do you really know this?
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?
Questa pagina contiene le istruzioni per predisporre tutto il necessario per partecipare al workshop del Laravelday 2021