This week's episode is another deep-dive into a niche coding topic. This time, we're dealing with time. In short, writing code that deals with times and dates is horrible. We're here to tell you that, as a sensible developer, you should avoid it at all costs.But if you're unlucky enough to actually _have_ to programme with times and dates, what are some of the common pitfalls? What "gotchas" are lurking in the depths? And how can you deal with them in the most effective way (and hopefully not be driven insane in the process)? Find out all this and more in this week's timely instalment of A Question of Code.Mentioned in this episodeThe Problem with Time & Timezones - ComputerphileInternationalis(z)ing Code - ComputerphileWhy 2020 Started On December 30th - Tom ScottThe world's silliest time zones - Map MenDaylight Saving Time Explained - CGP Greymoment.js
No persons identified in this episode.
This episode hasn't been transcribed yet
Help us prioritize this episode for transcription by upvoting it.
Popular episodes get transcribed faster
Other recent transcribed episodes
Transcribed and ready to explore now
#2426 - Cameron Hanes & Adam Greentree
16 Dec 2025
The Joe Rogan Experience
#2425 - Ethan Hawke
11 Dec 2025
The Joe Rogan Experience
SpaceX Said to Pursue 2026 IPO
10 Dec 2025
Bloomberg Tech
Donβt Call It a Comeback
10 Dec 2025
Motley Fool Money
Japan Claims AGI, Pentagon Adopts Gemini, and MIT Designs New Medicines
10 Dec 2025
The Daily AI Show
Eric Larsen on the emergence and potential of AI in healthcare
10 Dec 2025
McKinsey on Healthcare