How One Engineer Debugged a Timezone Bug That Cost a Trading Desk Millions

What this episode covers

In this episode, Lucas and Luna dive into one of software engineering's most insidious villains: the timezone bug. They focus on a real-world case from a trading desk where a subtle mismatch between UTC and local time in a cron job caused millions in losses over six months. Lucas explains why timezone bugs are uniquely hard to catch — they pass unit tests, work in staging, then fail in production at 2 AM. Luna shares how one engineer traced the issue to a single line of code using a clock-drift monitoring tool. They discuss best practices like storing times as UTC, using timezone-aware libraries, and why 'Spring Forward' and 'Fall Back' are engineering nightmares. A must-listen for anyone who has ever wondered why their scheduled tasks run at the wrong hour. #TimezoneBug #Debugging #SoftwareEngineering #TradingDesk #UTC #CronJob #DaylightSaving #ClockDrift #BestPractices #ProductionBug #TechPodcast #Engineering #FexingoBusiness #BusinessPodcast #SoftwareDevelopment #CodeQuality #IncidentResponse #Episode60 Keep every episode free: buymeacoffee.com/fexingo

PodParley-generated summary based on available episode metadata and transcript content.