How to Think About Time in Programming

10 months ago

Time handling in programming is complex, involving concepts like absolute time (instants and durations) and civil time (human-readable labels).
Absolute time is measured in seconds from an epoch (e.g., Unix epoch: Jan 1, 1970, 00:00:00 UTC).
Civil time uses systems like the Gregorian calendar, which includes periods (e.g., months, days) that are ambiguous in duration.
UTC (Universal Time Coordinated) synchronizes global clocks using atomic timekeeping and occasionally adjusts with leap seconds.
Timezones allow local expressions of UTC, but their rules can change unpredictably (e.g., daylight savings transitions).
The IANA Timezone Database tracks historical and current timezone rules globally, essential for accurate time conversions.
Common pitfalls include assuming UTC solves all time issues and not accounting for leap seconds or timezone rule changes.
Practical examples include chat forums (ordering messages by UTC) and event planning (handling timezone changes).
Best practices involve using libraries that leverage the IANA database and clearly defining user intentions for time handling.

Hasty Briefsbeta