What Peter said
and;
Hitting a button (two simultaneously in this case) to obtain the correct
UTC conversion is both faster and more accurate for this pilot
My synapses just aren't that good at taking local time, which I would
perceive to be say, 8:15pm EST, and convert it to UTC military time
which (I hope) would be 0115 UTC. What's simple, swift or straight
forward about that conversion unless you do it 10 times a day or
otherwise walkaround spouting the time in military format?
So for this casual pilot, I've come to rely on the simple shorthand we
all use at some time or another "...at 15 after the hour".
For reference, the way my brain works, the conversion from 8:15 EST to
UTC goes like this in my head - "8:15pm = 20:00, 20 + 5 = 25, no, =24+1
or 1, 0100+15=0115UTC, was that EST or EDT?" A button is faster and
more consistently accurate.
Did I do the math right?
Peter Duniho wrote:
"John Gaquin" wrote in message
...
I guess my synapses aren't firing too swiftly today. Would you explain
how the procedure above is easier or more convenient than simply adding 7?
I haven't found converting from local to UTC difficult. However, it's
certainly more complicated than adding an integer to the hours.
|