British Columbia's time zone changes expose a common weakness in software systems: assumptions about time. This article explores how PostgreSQL, application-layer time zone libraries, logging systems, financial transactions, and legacy data migrations can be affected when time zone rules change. It argues for UTC-based storage, rigorous testing, explicit conversion logic, and careful governance of time zone updates across the entire stack.