No Compromises

Factories are really useful in tests, but could they give you a false sense of security if they don't generate models exactly like a user of your application would? We talk through some benefits and cautions to think about as you're designing your factories and factory states. Share the love! Tell people on Twitter about the podcast.

What a surprise, Joel and Aaron have a different learning style. We talk through our different approaches to learning, and what we've found useful. Did you like this? We'd appreciate a review or share of the podcast

Do you like to fiddle with settings? Joel doesn't. Find out why, and hear about one example where we like deviating from the defaults. Learn more about Laravel at masteringlaravel.io

Maybe you've inherited a project and just looking at how the code is organized makes your head hurt. Before you go ripping it apart and "making it better", it can be useful to take a step back and use a more measured approach. Want us to work with your team? Book a free call to see if we can help.

You've inherited a legacy app. It's "running fine" in production, but when you add an error reporting tool, you see hundreds of errors, warnings, and notices logged each day. What do you do? Check out our books and courses at masteringlaravel.io

Can a Laravel developer learn something from the Rails or Erlang communities? We share some perspective on how to broaden your horizons, and when might be a good time in your career to do that. Download our free ebook 7 Steps to Securing Your Laravel App .

Many of us have built something we thought was "throw-away" code, only to have someone decide it's good enough to ship to production. How can you prepare for this, and avoid problems when it happens? Check out Aaron's blog and Joel's blog for even more amazing wisdom.

If you are listening to this, you probably enjoy hearing other people share what they've learned. In this episode, we turn the tables and explain why you should consider sharing what you've learned as well. Listening to us is just part of the fun. You can read what we've written too at masteringlaravel.io

How can you handle an interruption to your work, especially if it is an urgent request for help? We discuss how to do this without derailing your planned work for the day. Let us know if you have a question or topic you'd like to discuss on the show. Contact us with your suggestions, or just to tell us how great we're doing.

We walk through a recent experience where Joel was about to "burn down the world," as Aaron calls it. Instead, after doing a little exploration of the Laravel framework code, we landed on a much cleaner solution. Want some help to make your Laravel SaaS bette r? Book a free 30 minute call.

It feels good to finish a project, but before you move on, there are benefits to pausing and reflecting on what went well and what could have been better. If you're enjoying the podcast, we'd really appreciate it if you shared it with a fellow developer .

We have to ship this feature in 2 weeks! Do we have time to test? In this episode we talk through this scenario and share some benefits of testing even under the pressure of a looming deadline. Free, practical advice on how to improve your Laravel app at masteringlaravel.io

For some values, it can be tricky to know whether it's better to calculate it on the fly or when to calculate it once and store in the database. We talk through a recent scenario we bumped into, and what factors to weigh when making this decision Download our free Laravel tips ebook .

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 podcast@nocompromises.io 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