No Compromises

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.00:00 The value of a code review process02:53 Look at it as a learning opportunity04:06 Approaching a pull request to review it06:05 Should we make this better?07:00 Did the programmer have a reason for what they did?09:05 Everyone on the team should get their code reviewed10:25 Silly bit

Aaron and Joel talk about why they write tests and what sorts of tests they find valuable.00:00 Why do we write tests?03:05 Implied trust in packages04:15 What do you test? How do you write them?06:30 Testing the happy path07:05 Testing the "unhappy" paths08:12 It's less work than you think11:30 Testing a dumb mistake with range validators14:40 Silly bit

We discuss a couple scenarios where there's more than one way to do something, and how we think through our decision.00:00 How to pick what file to put this code in?01:51 An example of a single-action controller03:15 Should everything be single-action?04:58 How many methods on a controller is too many?06:10 Where do you put authorization logic?08:00 Consistency is important08:45 Silly bit

How do you learn a new technology? Or how do you find out what's changed in the latest version of something you already use? Aaron and Joel share some tips on what they do.00:00 So many new things to learn00:56 Importance of reading docs02:00 Reading versus doing03:45 Be curious when reading05:20 How to get hands-on practice07:30 Learning a new release of an existing tool10:15 Improve the docs!12:15 Silly bitExercises for Programmers from Pragmatic Press

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.00:00 A common pattern when a dev is stuck01:12 What is a "mental model"?02:15 A concrete example of a mental model04:30 Discussing rebase versus merge06:30 A PHP specific example for rebase07:40 Mental models for queue workers10:10 Open source helps us understand11:30 Silly bit

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.00:00 Developers want the "one true way" to do something01:45 Handling a difference of opinion02:33 Staying consistent within a project03:44 Using tools to help consistency06:00 Document your project standards07:37 Keep an open mind11:01 Choose your battles wisely12:25 Involve the whole team in the discussion13:05 Silly bit

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.00:00 Flaky tests are the worst02:12 Why randomization can lead to flaky tests03:10 A guideline on when to avoid randomization05:10 Trying to predict the future?06:15 Naming can be a guide07:15 Use factory states08:00 Another type of flaky test11:15 Silly bit

00:00 The desire to upgrade to a shiny new Laravel version02:20 I actually enjoy maintenance03:48 An analogy with cars04:30 The importance of communication05:30 Making it easier to upgrade06:30 Do you want to be on the bleeding edge?07:52 Silly bit

00:00 The thought process when you get stuck01:40 An example with CSS03:40 Tools that can help locally06:15 Using a debugger to learn about Laravel06:30 Tools that can help in a remote environment08:22 Real talk about debugging in production09:57 Troubleshooting database performance11:16 Searching the internet for an answer13:02 Silly bit

00:00 The urge to automate everything01:49 Document before you automate02:45 Weighing time spent versus time saved03:30 Automation isn't maintenance-free04:08 Types of automation05:18 The exception to the rule07:05 An example of using a command to update data08:00 Silly bit