Representing Time and Date

This is interesting to me, notations and ways to represent date and time

There’s something called metric time

Resources

data : Doesn’t have a time component but what actual point-in-time it is really is determined by the reader of the data(where they live)
date/time : Same as date. The correct time is determined by what timezone your location is assigned to.
- date/time by itself doesn’t seem

	point-in-time data	interop btwn systems	different systems ops	sortable
unix timestamp	YES	YES	YES	YES
date time w tz	YES + tz origin data	No, needs logic	YES	YES
date time w/o tz	No, represent social time

If you just want date and don’t want time component, UTC+000 seems like a way to go.
If you need to know the original timezone of the event, then store it with the original timezone.
Unless you have a reason to store something in a local timezone, UTC is the right choice, but no choice is perfect.
If using pg, use:
- date
- time
- timestamp {without|with} time zone
  - timestamp without time zone essentially falls into UTC
- AVOID time with timezone
  - See https://gist.github.com/henryivesjones/ebd653acbf61cb408380a49659e2be97

Common misconception is that Unix time can’t be used to represent dates before January 1st, 1970.
- It is timezone agnostoc works across timezones
Unlike Unix timestamp, there is no such thing as a universal DateTime format. Each programming language or tool relies on its own internal logic and implementation details for this data type. For the purpose of this article, we’ll categorize DateTime as an embedded calendar-aware and timezone-aware module, capable of handling the complexity of modern time-keeping systems.