Daylight saving time: why your meeting moved
A London–New York call is usually five hours apart. For a few weeks, it isn’t. Here is how to stop a calendar surprise.
Read the storyArticles on daylight saving time, leap years, ISO week numbers, Unix time and atomic clocks.
Subscribe via RSS ↗8 stories
A London–New York call is usually five hours apart. For a few weeks, it isn’t. Here is how to stop a calendar surprise.
Read the storyTomorrow is one date away. That does not always mean 86,400 seconds. The difference matters in code, travel, and everyday counting.
Read the storyWeek 53 is not a glitch. ISO week dates use a second kind of year, with its own boundary near New Year.
Read the storyThe exception to the exception explains February’s missing day—and why repeating the calendar every four years does not quite work.
Read the storyA date, a local time, and an instant are three different things. Mixing them is how a harmless form loses a day.
Read the storyAn arrival time earlier than departure is not time travel. It is two local clocks telling one story.
Read the storyTime does not stop. One particular way of storing it reaches its largest positive number.
Read the storyThe second is defined through an atom. Getting that definition onto your laptop is a different—and fascinating—problem.
Read the storyNo stories match. Try another search or category.
Original explanations with worked examples. Reference links point to the underlying standards and documentation.
Practical guides to time zones, date formats and counting days →