Programming

17313 readers

90 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

122

I Don't Trust My Own Code (lackofimagination.org)

submitted 5 months ago by Aijan to c/programming

37 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 12 points 5 months ago (2 children)

Falsehoods About Time

Having a background in astronomy, I knew going into programming that time would be an absolute bitch.

Most recently, I thought I could code a script that could project when Easter would land every year to mark it on office timesheets. After spending an embarrassing amount of…er…time on it, I gave up and downloaded a table of pre-calculated dates. I suppose at some point, assuming the code survives that long, it will have a Y2K-style moment, but I didn't trust my own algorithm over the table. I do think it is healthy, if not essential, to not trust your own code.

Falsehoods About Text

I'd like to add "Splitting at code-point boundary is safe" to your list. Man, was I ever naive!

[–] [email protected] 5 points 5 months ago

Rocket programmer (and engineer) here. Can confirm that time programming is hell. Don't even start on DST.

[–] [email protected] 2 points 5 months ago* (last edited 5 months ago) (1 children)

I'm sure many smaller companies had their own internal Y2K moment as they scaled and became a big hit, and realized they used a wrong datatype like int instead of long or something and shit was gonna break by XYZ date if they did nothing heh.

[–] [email protected] 2 points 5 months ago (1 children)

Imagine if you were the guy who made the call on IPv4 addresses…

[–] [email protected] 2 points 5 months ago (1 children)

Give it long enough and somehow the person who decided on IPv6 will feel the same as every piece of matter we want to interact with can be networked.

[–] [email protected] 2 points 5 months ago (1 children)

I guess the MAC address guy is up next. 48 bits may not go so far if every light bulb is going to want its own.

[–] [email protected] 2 points 5 months ago

Apple won't like that doomsday event lol