On this week's episode Steph and Chris discuss some of characteristics and behaviors they've observed in high-performing teams, touching on pull request sizing and prioritizing code review, deploy cadence, error monitoring and response, and minimizing the number of themes being tackled by the team in parallel. They also touch on moving to Netlify and simplifying deploys, an odd edge case with 303 vs 302 status code, and the quirks of the ActiveRecord or method. This episode is brought to you by ScoutAPM (https://scoutapm.com/bikeshed). Give Scout a try for free today and Scout will donate $5 to the open source project of your choice when you deploy Netlify (https://www.netlify.com/) Netlify build plugins (https://www.netlify.com/products/build/plugins/) Git LFS (https://git-lfs.github.com/) Issue opened on Inertia for 302 vs 303s (https://github.com/inertiajs/inertia/issues/419) "Scoping .or clauses with common joins" post (https://thoughtbot.com/blog/scoping-or-clauses-with-common-joins) Derek Prior's Building a Culture of Code Review (https://www.youtube.com/watch?v=PJjmw9TRB7s) Charity Majors (https://twitter.com/mipsytipsy?lang=en) Honeycomb.io (https://www.honeycomb.io/) Become a Sponsor (https://thoughtbot.com/sponsorship) of The Bike Shed!