How One Engineer Fixed a Timezone Bug That Lost Millions episode artwork

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

Episode metadata supplied by the publisher feed · Published Jun 15, 2026

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

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

NOW PLAYING

How One Engineer Fixed a Timezone Bug That Lost Millions

0:00 8:39

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

Frequently Asked Questions

How long is this episode of The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices?

This episode is 8 minutes long.

When was this The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices episode published?

This episode was published on June 15, 2026.

What is this episode about?

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...

Can I download this The Software Engineering Podcast with Fexingo: Code, Architecture, and Engineering Best Practices episode?

Yes, you can download this episode by clicking the download button on the episode player, or subscribe to the podcast in your preferred podcast app for automatic downloads.
URL copied to clipboard!