Displaying episodes 1 - 30 of 51 in total
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.
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?
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.
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.
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.
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.
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.
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
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.
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.
You learned a best practice, and it served you well. Is it set in stone? Or should you be open to re-evaluate later?
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.
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.
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.
When you inherit a project, how do you draw a balance before making everything nice to work with and delivering value to the stakeholders?
Is all technical debt bad? Can it serve a valuable purpose? We share our opinions along with some tips on how to be strategic when paying down technical debt in your project.
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.
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
Maybe "continuous integration" sounds like a complex thing to setup. We explain why it doesn't have to be, how to start small, and what the benefits are.
So someone has asked you to build an app, or add a feature to an app. How do you decide exactly what to build and how much to charge? We share our approach to these important questions in this episode.
Logs and error trackers are a vital tool for maintaining a production app. But if you're not careful, they can get so noisy they stop providing value. We discuss a few reasons why this is the case and our strategy for avoiding this problem.
This episode is a little different. We take a peek behind the scenes as to how we qualify projects, and the sorts of things you might think about before deciding whether or not to take on something new.
Roles and permissions are a core part of most applications. Laravel provides some tools for managing and enforcing this, and third party packages provide even more features. Aaron and Joel share their techniques for enforcing roles and permissions, in a way that won't get harder to manage over time.
When you're building a Laravel app, you're writing PHP code, but you're dealing with many patterns and conveniences provided by Laravel. So where do you draw the line between the two? Is it important? We discuss this topic and how you can get the most out of what both PHP and Laravel have to offer.
> Developer: "I just need to SSH in real quick" > Server admin: "No" Have you had this discussion? Listen in as Joel and Aaron talk about their experience on teams of different sizes, and how to handle this potential conflict, while still getting your work done.
Where should I place this curly brace? Trailing commas or not? Have you encountered disagreements about coding standards on your team. In this episode we explain the benefits of coding standards, how to adopt them on your project, and discuss the two most popular tools in the PHP community for enforcing them.
We've all been stuck with something we didn't know. Should you ask for help? And how? Or if someone on your team asks you a question, how can you handle it best? We discuss it all.