No Compromises: Recent Episodes
Joel Clermont and Aaron Saray
Two seasoned salty programming veterans talk best practices based on years of working with Laravel SaaS teams.
Developers spend a large part of their day inside an editor. For a full-featured like PHPStorm, there may be some useful features you've never noticed. We discuss a few of those.
PHPStan is a great tool, but if you're not careful it might push you to write code in a way you wouldn't normally write it. How can you balance a tool's strengths with your team's style of writing code?
- (00:00) - We really like PHPStan
- (01:30) - Can you go too far with a tool, though?
- (03:40) - Things to consider if you're newer to Laravel or PHP
- (05:30) - PHPStan has helped us find bugs
- (06:25) - Accessing route parameters in a type-safe way
- (09:22) - Know how the tool works, to make it work for you
- (11:13) - Return types on controller actions
- (14:22) - Silly bit
Need help getting unstuck with a Laravel issue? We can help!
- (00:00) - Post-conference excitement is a real thing
- (01:11) - The reality of how conferences are structured
- (03:50) - Talks share things you could do not things you should do
- (05:00) - How to apply new ideas in your daily work
- (06:08) - Specific challenges within a team
- (11:40) - Silly bit
Want to see the musical conference talk Joel mentioned?You like short things, that's why you listen to this podcast. How about a short Laravel tip in your inbox?
Programmers have opinions on things. Shocking, I know! How can we tell someone we think there's a better way to do something, without being counterproductive and causing needless confrontation?
- (00:00) - Programmers have opinions on a lot of topics
- (02:25) - Start by asking questions
- (03:45) - Get smart with leading questions
- (05:25) - Do you always have to call out something you think is wrong?
- (07:15) - Conflict doesn't mean confrontation
Need help from some seasoned Laravel devs? Don't be shy. We don't bite.
We get a bit nerdy here and dive deep on a few different ways to test record creation.
- (00:00) - We like testing
- (01:20) - One way to test creating a record
- (03:00) - Limitations of fetch the record with first()
- (05:30) - Considerations when using latest() in tests
- (07:00) - An approach for using auto-increment IDs
- (08:05) - Silly bit
Read more of our thoughts at masteringlaravel.io
Do you maintain laser focus when you work, or are you a normal human being? How do you balance use of email and social media for legitimate work reasons without going down the rabbit hole of distraction? Stop your work and listen to this episode for answers. It's not a distraction, it's an investment.
- (00:00) - Feeling the pull of distraction when trying to focus on work
- (01:30) - Email - the biggest distraction
- (03:00) - The world won't end if you keep email closed
- (06:00) - Setting expectations with others
- (07:45) - Being a hero might actually be unfair to others
- (08:20) - Productivity is really about well-being, not cranking out work
- (09:00) - Be realistic when planning
- (10:00) - Experiment and find what works for you
- (11:30) - Social media as a distraction
- (13:00) - Silly bit
The discussion of final classes was a hot topic recently. We had planned on discussing this even before it came up on Twitter, but here is our unsolicited opinion.
Is there some use case we missed? Aaron wants to hear about it.
Show notes
- (00:00) - Final classes, the hot topic on Twitter
- (01:00) - Aaron's opinion has evolved over the years
- (03:15) - Packages vs applications
- (04:00) - What about making PHPStan happy?
- (06:45) - What about reducing support burden on package maintainers?
- (10:05) - What about private properties?
- (11:15) - Aaron wants to be wrong
- (11:45) - Silly bit
Want to hire us and argue about it? Book a call
Want another set of eyes on your code? We can help! Visit our site and schedule a free call with us today.
- 00:16 The problem: this code works, but I don't like it
- 01:17 What we mean by "I don't like this code"
- 02:22 A specific example of code I didn't like
- 03:52 Code review sparks a discussion, and a solution
- 05:20 Principle: don't get locked in to your first approach
- 06:03 Principle: the benefits of code review
- 07:22 Don't be defensive, and the code reviewer isn't always right
- 08:03 Silly bit
Do you want to blindly take our advice? Great idea! Check out our book on Laravel validation rules.
Want to get notified when we release new tools, books, and articles? Sign up for our newsletter!
Check out the validation worksheet we built. It may help jump start your Laravel validation rules.
Maybe the World Destruction Tour isn't so crazy after all.
Listening to us is just part of the fun. You can read what we've written too at masteringlaravel.io
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.
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.
Download the free security tips ebook from masteringlaravel.io.
It's not easy being green
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.
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.
- Github Actions by Michael Heap (50% discount for podcast listeners)
- masteringlaravel.io - get a jump start on validation with our free worksheet
Download our free eBook of Laravel tips: A Little Bit of Laravel
Our favorite permissions package: laravel-permission
Download our free eBook of Laravel tips: A Little Bit of Laravel
Fun game to learn/practice regular expression syntax: Regex Crossword
Need help improving your testing strategy, or just need help to get your team started with testing? Setup a free consultation call.
Sign up for our Laravel tips newsletter!
Find out more about Mastering Laravel Validation Rules.
Sign up for our Laravel tips newsletter!
Find out more about Mastering Laravel Validation Rules.
Sign up for our Laravel tips newsletter!
Find out more about Mastering Laravel Validation Rules.
Sign up for our Laravel tips newsletter!
Our templates to help clients setup accounts and invite us to them.
Sign up for our Laravel tips newsletter!
Does anyone read these? Tweet @jclermont if you see this.
Some shy away from code review, not wanting to be critiqued. Aaron and Joel share some tips on how to get the most out of code reviews, and things to look for as a code reviewer.
Aaron and Joel talk about why they write tests and what sorts of tests they find valuable.
We discuss a couple scenarios where there's more than one way to do something, and how we think through our decision.
The technologies we work with are extremely detailed. Without a clear mental model of how things work together, it's easy to get lost or confused.
Disagreements and debate can sap your team's energy. We'll talk about some ways to avoid unnecessary conflicts, and how to successfully handle a difference of opinion on your team.
Croissants are great because they're flaky, but no one likes a flaky test. We share some strategies on how to make your tests more reliable.