Keeping the type hints in argument and return types makes your code easier to understand, describes intents to colleagues, and prevents bugs from sloppy type coercions. If you’re the lead, the responsibility can’t fall on your shoulders alone to make sure your team is being diligent about using them properly. Nor should you be expected to check that code will work properly during code reviews. In this month’s article, I’ll show you why you need to add PHPStan to your project and how to get the most out of it by gradually increasing its scrutiny and documenting your types accurately. We’ll also see how you can extend PHPStan to check for custom rules made to analyze your code and enforce coding practices. by Oscar Merida