How Daylight Saving Time Works — And Why 40+ Countries Skip It

Twice a year, most of North America and Europe reset their clocks. Phones update silently overnight; ovens and car dashboards stay wrong for weeks. The ritual is so entrenched that most people never ask the obvious question: why do we do this at all? The answer involves World War I energy policy, a New Zealand entomologist, and a lobbying campaign by the golf and barbecue industries — none of which are apocryphal.

What Happens During DST

In regions that observe Daylight Saving Time, clocks spring forward one hour in spring and fall back one hour in autumn. The mnemonic "spring forward, fall back" gets it right. The result is that summer evenings stay light longer by conventional clock time, while winter mornings get more usable morning light.

The exact transition dates vary by country. In the United States, clocks change on the second Sunday in March and the first Sunday in November. In Europe, the last Sunday in March and the last Sunday in October. Australia flips the calendar — its summer is the Northern Hemisphere's winter, so its clocks spring forward in October and fall back in April.

Why Was DST Created?

The popular story credits Benjamin Franklin with inventing DST. It is not quite true — Franklin wrote a satirical 1784 essay about Parisians wasting candles by sleeping late, but he never proposed changing the clocks. The first serious proposal came from New Zealand entomologist George Hudson in 1895, who wanted more daylight hours after work to collect insects.

The first national implementation was Germany in April 1916, during World War I, as a wartime energy conservation measure — less artificial light needed in long summer evenings meant less coal burned. Britain followed weeks later. The United States adopted it in 1918, then repealed it, then reinstated it during World War II, then left it to individual states until the Uniform Time Act of 1966.

The modern justification is energy savings and road safety — more daylight in the evening reduces traffic accidents and electricity use. The evidence for these benefits is weak and increasingly contested. Multiple peer-reviewed studies have found the energy savings are negligible or negative, and while evening accidents fall, morning accidents rise.

Who Observes DST?

Why Equatorial Regions Skip DST

Near the equator, daylight hours are roughly constant year-round — about 12 hours of daylight every day regardless of season. There is no significant shift to accommodate and nothing to gain by moving the clocks. Countries in tropical latitudes (roughly between 23°N and 23°S) have historically never adopted DST for this reason.

The Human and Health Cost

The spring transition — when clocks spring forward and everyone loses an hour of sleep — has measurable health consequences. Studies have found a 24% increase in heart attacks in the three days following the spring clock change, a 6% increase in traffic accidents on the Monday after the switch, and significant disruption to circadian rhythms that can take weeks to fully resolve. The fall transition, when clocks fall back and people gain an hour, has a much smaller negative effect.

DST and Software Development

• •Never store or compare local times directly around DST transitions. The "1:30 AM" that appears on a clock during the fall transition in the US can refer to two different UTC moments separated by one hour.
• •Store all timestamps in UTC and convert to local time at display time using a reliable library (Luxon, date-fns-tz, Temporal API) and IANA zone identifiers.
• •Use IANA zone names (e.g., "America/New_York") not offset strings (e.g., "UTC-5"). New York is UTC-5 in winter and UTC-4 in summer; the IANA name handles both automatically.
• •Set up server and database clocks to UTC and never change them. DST is a display concern, not a storage concern.
• •For recurring events (weekly meetings, daily reminders), decide whether they should fire at the same UTC time or the same wall-clock time after a DST change. Both have valid use cases; neither is default-obvious.
• •Test time-sensitive code with dates that straddle DST transitions — especially at 2:00 AM on the transition Sundays.