this post was submitted on 26 Jan 2025
609 points (96.1% liked)

196

16826 readers
1330 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 2 years ago
MODERATORS
609
ISO 8601 ftw rule (gregtech.eu)
submitted 5 days ago* (last edited 5 days ago) by lena@gregtech.eu to c/196@lemmy.blahaj.zone
 

!iso8601@lemmy.sdf.org gang, rise up

you are viewing a single comment's thread
view the rest of the comments
[–] nesc@lemmy.cafe 55 points 5 days ago (14 children)

This pyramid visualisation doesn't work for me, unless you read time starting with seconds.

[–] lena@gregtech.eu 13 points 5 days ago* (last edited 5 days ago) (2 children)
[–] nesc@lemmy.cafe 29 points 5 days ago (2 children)

I get it, just pyramids are misleading, also year-month-day is better because resulting number always grows. 😺

[–] lena@gregtech.eu 6 points 5 days ago (1 children)

A bit out of context, but is your username and instance a reference to nescafe?

[–] nesc@lemmy.cafe 11 points 5 days ago (1 children)

Not really but now that you mentioned it, it will! 😄

[–] lena@gregtech.eu 4 points 5 days ago

That's an interesting coincidence

[–] Zagorath@aussie.zone 16 points 5 days ago (2 children)

2025-01-26T11:40:20, you mean?

[–] olympicyes@lemmy.world 5 points 5 days ago (1 children)

Hold on there pal that time zone is ambiguous. Did you mean 11:40:20 UTC? If so, don’t forget your Z!

[–] Zagorath@aussie.zone 1 points 4 days ago

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.)

load more comments (11 replies)