Refactor data checking to cleaner implementation
Very often you find yourself in situations where you need to make your data pass some kind of checks or filters before doing something with them. This post shows how to make a first attempt approach better and cleaner
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?
![Applicazioni complesse con Laravel [GrUSP Academy - PHP Masterclass]](/storage/covers/uWiEA1xgjrjGf0TAebHHsPD6wh7Yy8Lf7fGrNCHO.png)
Questa pagina contiene le istruzioni per predisporre tutto il necessario per partecipare alla masterclass del GrUSP
This article describes a TDD (Test Driven Development) approach to implement a Finite State Machine (FSM) using PHP+Laravel. However, such method is general and could be used in the programming language of your choice.
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?