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.

You just attended a conference or finished a book/course and you're all excited to try out some new "best practice". We discuss how to balance this enthusiasm with the needs of your team and project.

* Check out masteringlaravel.io
* Download our free Laravel Tips ebook

As developers, coding is the fun part, but we share why we like to slow down and take some time to wireframe before diving into the editor

* Download our free Laravel Tips ebook

* Github Actions by Michael Heap (50% discount for podcast listeners)
* masteringlaravel.io - get a jump start on validation with our free worksheet

Check out our new website: MasteringLaravel.io

• The broken window theory of programming
• New site launch! MasteringLaravel.io