Displaying episodes 31 - 60 of 105 in total
Is it ever ok to delay writing tests?
We always write tests, and can't imagine working without them. But is there ever a time where it might make sense to delay writing some tests until later in the projec...
Should an Eloquent relationship include soft-deleted records?
Show notes:Get a free ebook of Laravel security tips
Interviewing other developers like a human
Some interviewing techniques can be pretty disrespectful of the applicant's time or humanity. On today's episode we talk about some ways of approaching an interview to...
The benefits of working with other developers
Maybe you're a solo dev or working on a small team. What benefits are there in widening your circle of developers? We talk through our own personal experiences in this...
Changing our mind about queues in testing
We'll admit it: sometimes we change our mind. In this episode, we discuss how we used to setup queues in Laravel tests, and why we changed it.Show Notes00:00 Sometimes...
Too many rules?
Rules in programming can be extremely helpful, especially on a team. But is it possible to go too far with rules? We discuss a couple recent scenarios where we could h...
Keeping an open mind with other languages and tools
Before you vent some frustration on another tool or programming community, take a deep breath and think about why you're irritated? We talk about our own reactions to ...
What we look for in a package
We have such a rich ecosystem of packages in the Laravel and PHP community. But can there be too much of a good thing? What do we consider before adding a small packag...
Blogging versus tweeting
Laravel has a vibrant community of people teaching and sharing what they've learned. What makes a good tip? Should you tweet or blog or both?00:00 Why blogging is bene...
Knowing when to use new language or framework features
New PHP version! New Laravel version! So exciting! But when does it make sense to upgrade, and when does it make sense to start using new language or framework feature...
Going on a bug hunt
How can a bug be fun, and not frustrating? When you treat it like a puzzle. Let's walk through a recent bug with CSV mime type validation and go deep down the rabbit h...
Thinking about the user, even in the details
User experience is a term we hear a lot as developers, but it can mean different things depending on the context. We discuss a recent project where decisions around wh...
Why do you write your tests like that?
We discuss two "interesting" patterns we've observed in a number of Laravel projects. Let's take a step back and think about why we write tests the way we do.1:06 - On...
Avoid painting yourself into a corner
We've all been there: a thorny piece of code works, but it seems like there must be a better way to simplify it or make it more readable. We share one example when thi...
Look before you leap
Hear about some cool new tool or coding technique on Twitter? Great, jump right in and use it on your biggest production app! Or . . . maybe don't. We share some thoug...
Don't plan to do too much
Do you always finish everything you plan on doing? Probably not, very few developers do. The problem isn't always how you work. Some of it is how you plan. We discuss ...
Isolate the problem
What do you do when you're stuck? Aaron shares a tip on how he breaks down a problem when he's feeling stuck.Are you stuck with your Laravel/PHP project? We can help! ...
What should I test?
We all know we should write tests, but what should we test? Is there anything it doesn't make sense to test? We talk through a high-level approach to how we do feature...
Picking a strategy for translation in Laravel
There are different ways to structure your translation assets in Laravel. We discuss how we approached this on a recent project, and why we chose the method we did.Che...
Should a factory follow all business rules?
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...
Understanding different learning styles
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? W...
Sometimes it's good to be boring
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 maste...
What was this developer thinking??
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 u...
Should you fix all bugs in a legacy project?
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 ea...
Learning from other communities
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 ...
Uh-oh, that proof of concept is going into production. Now what?
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...
The benefits of sharing what you learn
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 consid...
How to deal with interruptions
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 ...
Should I write this weird code or is there a Laravel feature I can use instead?
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 framewor...
Take time to look back and review
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 enj...