Your calendrical fallacy is thinking…
Days are 86,400 seconds long
False. Even if you live in a place that doesn’t have Daylight Saving Time, you are still subject to rogue leap seconds that get inserted into our calendars every now and then. If you care about being precise, you care about leap seconds. And if you’re writing software for others to use, chances are at least one of your users will be affected by DST at some point.
Days are 24 hours long
False. Many places around the world observe Daylight Saving Time, which means that people living in these locations will sometimes experience 23 hour days (when they “leap forward”) and 25 hour days (when they “leap back”).
An hour will never occur twice in a single day
False. On days when we “leap back” for the Daylight Saving Time shift, one hour occurs twice. For example, in the United States, the hour that occurs twice is the 1 AM hour. This means that on these “fall back” days, correctly-implemented clocks will go from 1:58 … 1:59 … 1:00 … 1:01 … … 1:59 … 2:00 … 2:01 …
This leads to some interesting questions: If a user has set an alarm to wake up at 1 AM on that day, what happens? Does the alarm go off the hour after the midnight hour? Or does it go off during the hour before 2 AM? Or does it go off twice? Or do you just give up and not make the alarm go off at all and make your users miss their dead-of-night appointment?
Every day has a midnight
False. Some countries, like Chile and Iran, perform their DST “leap forward” transition at midnight, which means that 11:59 PM is followed by 1:00 AM. Other countries have historically done the same, like Romania until 1996 and Brazil until 2018.
So if you’re writing code and are trying to use the time
00:00:00 to represent “no time”, you will be wrong in these countries.
Days start at midnight (or as close to it as possible)
Mostly true. For the sake of simplifying calculations and establishing conventions, the day-to-day rollover happens at midnight. However, the Hebrew calendar traditionally starts its days at sunset.
Saturday and Sunday are the weekend
False. Most Muslim countries use either Thursday and Friday, or Friday and Saturday as their weekend.
Weeks start on Sunday
False. Weeks start on Sunday in the United States, Monday in Europe, and a couple of places start on Saturday.
Days in a work week are always contiguous
False. In Brunei, the work week is Monday - Thursday and Saturday.
Everyone uses the Gregorian calendar
False. Many places in Africa use one of the various Coptic calendars. Israel uses the Hebrew calendar for determining holidays. The Islamic calendar is used all through the Middle East and other predominantly Muslim countries. Thailand uses the Buddhist calendar. Japan uses the Japanese Imperial calendar for official state business.
Months always have 30 or 31 days in them
False. February. Duh.
OK… Months always have at least 28 days in them
False. The month Pi Kogi Enavot in the Coptic calendar only has 5 or 6 days in it (depending on the year).
Month lengths follow regular cycles
Mostly true, but specifically false. Traditional Islamic calendars base their months on local observations of the moon. Sighting the moon determines whether the month will be 29 or 30 days long. However, since you can’t know ahead of time if the moon will be visible (for example: extreme cloud cover), it’s not always possible to know ahead of time how long the month will be.
A week is always seven days
Currently true, but historically false. A couple of out-of-use calendars, like the Decimal calendar and the Egyptian calendar had weeks that were 7, 8, or even 10 days.
The current year is 2020
False. It’s the year 5780 in the Hebrew calendar.
All the important years are four digits long
False. It’s the year Reiwa 1 in the Japanese calendar.
In a range of hours, an hour will not be missing in the middle of it
False. When the “leap forward” transition happens for Daylight Saving Time, an hour is missing. In the US, this is the 2 AM hour, which means that time goes from 1:58 … 1:59 … 3:00 … 3:01 …
In a range of days, a day will not be missing in the middle of it
False. In 1582, the transition from the Julian to Gregorian calendars meant that there was about a week and a half that was missing for various locations around Europe. That same switch happened in the United States in 1752.
Additionally, in 2011, Samoa decided to jump “ahead” a full day in order to move to the west side of the International Date Line (previously they were on the east). This resulted in December 30, 2011 being skipped on their calendars. So for residents of Samoa, December 29, 2011 was followed by December 31, 2011. The Marshall Islands made the same move in 1993.
In a range of months, a month will not be missing in the middle of it
False. The Hebrew calendar uses leap months, which occur during the middle of the year.
A year is twelve months
False. Calendars like the Hebrew and Coptic calendars deal with years that are 13 months long.
A year is 365 (or 366) days
False. The Islamic calendar is 354 (or 355) days long.
A holiday will always occur in the same part of the solar year
False. Because the Islamic calendar is only 354 days long, holidays drift by about 10 days each solar year. So after eighteen years, a holiday that used to occur during the winter will be in the summer.
Leap years occur every four years
False. The year 1900 was not a leap year.
Leap years occur every four years except when the year is evenly divisible by 100
False. The year 2000 was a leap year.
Leap years occur every four years except when the year is evenly divisible by 100, unless it’s also evenly divisible by 400
False. The Hebrew calendar, which is based almost entirely off the lunar cycle, inserts leap years 7 times in a 19 year period.
The current year only changes at “New Years”
False. The current year of the Japanese Imperial calendar is based on the reign of the current emperor. When the emperor dies (or abdicates), the next day is reset to the year 1 (of a new era).
For example, the Emperor Shōwa (Hirohito) passed away on January 7, Shōwa 64 (January 7, 1989). His son, Akihito, ascended to the throne the next day, which was the date January 8, Heisei 1.
A year only has one “New Years”
False. In addition to the Japanese calendar having (potentially) an unbounded number of “New Years” in a single year, the Hebrew calendar historically celebrated up to four different New Years in a single year.
A specific holiday on a specific calendar falls on the same date everywhere
False. The Hebrew calendar adds extra days of observance to some holidays only outside of Israel. For example, the holiday of Shavuot is observed for one day in Israel, but for two days in the Diaspora. Similarly, the holiday of Purim is observed on a different day in Jerusalem.
Nobody uses the Julian calendar anymore
False. The Julian calendar is still used by Eastern Orthodox churches and the Julian day is used in certain kinds of astronomical calculations. There is a village in Wales that still celebrates New Year according to the Julian calendar on January 13.
Timezones always are on the hour mark
False. Many places have half-hour offsets, such as French Polynesia, Newfoundland and Labrador, Iran, Afghanistan, India, Sri Lanka, Myanmar, the Cocos Islands, North Korea, and parts of Australia.
OK… Timezones are always on the half hour mark
False. There are a few places that have an offset of :15 or :45 minutes, such as Nepal, part of Western Australia, and the Chatham Islands.
Fine… Timezones are always on the quarter hour mark
Currently true, but historically false. Before the advent of global communications and standardized time keeping, the current time was pretty much up to the local administrators. When regions were brought in line with the international time keeping standards, they’d have to do some shifts to accomplish that, like Shanghai’s weird 343 second shift in the early 1900s. For more examples, Liberia was 44 minutes behind UTC up until 1972, and from 1880 to 1916, Ireland was 25 minutes and 21 seconds behind UTC.
No place is ever more than 12 hours away from UTC
False. Parts of Oceania are 12:45, 13:00, and 14:00 hours ahead of UTC.
No location will ever change what time zone it’s in
False. As mentioned above, Samoa did just that in 2011. Cancún switched timezones in 2015, as did Turks & Caicos.
We’re done adding time zones
Asia/Tomsk timezone was created in 2016 for parts of eastern Russia.
Time zones do not change their offset from UTC
False. Eight different time zones changed their UTC offset in 2016.
The UNIX epoch is January 1, 1970
False. The UNIX epoch is January 1, 1970 in UTC, but is Dec 31, 1969 in Los Angeles.
Daylight Saving Time rules do not change
False. They change all the time. In 2016, there were nine different DST changes.
Daylight Saving Time rules do not change on short notice
False. In 2016, Egypt decided to re-instate DST in June, and then reversed that decision three weeks later, three days before the shift was supposed to happen.
Days don’t last longer than 25 hours
False. Because of time zone offsets, a single calendar day typically lasts 50 hours. Or in other words, if you choose a date on the calendar, then there is a 50 hour window where at least some point on the earth thinks it is that day. The day “starts” in the UTC+14 timezone and continues for 14 hours until UTC+0 catches up to that calendar date. That date then continues for 24 hours, at which point UTC+0 transitions out of that timezone, but the other timezones behind UTC are still catching up, all the way to UTC-12.
It is normal that the Sept-, Oct-, Nov-, and Dec- months are numbered 9, 10, 11, and 12
False. This is very weird. They used to be months 7, 8, 9, and 10, but some reform to the Roman calendar back in the day resulted in the creation of January and February, which messed everything up.
Everything you know about calendars is applicable to space travel
False. There are many weird things about calendars and space travel. Days are longer, days are shorter, time flows faster, time flows slower, days are longer than years, etc etc.
“Calendrical” isn’t a real word
This is all really complicated
I never want to write code that handles all of this
True! You should always use the Date and Time Services provided by the ICU Project. If you’re an iOS/macOS developer, then you should always stick to
NSCalendar and its cohorts, which are all built on top of the ICU libraries.