Joel and Aaron unpack how they use code-coverage numbers as a starting signal rather than a finish line. They discuss realistic thresholds, choosing the right tool for each test layer, and why coverage metrics can double as negotiation leverage inside big organizations. Listen in for practical ways to decide what to test—and when to stop.

• (00:00) - Testing passion vs. shipping work
• (01:00) - Coverage tells you what’s missing
• (03:45) - Picking a baseline metric that grows
• (06:15) - Draw the line between logic and UI tests
• (12:45) - Silly bit

Joel and Aaron unpack a recent client project where the only spec was “make these two systems talk.” They share how console-level prototypes helped them clarify data mapping, test tricky scenarios, and keep the client looped in without over-building a UI. If you’ve ever had to code first and document later, this one’s for you.

• (00:00) - Bridging two APIs with minimal specs
• (03:30) - Choosing an exploratory workflow over full UI
• (06:00) - Console closures for quick, testable steps
• (09:15) - Hand-off strategy: letting others poke the prototype
• (11:45) - Silly bit

Joel and Aaron dig into Laravel’s `Stringable` class and uncover how it can silently skip Blade’s automatic HTML escaping. They explain why that’s both a convenient feature and a potential security pitfall if user input isn’t properly sanitized. You’ll hear practical ways to keep your views safe without losing the API’s fluency.

• (00:00) - Stringable can sidestep Blade escaping
• (03:45) - Dangers of outputting unsanitized HTML
• (05:45) - Defensive strategies for safe rendering
• (08:45) - Silly bit