The basic unit of time is the second. For smaller amounts of time they
use metric prefixes.
I sometimes think of what it would like to use metric prefixes for
larger units, like kiloseconds.
After 86.4 kiloseconds you run into the day, a natural period of time
that doesn't fit into this metric stuff. Reality gets in the way.
How about forgetting about seconds, and use days. Then you have the
milliday, (which is still longer than a minute). A microday would be the
period of time we used to call 86.6ms (milliseconds).
BTW, in our system the average year is 365.2425 days long. Unexpectedly,
that IS a whole number of seconds. There are 31,556,736 seconds in the
average year. That's about 31.5 megaseconds per year.
1 gigasecond is approx. 31.69 years.
1 terasecond is approx. 31.69 millennia.
On Sunday, March 13, 2016 at 11:08:56 PM UTC-4, Mark Lloyd wrote:
Here's an interesting article on how Excel stores dates and times. If anyone ever asks why
Excel includes Feb 29, 1900 even though 1900 was not a leap year, you'll be able to tell them
that it is not a bug. It is by design.
I did some patching in the months leading up to Y2K but there really
wasn't that much. I was on call New Year's Eve but it passed
uneventfully. Luckily someone other than myself will have to worry about
I saw "19A0" in one case. Caught me completely off guard
("Where the hell did that 'A' come from??"). But, thinking
about it for a few microseconds and it was obvious...
I now keep dates as ascii strings. It's not that much more work.
The tougher problem (and it will NOT be solved, here! :> )
is thinking about temporal "REFERENCES"!
E.g., if I have an appointment "in 35 minutes" and I *bind* that
to the current time (it is roughly 8:40P here), then that would
suggest the appointment is at 9:15P. Assume I also have something
scheduled for 10:00P.
Now, if I adjust my local clock to make "now" be 8:45P, how
does that affect these two events? Is my appointment still
35 minutes in the future? And, the 10:00 event 5 minutes sooner
than it would have been had I not updated my clock?
What if I then set my clock *back* 5 minutes? Has anything changed??
Silly example. But, think about things that are days or weeks
hence. How do you "store" those times? And, how does your choice
of storage technique (e.g., early or late binding) affect when
they ACTUALLY occur?
Do you store "relative times" using a relative notation? And,
store the reference from which they were originally specified?
Or, convert everything to absolute times?
Do you convert absolute times to relative times and store the
I.e., when a person says "I have an appointment in 35 minutes",
does that really mean they will wait for the minute hand to make
35 complete revolutions before the appointment begins? Or,
have they done some mental arithmetic and decided to express
the ABSOLUTE time of the appointment in relative terms (for
the benefit of whomever they are conversing with)?
That stuff reminded my of my grandmother cooking biscuits. She wanted to
leave them in the oven for 10 minutes, and seemed to have a problem with
keeping track of that. Keep looking at the clock ans saying "how long
has it been...".
I suggested that (when putting the biscuits in) look at the clock NOW
and figure out what time it will be 10 minutes from now. Then it's easy
to check for that.
Some people will not allow things to be easy.
Growing up, we had pasta at least once a week. (short) mother kept
it on the top shelf -- and always had to ask me to get it down for her.
"Sheesh! Why don't you just LEAVE IT ON THE COUNTER, we eat it often
PNEUMONOULTRAMICROSCOPICSILICOVOLCANOCONIOSIS (45 letters, a lung disease caused by breathing in particles of siliceous volcanic dust) is the longest word in the English language, beating TETRAMETHYLDIAMINOBENZHYDRYLPHOSPHINOUS ACID, HEPATICOCHOLANGIOCHOLECYSTENTEROSTOMIES, FORMALDEHYDETETRAMETHYLAMIDOFLUORIMUM, and DIMETHYLAMIDOPHENYLDIMETHYLPYRAZOLONE.
I always preferred $23 (On the Commodore-64 hex was indicated by a
As to language, I was once looking at the source code for a program. One
of the error messages was "not enough memory to execute child". It made
perfect sense to me, just not anything like what it would mean to a
HomeOwnersHub.com is a website for homeowners and building and maintenance pros. It is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.