A pyramid is built bottom to top, not top to bottom. That’s also one of the strengths of the ISO format. You can add/remove layers for arbitrary granularity and still have a valid date.
Yeah, but people read top to bottom. The best way to do it would be to have upside down pyramids. With the biggest blocks at the top representing the biggest unit of time (YYYY) and the smallest blocks at the bottom representing seconds & smaller.
I mean 11:40:20 in what NodaTime would call a “LocalDateTime”. i.e., irrespective of the time zone.
(And incidentally, if you’re working in C# I strongly recommend the NodaTime library. And even if you’re not, I strongly recommend watching the lectures about dates and times by the NodaTime developer, who demonstrates a way of thinking about dates and times that is so much more thoughtful than what most standard libraries allow for without very careful attention paid by the programmer.)
This pyramid visualisation doesn’t work for me, unless you read time starting with seconds.
A pyramid is built bottom to top, not top to bottom. That’s also one of the strengths of the ISO format. You can add/remove layers for arbitrary granularity and still have a valid date.
Yeah, but people read top to bottom. The best way to do it would be to have upside down pyramids. With the biggest blocks at the top representing the biggest unit of time (YYYY) and the smallest blocks at the bottom representing seconds & smaller.
What do you think this is some sort of pyramid scheme?
Offene Feldschlacht betritt den Raum
2025-01-26-11-40-20
I get it, just pyramids are misleading, also year-month-day is better because resulting number always grows. 😺
A bit out of context, but is your username and instance a reference to nescafe?
Not really but now that you mentioned it, it will! 😄
That’s an interesting coincidence
2025-01-26T11:40:20, you mean?
Hold on there pal that time zone is ambiguous. Did you mean 11:40:20 UTC? If so, don’t forget your Z!
I mean 11:40:20 in what NodaTime would call a “LocalDateTime”. i.e., irrespective of the time zone.
(And incidentally, if you’re working in C# I strongly recommend the NodaTime library. And even if you’re not, I strongly recommend watching the lectures about dates and times by the NodaTime developer, who demonstrates a way of thinking about dates and times that is so much more thoughtful than what most standard libraries allow for without very careful attention paid by the programmer.)
Yeah