It's about time
summary
A rapid tour of concrete hazards and fixes: Gregorian quirks create Feb 30th and shifted Revolution dates, historical offsets force Los Angeles local mean time math, AOL’s billion‑second bug and the 2038 epoch bug show hard deadlines, leap seconds and DST transitions break naive arithmetic. Practical prescriptions include using Python’s datetime with pytz for localization and normalization, prefer ISO‑8601 in logs, always store and display year plus explicit timezone, and treat parsers like dateutil/arrow as heuristics with documented assumptions.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:49The Gregorian Calendar
- 9:07Date Time Module
- 9:56How Old Is Stephen Hawking
- 12:03Why Is a Whole Database Format Needed
- 14:28Local Mean Time
- 15:36Parsing Dates from Text
- 19:54Leap Seconds
- 22:50Summary
- 23:24Unicode Handling
related talks
32mIt's about time
28m"Time and Time Again"
18mManaging Time like a Time Lord: It's bigger on the inside
38mA Matter of Time
32mYou Depend on Time, This Is How It Works and You Won’t...
41mimport time_travel: A Primer on Timezones in Python
44mDates and Times on the Horizon? Run… or Come Learn All the Traps That...
52mIt's about time