Today is a great day: you will begin to develop the new greenfield project of the soon-very-successful startup you work for, as a PHP Ninja Wizard of the Crown. But wait! You're teaming with Dave, your colleague developer! He's creating an Anemic Domain Model! Why? Is it that bad?
Oh no! You're working on an application which is as messy as your flat! You don't understand anything, every bug takes weeks to fix. You need to improve the quality of your PHP code... but how? What tool to use? A hoover? Don't worry, dear reader, I have some answers for you.
The DRY principle (Don't Repeat Yourself) is easy to understand but difficult to apply. Should we never repeat our code? What was the true purpose of the principle's authors? Let's decipher what should be DRY in our code, and what should not.
What are the traps you can fall into, using PHP 7.2? Should you use everything implemented in this new version? Don't introduce ambiguity in your codebase: everything in PHP is not necessarily good to use.
I can see you spitting your cereals in front of you computer. 'What? A PHP IDE with Vim? Are you insane?'. If I am, I'm not the only one: many developers use Vim, why not PHP developers? This article will describe everything you need for you to build your own personal IDE, which fits your way of working and answers your specific needs.