@GergelyOrosz: Actually - no. This is why every and any sane software engineer uses 1) Utc timestamps (no daylight savings) or Epoch t…
Summary
Gergely Orosz emphasizes the importance of using UTC timestamps or epoch time along with proper date libraries to handle time zones and daylight saving time correctly.
View Cached Full Text
Cached at: 07/15/26, 11:52 AM
Actually - no. This is why every and any sane software engineer uses
-
Utc timestamps (no daylight savings) or Epoch time (timezone independent)
-
Date libraries to render dates that take care of local conversion and pesky things like daylight savings
Rhys (@RhysSullivan): a million software engineers just felt a disturbance in the force
Similar Articles
@GergelyOrosz: I'm using Antithesis (@AntithesisHQ - the presenting sponsor of the podcast) more to better understand how they test de…
Gergely Orosz shares his experience using Antithesis, a deterministic testing infrastructure that can run hours of testing in minutes.
@GergelyOrosz: This is exactly why experienced software engineers are valuable and will be valuable. If you don’t know what good code …
Gergely Orosz argues that experienced software engineers remain valuable because they can discern good code from bad, something AI code generators still cannot reliably do.
@GergelyOrosz: How have the fundamentals of building large, distributed software systems changed the last decade? A conversation with …
Martin Kleppmann discusses how the fundamentals of building large, distributed systems have evolved over the past decade in light of the updated second edition of his book "Designing Data-Intensive Applications."
British Columbia, Time Zones, and Postgres
Discusses how British Columbia's permanent switch to Pacific Daylight Time in 2026 affects PostgreSQL timestamp storage, and provides best practices to avoid time zone shift errors using a dual-column pattern.
@GergelyOrosz: The way I look at it: 1. The husband had urgent demands at work 2. Communicated with his partner and decided to priorit…
Gergely Orosz shares his perspective on prioritizing work under urgent demands, citing an interview with a top developer who did the same.