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?
Falsehoods programmers believe about time
71–80 of 212 posts
Re: Falsehoods programmers believe about time
#72Is 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…
Don't make assumptions. You aren't smart. Keep it simple and don't get clever.
Re: Falsehoods programmers believe about time
#73Earlier 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?
Re: Falsehoods programmers believe about time
#74"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...
Re: Falsehoods programmers believe about time
#75We 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…
Re: Falsehoods programmers believe about time
#76Unimportant 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.
Re: Falsehoods programmers believe about time
#77We 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…
Kodak used to run on this calendar.
Re: Falsehoods programmers believe about time
#78Is 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…
Re: Falsehoods programmers believe about time
#79We 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…
Re: Falsehoods programmers believe about time
#80Earlier 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.
Wait. In fact, if you weren't born on 01-01-1970, you can't be Time Druid. Sorry.