Podcast: Time Keeps on Slipping

Did a leap year trip up Robinhood? Why does Postgres know so much about ancient calendars? And how do you pronounce char?

Article hero image

This week we discuss the many reasons "time" always trips up programmers. Plus, a deep dive into Docker, GUIDs, and Paul's patented approach to radical pander.

Note: for those looking to avoid the topic, this episode was recorded several weeks prior to publication and is free of any pandemic conversation.

When Robinhood went down at the beginning of March, many speculated it might have been caused by an extra day, February 29th. This is a leap year after all. Robinhood blamed the outage on an unprecedented spike in usage. Either way, it go us thinking about time.

For example, Postgres has a great understanding of time as a database. Like, it really knows all the different things that happened going back to literally year 4,000 BC including years that were skipped when they re-crafted the calendar and just like bananas stuff that happens with calendars over time. An excellent source of truth if it fits with your project.

Next up, a user shared the story of a wild interaction between Docker and the driver used by Razor peripherals. You can't have your fancy gaming mouse fired up and also be working on some container orchestration. Apparently they request the same GUID and get a bit confused if one already exists.

If you're still feeling a little uncertain about exactly how Docker/Kubernetes works, Paul suggests this lovely illustrated guide for children or this comic, which is for grown ups.

We chat about MySpace and whether it was ever cutting edge during its rise to prominence?

Last, we dive into the pronunciation of "char", by the end of which, half of us have turned into full blown pirate impersonators.

Login with your stackoverflow.com account to take part in the discussion.