this post was submitted on 18 Dec 2024
1100 points (98.2% liked)

memes

10671 readers
1929 users here now

Community rules

1. Be civilNo trolling, bigotry or other insulting / annoying behaviour

2. No politicsThis is non-politics community. For political memes please go to !politicalmemes@lemmy.world

3. No recent repostsCheck for reposts when posting a meme, you can only repost after 1 month

4. No botsNo bots without the express approval of the mods or the admins

5. No Spam/AdsNo advertisements or spam. This is an instance rule and the only way to live.

Sister communities

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] whotookkarl@lemmy.world 18 points 3 days ago (9 children)

The two most difficult things in programming; dealing with time, naming things, and boundary conditions.

[–] grandkaiser@lemmy.today 12 points 3 days ago* (last edited 3 days ago) (1 children)

dealing with time

Network engineer here, it's just as bad here. Currently trying to figure out what to do with 'gaining' a negative leap second. In 2025, we may lose one for the first time in digital history.

[–] possiblylinux127@lemmy.zip 2 points 3 days ago (2 children)
[–] kungen@feddit.nu 5 points 2 days ago (1 children)

I forgot what the N stands for in NTP, but the network engineer might know.

[–] Hupf@feddit.org 1 points 2 days ago
[–] grandkaiser@lemmy.today 3 points 2 days ago* (last edited 2 days ago) (2 children)

Absolutely. I'm a ddi engineer. NTP plays a huge part in my work. Systems, including ntp, are designed to handle leap seconds. Negative leap seconds are uncharted territory. I could go off on a long rant about it, but I doubt people care that much. It's really dry stuff.

[–] BeardedGingerWonder@feddit.uk 3 points 2 days ago

I'll listen, then I can seem knowledgeable af when it gets mentioned on a call 3 days before it happens and everyone else is freaking out.

[–] jol@discuss.tchncs.de 2 points 2 days ago

We love long dry niche rants though.

load more comments (7 replies)