Back in the mid 80's, I was doing a contract at DuPont in Delaware. The "terminal room", remember them...?, did not have a clock on the wall. So I ordered a clock, a 24 hour clock, from a vendor and installed it. Almost immediately I started receiving complaints from other "programmers" and "systems folks". It was too difficult to determine the time. A little while later, someone got fed up with figuring out how to tell the time so they ordered a 12 hour clock.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, January 09, 2008 9:28 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: OT: Computer Science Education: Where Are the Software Engineers of Tomor... I know the feeling. At my first job, I put the computer's time on UTC and printed it in 24 hour clock time. When people learned that they had to (1) first subtract 6 hours to find the local time, then (2) perhaps subtract 12 to convert to a.m. or p.m., they threatened me with bodily harm. In my emails, I still use a 24 hour clock, but use local time. Luckily the rest of the people in my group understand 24 hour clock (like if the number is > 12, then subtract 12 and say p.m. - how hard is that?) -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology <http://e-mail-servers.com/ef0869bfeaf6c579fc8a966d14f599e3worker.jpg> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
