Time & Date guides
5 articles · Browse the Time & Date tools →
Dates and times look simple until they cross a boundary: a time zone, a daylight-saving change, a leap year or a computer’s clock. These guides explain how software represents time and why the usual shortcuts fail.
The safest way to store a moment is as a count of seconds from a fixed origin. A Unix timestamp counts from 1970-01-01 00:00:00 UTC, and a signed 32-bit counter runs out at 03:14:07 UTC on 19 January 2038, the Year 2038 problem. For anything people read, ISO 8601 writes the largest unit first, as in 2026-10-17T14:30:00Z, which sorts correctly as text and cannot be confused between month-first and day-first readers. A trailing offset names the zone: 14:30:00-04:00 is the same instant as 18:30:00Z, because UTC-4 is four hours behind UTC.
Date arithmetic breaks the assumption that a day is 24 hours and a month is 30 days. A year is a leap year if it is divisible by 4, except century years unless they are divisible by 400, so 2000 was a leap year but 1900 was not. A local day can have 23 or 25 hours when clocks change. For durations, work in UTC or in whole calendar units, and convert to a local zone only for display.