Episódios
-
Have you ever struggled working with a third party on one of your developer projects? How do you handle that, keeping it professional and also still able to meet your commitments?
In today's episode of No Compromises, Aaron and Joel discuss what happened on a recent project and how they think about handling those kinds of difficulties while still having boundaries.
And if you're looking for help on your Laravel project, get in touch!
-
JSON fields can be very useful, but when is a good time to include them in your database design?
In today's episode of No Compromises, Aaron and Joel use a couple examples from recent projects to talk through reasons they would and would not use a JSON field.
(00:00) - Debating JSON fields in database design(03:06) - Configuration options: JSON vs. relational tables(07:05) - Real-world example: label customization dilemma(11:30) - Silly bit
Want a place to ask any question related to Laravel development? Check out the Mastering Laravel community. -
Estão a faltar episódios?
-
Static types and tooling have increased the quality of our apps, but sometimes certain features in your Laravel app don't play nicely with static analysis.
In today's episode, we talk about how we approach the tradeoffs around making a tool happy without changing how you write code.
(00:00) - Our approach to static analysis in a Laravel app(01:30) - Using PHPDoc inline(03:00) - When Laravel doesn't quite give you the type you want(05:00) - A different approach than inline types(06:30) - Are you just making the tool happy?(07:45) - An example of going too far(10:10) - Silly bit
Check out the newly published volumes of Laravel tips. Collect them all! -
I write a lot about testing in the Mastering Laravel newsletter. Ever wonder why it's a topic I care so much about?
In today's episode, we discuss that question and come up with a few different reasons.
(00:00) - Why do we like testing so much?(01:20) - Looking back at how we learned(02:30) - Making it easier to join a project(05:45) - Tests make you more productive(07:45) - Shifting your thinking(10:10) - Silly bit
Let us help you add tests to your project. -
What does it really mean when you say you know a particular technology? On today's episode, we discuss this using TypeScript as a specific example.
(00:00) - What does it mean to "know" something?(03:15) - Thinking about TypeScript vs strict types in PHP(05:30) - Are you fluent?(06:50) - Silly bit
Want help with your Laravel or PHP project? We really know that! -
Programmers are not shy about telling other programmers when they're wrong. But what can we learn in a situation like his? How can we be wrong with style? In this episode, Aaron and Joel talk about times they've been wrong throughout their career and what they've learned.
(00:00) - Aaron admits he was wrong(02:00) - What can I learn from this?(05:30) - Being wrong in public with style(07:00) - Being wrong throughout your career(08:45) - Two people can both be right for their context(10:10) - Silly bit
Sign up for the free Mastering Laravel newsletter and learn a little something about Laravel each day. -
We can't know everything, so throughout each day we inevitably have questions. On today's episode, we discuss different approaches we have used when we need a little help.
(00:00) - Where do you go when you need help?(01:30) - Option 1 - search engines(03:30) - Getting the most out of search results(05:00) - Option 2 - talk to AI(07:00) - Using AI in the right context(09:10) - Option 3 - talk to a person(11:30) - What if you work alone?(12:55) - Silly bit
Looking for a community of smart Laravel developers that you can ask for help? -
The dreaded bug report: this app is slow. Ok, but what is slow? I have so many questions!
In today's episode, we discuss our approach to getting more information out of that initial bug report, and a methodical approach to locate and quantify the slowness.
If you'd like help setting up tools like Xdebug profiling, send us a message.
-
Writing tests that communicate with a third party can be a little tricky, but we've found an approach that balances speed and confidence.
In today's episode, we share that approach and talk through a strategy of how frequently to run tests that talk to the outside world.
(00:00) - Why would your tests ever talk to an external service?(02:30) - What does it mean to have a separate test suite?(06:00) - Keeping them separate allows different triggers for running(07:00) - When should you run external tests?(08:30) - You can't always know when you'll break an external integration(11:00) - Check on a schedule?(13:00) - Silly bit
Would you like to take 2 - 3 minutes each day to learn a little bit about Laravel? Join for free, unsubscribe any time. -
I don't have time to write an API spec. We're not a giant team. We don't have external users of our API.
I've said all these things in the past, but in today's episode, we discuss why you should still consider writing a specification for your Laravel API.
(00:00) - Should you write a spec for your API?(01:37) - Thinking through the requirements(04:07) - What's in a spec?(06:20) - Balancing detail with moving forward(08:15) - Who is consuming the spec?(09:30) - The spec keeps you honest
Would you like to see what over 4,000 Laravel developers like about the Mastering Laravel newsletter? It's free to sign up. -
Maybe you've tried to add static analysis to your Laravel app and got scared away by all the errors.
In this episode we discuss how we like to introduce PHPStan to large, long-lived projects in a way that doesn't introduce a lot of risk or change.
Would you like help introducing Larastan to your project? That's one of many things we can help you with!
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO
-
Why isn't this working? It can be frustrating when something doesn't work as expected!
In this episode, we talk through a recent issue Joel had with sessions and oauth flows. There are a couple principles that apply more broadly.
Next time you're stuck on something, let us help!
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO
-
"Magic" methods and properties show up several places in Laravel, as well as third-party packages. They can make certain things easier and less verbose, but there is a trade off. In this episode, we discuss a few different contexts where we like and avoid magic accessors.
We'd really appreciate it if you share the show with other Laravel devs.
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO
-
Admins can do everything in the app, right? Today we discuss a couple reasons why you may want to consider not letting an admin have access to every single feature in your app.
🎉️ Episode 100 is a huge milestone for us. Thank you for listening!
This episode is sponsored by Mailtrap, an Email Delivery Platform that developers love. Try for Free at MAILTRAP.IO
-
Have you ever turned on error tracking in a long-lived app and then got overwhelmed by all the errors happening? We talk through some strategies to not get overwhelmed and make a case that you really should be monitoring this in production.
Would you like help with your legacy app? We have a ton of experience making legacy apps a joy to work within.
(00:00) - Your app should be tracking errors(02:30) - Better than just parsing logs(05:15) - Don't get overwhelmed when you first turn it on(06:00) - How to triage and prioritize(07:30) - Know about performance issues(10:30) - Silly bit -
We've talked about coding standards before, but this time we approach it from a slightly different angle. Does the way you're code is formatted affect your ability to understand it? Brains are interesting things.
Is your code slower than you'd like? We specialize in Laravel performance optimization and we can help! Contact us to discuss.
-
You launched a hobby project and then it starts to get some traction. What next? How do you get a more solid foundation under your app when it comes to database hosting? In this episode, we discuss the common phases we see a database go through during an app's life.
And if you'd love some help moving your database or tackling performance issues, give us a call!
-
Interfaces are a great tool for writing maintainable applications, but it is possible to go "too far" with abstraction. Or maybe, it's a bad use of time to write an abstraction up front before you really know you need it. We discuss some trade-offs and examples.
(00:00) - Life before interfaces in PHP(02:30) - Going too far with interfaces(04:45) - A discussion with payment gateways(07:30) - Abstracting the database as another trap(09:15) - Laravel makes good use of interfaces(10:05) - Silly bit
Need some perspective on your Laravel project? We offer a code review service. Get in touch to learn more. -
When you're writing a test it can be so tempting to just "tweak" some app code to make it easier to write that test, but we discuss why that might not be a good idea. We also talk about some app changes while writing tests that are beneficial to the overall project.
(00:00) - Sometimes changing code makes testing easier(01:30) - Different types of code changes(02:45) - An example with Laravel jobs(04:30) - A time when it's okay to change code while testing(08:50) - Avoid problems by writing tests earlier(09:30) - Silly bit
Don't "compromise" on testing. See how we can help level up your Laravel project. -
Do your eyes glaze over when someone mentions singletons or factories? We'll try to not to be boring as we explain the benefits of design patterns.
Sign up for our free Laravel newsletter and learn something new in 2 minutes or less.
- Mostrar mais
