We share a few rules that help guide us to determine when to manually fire an event versus when to wire up a model observer.

Make my phone buzz and download a book to make you a better Laravel developer.

Wrapping up our series on how we work, we talk through the end of a project and how to make sure there are no surprises.

Download the free security tips ebook from masteringlaravel.io.
It's not easy being green

You learned a best practice, and it served you well. Is it set in stone? Or should you be open to re-evaluate later?

Get those free e-books at masteringlaravel.io

We've all had disagreements about how to write or organize code, or how a feature should work. We share some tips on how to discuss it productively.

Be a Joel, not a Cole: masteringlaravel.io

Setting up a useful staging environment involves a number of choices. We discuss our preferred strategies and talk about why having a staging environment is a good thing.

This isn't meant to be an insult. It's actually a good thing that your project isn't completely unique, and you can benefit from what other people have already learned.

Continuing our series on "how we work", today we finally get to the dev work. How we organize it, plan it, and communicate with the project stakeholders.

I heard this site is cool: masteringlaravel.io

Aaron shares a few things that he's bumped into with policies in his apps, and we talk through some possible solutions or processes to help avoid them.

Tweet @jclermont if there's something you'd like us to discuss.

When you inherit a project, how do you draw a balance before making everything nice to work with and delivering value to the stakeholders?

Check out masteringlaravel.io

Have a question? Want us to discuss a topic? Do you like sending email to random people on the Internet?
Contact us at [email protected] for all of the above.