Tools should work for you, not boss you around

<p>PHPStan is a great tool, but if you're not careful it might push you to write code in a way you wouldn't normally write it. How can you balance a tool's strengths with your team's style of writing code?</p><p></p><ul> <li>(00:00) - We really like PHPStan </li> <li>(01:30) - Can you go too far with a tool, though? </li> <li>(03:40) - Things to consider if you're newer to Laravel or PHP </li> <li>(05:30) - PHPStan has helped us find bugs </li> <li>(06:25) - Accessing route parameters in a type-safe way </li> <li>(09:22) - Know how the tool works, to make it work for you </li> <li>(11:13) - Return types on controller actions </li> <li>(14:22) - Silly bit</li> </ul><br>Need help <a href="https://masteringlaravel.io/get-unstuck?ref=podcast">getting unstuck with a Laravel issue</a>? We can help!