Your Calendrical Fallacy Is

This is the sort of thing that enabled me to do an entire 30 minute programming conference talk on Timekeeping (both calendrical and chronological) and how it works outside computers, and what to do when your programming the computer if you want to hedge your bets and try and get it right (or as right as you need it to be)

Most people just internalise the 24hr clock mental model and then whatever version of remembering days, weeks and months works best in their part of the world.

It makes so much more sense when you understand the whole pyramid of time keeping and calendar making where they overlap and very importantly, when they don’t.

This is so much nicer than the usual "List of falsehoods programmers believe about X" for one simple reason - _examples_. Having concrete counterexamples to the assumptions being considered makes it so much easier to understand what some of the possible issues might be.

The “False” before every explanation is so incredibly off-putting. I think the site would be more effective if the explanations were just the explanation. The title has “fallacy”, no need to repeat that these assumptions are not true.