57: Why is time so hard to work with?

A Question of Code

Content provided by Tom Hazledine. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tom Hazledine or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

4+ y ago 31:37

MP3•Episode home

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 episode

The Problem with Time & Timezones - Computerphile
Internationalis(z)ing Code - Computerphile
Why 2020 Started On December 30th - Tom Scott
The world's silliest time zones - Map Men
Daylight Saving Time Explained - CGP Grey
moment.js

96 episodes

#Programming #Software Development #Learning To Code #Questions #Python #Tom Hazledine #Tech #Podcasting Education #Code #JavaScript