Ever shipped a “simple” feature and discovered your date/time logic is on fire? In this episode of SEEK Bytes, the crew dive into the weird, wonderful and truly painful world of time zones, UTC and daylight savings – and why getting this wrong can break products, reports and disaster recovery plans across your whole IT stack.

In this episode, we explore:

• Why time zones are way messier than you think – odd offsets, countries changing time zones overnight, multiple names for the same UTC offset, and scenarios where two people standing on the same street literally disagree on what time it is.

• How this breaks real-world systems – from expiring promo links and DR runbooks to global products that must store bookings across APAC and beyond, plus the UI pain of showing “the right” local time vs relative time for each user.

• Survival tips for developers – why standards bodies say “just store UTC + offset”, when to lean on libraries like NodaTime instead of native date objects, and how epoch timestamps, ISO 8601 formats and good packages can save you from reinventing the world’s worst wheel.

Whether you’re in software engineering, data, SRE, ops, security or any IT role that touches logs, reports, alerts or user-facing dates, this episode will change how you think about time – and probably make you a lot more cautious the next time someone says “it’s just a datetime field”.

🔔 Follow the SEEK Bytes podcast so you never miss a new episode