In this episode, Michael shares details from a major internal platform shift at work, including the decision to completely remove an underused public JSON API and rebuild integrations around real customer needs instead of hypothetical use cases. The conversation dives deep into Laravel Passport, Sanctum, OAuth flows, request authorisation, and some tricky edge cases around testing authenticated APIs.

Jake then broadens the conversation into AI infrastructure, local model hosting, security implications of autonomous AI systems, NVIDIA hardware demand, and the future potential of photonic processors as a solution to the growing power and cooling bottlenecks facing AI workloads.

Show links

• Laravel Passport
• Laravel Sanctum
• Laravel Passport actingAs testing helpers
• PHP enums
• PHPStan
• Larastan
• Zapier
• Claude
• NVIDIA DGX systems
• Photonic processors

Michael and Jake are joined by David Hemphill to discuss David's macOS app Gent, a task runner built on the "Ralph loop" pattern for AI-powered coding workflows.

The conversation covers how Gent takes a project requirements document (PRD), breaks it into small tasks that fit within a single context window, and runs them sequentially or in parallel using copy-on-write clones and Git worktrees.

We discuss our own evolving workflows with Claude Code, including plan mode, the "Grill Me" skill for stress-testing plans, managing context windows, and the /rewind command.

Show Links

• David Hemphill
• Gent
• Ralph loop
• Conductor
• Polyscope
• Chief
• "Grill Me" skill
• Matt Pocock / AI Hero
• Solo
• The Eternal Promise: A History of Attempts to Eliminate Programmers
• Laracon

In this episode, Michael and Jake catch up ahead of Laracon and share a wild travel story involving flight changes, third-party booking headaches, and expensive rebooking.

Jake then shares a fun personal highlight: attending the NCAA Men's Basketball Championship and watching Michigan win.

The conversation shifts into development work, where Jake dives into building a centralised system for managing failed Laravel jobs across multiple applications. He explains the challenges of aggregating failed jobs without Horizon, how they built a custom package to expose APIs for inspecting and retrying jobs, and the nuances of Laravel's queue system.

They also explore ideas for turning this work into a Laracon talk, emphasising practical, experience-driven content over purely technical deep dives.

Show Links

• Laracon AU
• Laravel Horizon
• Sentry
• Dead Letter Queue

• (00:00) - Introduction and road to episode 200
• (01:00) - Laracon plans and travel setup
• (02:00) - Flight booking disaster and schedule change
• (06:00) - Rebooking flights and unexpected costs
• (09:00) - Lessons learned with third-party bookings
• (10:00) - Michigan wins NCAA championship
• (12:30) - Midwest geography and personal background
• (12:45) - Building a centralized failed jobs system
• (15:30) - Challenges with retries and tracking failures
• (16:40) - The "Dead Letter" package and API approach
• (23:20) - Turning real-world problems into Laracon talks
• (48:20) - Wrapping up and outro