Live data from Hacker News

Falsehoods programmers believe about time

infiniteundo.com

71–80 of 212 posts

Re: Falsehoods programmers believe about time

#71
post #50

Earlier quoted context omitted.

So "most" programs can ignore birth dates of people older than 52? I don't think so.

Do most programs need to know the birth date of the user?

Most of the programs I write do. Well, of people, but not typically the user.

Re: Falsehoods programmers believe about time

#72

Is it just me, or does anybody else hate these "Falsehoods programmers believe about..." lists. Every abstraction at some level is leaky. Even the atom is a leaky abstraction, and maybe even matter itself is a leaky abstraction at some level. What matters is how well the abstraction matches your use case, and where the leaks are. Just having a list of how a particular abstraction leaks without any context is not supe…

Here's my tl;dr for "falsehoods programmers believe about [x]" so you never have to read another:

Don't make assumptions. You aren't smart. Keep it simple and don't get clever.

Re: Falsehoods programmers believe about time

#73
post #69

Earlier quoted context omitted.

Should we also turn off computers in hospitals and in other important facilities? And then how can we qualify what's important? Maybe you and I have the privilege to turn off computers for almost a week without a negative effect, but not the majority of the world, everything uses a computer to operate and coordinate. Think about food production, aviation, shipping, sailing... And much more at both small and big scale…

You're going to take issue with that instead of Druid part?

I hereby announce my campaign for the role of Time Druid.

Re: Falsehoods programmers believe about time

#74
post #28

"Months have either 28, 29, 30, or 31 days." Ok, Im intrigued, are there months that don't? I assume it must be a country specific thing?

Clicking through the links, this post appears to be the source: https://news.ycombinator.com/item?id=4128470 As another commenter noted, the exception appears to be September 1752. That's a fun example but whether it's worth worrying about is another question...

As the comments to that comment points out, 1752 is only for one specific country. All countries switched at different times (and a few even switched back and forth a few times). Greece, in particular, seems to have switched as late as 1923.

Re: Falsehoods programmers believe about time

#75

We should just define a year to be 360 days long and made up of 12 30 day months. Then we can elect some druids or whatever to arbitrarily, at the start of each year, define which dates the seasonal borders will land on. Events which are truly dependent on weather can be defined in terms of "Days after the season starts." Or we could define a 5.5+-.5 day holiday between the beginning and end of a given year. Those da…

Should we also turn off computers in hospitals and in other important facilities? And then how can we qualify what's important? Maybe you and I have the privilege to turn off computers for almost a week without a negative effect, but not the majority of the world, everything uses a computer to operate and coordinate. Think about food production, aviation, shipping, sailing... And much more at both small and big scale…

And why do only people born within them get special hats? Maybe you and I have the privilege of going about hatless, but not the majority of the world.

Re: Falsehoods programmers believe about time

#76
post #3
post #2

Unimportant sidenote: I don't like the naming of these "falsehoods programmers believe about X" lists. Surely programmers are more likely to be conscious of these not being true than non-programmers.

I still encounter forms on the web or input fields in software that prevent me from entering truthful information or that require me to input information that doesn't exist. There are definitely still programmers out there that make assumptions that don't hold in all cases.

[deleted]

Re: Falsehoods programmers believe about time

#77

We should just define a year to be 360 days long and made up of 12 30 day months. Then we can elect some druids or whatever to arbitrarily, at the start of each year, define which dates the seasonal borders will land on. Events which are truly dependent on weather can be defined in terms of "Days after the season starts." Or we could define a 5.5+-.5 day holiday between the beginning and end of a given year. Those da…

Something very similar already exists (in theory): https://en.wikipedia.org/wiki/International_Fixed_Calendar

Kodak used to run on this calendar.

Re: Falsehoods programmers believe about time

#78

Is it just me, or does anybody else hate these "Falsehoods programmers believe about..." lists. Every abstraction at some level is leaky. Even the atom is a leaky abstraction, and maybe even matter itself is a leaky abstraction at some level. What matters is how well the abstraction matches your use case, and where the leaks are. Just having a list of how a particular abstraction leaks without any context is not supe…

I think I understand why you feel this way, but I personally find them to be a helpful format. For example, last time I had to figure out how to store addresses in a database I made a point to check out the falsehoods programmers believe about addresses document (as well as other sources).

Re: Falsehoods programmers believe about time

#79

We should just define a year to be 360 days long and made up of 12 30 day months. Then we can elect some druids or whatever to arbitrarily, at the start of each year, define which dates the seasonal borders will land on. Events which are truly dependent on weather can be defined in terms of "Days after the season starts." Or we could define a 5.5+-.5 day holiday between the beginning and end of a given year. Those da…

Should we also turn off computers in hospitals and in other important facilities? And then how can we qualify what's important? Maybe you and I have the privilege to turn off computers for almost a week without a negative effect, but not the majority of the world, everything uses a computer to operate and coordinate. Think about food production, aviation, shipping, sailing... And much more at both small and big scale…

No post body was provided.

Re: Falsehoods programmers believe about time

#80
post #73
post #69

Earlier quoted context omitted.

You're going to take issue with that instead of Druid part?

I hereby announce my campaign for the role of Time Druid.

Your symbols of office shall be a blinking 12:00 and the date 01-01-1970.

Wait. In fact, if you weren't born on 01-01-1970, you can't be Time Druid. Sorry.

Post reply on HN