"Time and Time Again"
summary
Concrete claims and code-level failures matter: calendar proposals like the 13‑month international fixed calendar add 364 weeks not 365, Hebrew months run sunset‑to‑sunset, and the Islamic year is purely lunar so Ramadan shifts yearly. Production failures include a real leap‑day bug that breaks certificate logic (Feb 28 2012 Azure outage) and mismatched epochs like Unix epoch 1970 versus Apple 2001 and Steam 2005. Recommendations are learn calendar rules, use standard libraries (call addYears not manual arithmetic), store timezone and calendar metadata.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:07Time in discussions
- 6:43Time as fourth dimension
- 10:39Measuring and perceiving time
- 11:22Calendars as tools
- 13:49Gregorian vs Julian calendars
- 15:56Financial and ISO weeks
- 16:19Hebrew and lunar calendars
- 18:26Why learn calendars
- 20:12Dangers of reinventing time
- 20:54Azure leap day bug
- 22:37Computers and epoch time
- 24:02Multiple calendars in apps
- 25:28Testing time zones
- 26:31Edge cases in time
