How clear coding rules can free up your team

Have the debate once, then move on

Joel Clermont
Joel Clermont

It's no secret. I'm a fan of rules.

I find them useful because they free teams from needing to make a lot of decisions or invite a lot of unproductive debate, especially on trivial things.

This is especially useful with an endlessly-flexible framework like Laravel, where there are multiple ways to make something work.

Even better, a rule should be so well-defined that you can implement it with tooling. This way the rules can be enforced and applied automatically, long before a human code reviewer needs to take a look.

A truly great rule should also come with the "why". Why did we decide to write code this way? What makes it preferred to a different way of writing it? Having a reason is easier to remember and makes it feel less arbitrary.

The next time you find yourself in a debate about code, consider if it could be solved by having the debate one time, and then enforcing a rule automatically.

Here to help,


P.S. Don't leave security as an after-thought in your Laravel application. Download our free ebook: 7 Steps to a Secure Laravel App.

Toss a coin in the jar if you found this helpful.
Want a tip like this in your inbox every weekday? Sign up below 👇🏼

Level up your Laravel skills!

Each 2-minute email has real-world advice you can use.