EPISODE · Jun 15, 2026 · 8 MIN
How One Engineer Fixed a Timezone Bug That Lost Millions
from The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices · host Fexingo
Episode 52 of The Software Engineering Podcast with Fexingo tells the story of a single timezone handling bug at a travel-booking company that caused a cascading failure, losing over $2 million in revenue in a single weekend. Lucas and Luna break down how one engineer—Maya Chen—discovered the root cause was a misconfigured Olson database file, and the elegant fix she deployed using a small Go service to normalize all timestamps to UTC before processing. They discuss the broader lesson: timezone bugs are insidious because they pass tests but fail in production when DST transitions hit. The episode also touches on best practices for handling time in distributed systems, including storing as epoch milliseconds, using dedicated libraries like Joda-Time or Python's pytz, and why string-based timestamps are a red flag. A cautionary tale for any engineer working with global data. #TimezoneBug #MayaChen #DSTFailure #TravelBooking #RevenueLoss #SoftwareEngineering #UTCisKing #OlsonDatabase #GoMicroservice #DistributedSystems #EpochTime #JodaTime #pytz #ProductionIncident #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineeringPodcast Keep every episode free: buymeacoffee.com/fexingo
What this episode covers
Episode 52 of The Software Engineering Podcast with Fexingo tells the story of a single timezone handling bug at a travel-booking company that caused a cascading failure, losing over $2 million in revenue in a single weekend. Lucas and Luna break down how one engineer—Maya Chen—discovered the root cause was a misconfigured Olson database file, and the elegant fix she deployed using a small Go service to normalize all timestamps to UTC before processing. They discuss the broader lesson: timezone bugs are insidious because they pass tests but fail in production when DST transitions hit. The episode also touches on best practices for handling time in distributed systems, including storing as epoch milliseconds, using dedicated libraries like Joda-Time or Python's pytz, and why string-based timestamps are a red flag. A cautionary tale for any engineer working with global data. #TimezoneBug #MayaChen #DSTFailure #TravelBooking #RevenueLoss #SoftwareEngineering #UTCisKing #OlsonDatabase #GoMicroservice #DistributedSystems #EpochTime #JodaTime #pytz #ProductionIncident #Technology #FexingoBusiness #BusinessPodcast #SoftwareEngineeringPodcast Keep every episode free: buymeacoffee.com/fexingo
NOW PLAYING
How One Engineer Fixed a Timezone Bug That Lost Millions
No transcript for this episode yet
Similar Episodes
Mar 26, 2026 ·1m
Mar 19, 2026 ·34m
Feb 18, 2026 ·11m
Feb 11, 2026 ·45m