Time isn’t Simple: Design Around Clock Skew and Shifts
Most code treats the current time as a trivial value, yet production environments face clock drift, backward jumps, and ambiguous timestamps. The blog shows how distinguishing elapsed duration, stable instants, transaction ordering, and business‑logic calendars lets you make time an explicit design boundary rather than a hidden assumption, preventing subtle failures in reservations, retries, and billing.