It's about time
summary
Practical rules and gotchas for storing and testing time including concrete examples: use the Joda/Noda/Java Time model (Instant, LocalDateTime, zone-aware types) and prefer timestamp with time zone vs timestamp awareness when persisting, because OS timezone changes can flip instants; prefer start + duration, not start/end for scheduled events to survive DST gaps and overlaps; account for leap second causes 61s and JVM smearing or OS-dependent behavior. Test against a real DB, parameterize edge instants, and persist UTC where sensible.
AI-written summary · about
chapters (6)
- 0:00Start
- 8:42Sequence number?
- 21:57Working with durations
- 30:50Persistence
- 46:23Testing
- 49:03Parameterized Tests
related talks
01h 00mDates and times aren't that hard - honestly!
01h 05mWorking with Time is Easy
48mWorking with date and time data in .NET
42mStrategies for Dealing with Date and Time in Test and Production Code
24mI have a Date
38mA Matter of Time
39mThe Pearls and Pitfalls of DateTime
42mWorking with Dates and Times (It's Possible!)