Duh-2000:
The past nominees... The monthly contest for the stupidest thing said about the Year 2000 problem |
From Contest #10 This Contest's Candidates (the official list, in no particular order): Speaking of millennium babies... Hugh Downs, co-anchor
ABCNEWS 20/20 and one of the most familiar figures in the history of broadcasting:
"Some calendars and computers have a leap day built in, some do not. The confusion
comes from a difference of opinion as to whether the 400-year cycle extends from 1000 or
from 2000 AD. If the latter, then a 29-day February is appropriate for the coming
millennial year. If not, we may have a problem. Because our computers and calendars are
not all the same on this and because nobody, it seems, is doing anything about the
anomaly were headed for a mess. The best thinking, Im told,
astronomically, is that the year 2000 should not have a leap day." Neither rain, nor snow, nor darkness... Who's on first, the Y2k edition
Obviously Larry and Art were demonstrating "channelling" with the spirits of Bud Abbott and Lou Costello. Quoted on CNN's Larry King Live Art Bell Discusses the Unexplained March 5, 1999. Submitted by Merle Bengston. Joe Riley, president of the
Technological Information Consultants of Australia: "One likely thing that may happen
is something like an insurance company will not insure or underwrite planes that go to
(non-compliant) countries. ... Nobody's alarming people or doing alarmist things. It's a
reality.'' Jack L. Brock, director of
governmentwide and defense information systems at GAO, said DoD needs to take extra
precautions to make sure its critical systems will work. "It's like going to a party,
and you risk your pants falling down," he said. "You not only want to wear a
belt, but suspenders as well." This is like shooting Russian fish in a barrel... Not to be outdone by the Russians and the Italians,
Spain checks in... Vice President Al "Mr.
Information Superhighway" Gore weighs in on Y2k: "We feel, and the
Defense Department feels, that problem is not going to be a problem. Of course, it can't
be a problem. We won't allow it to be a problem. ... We're confident that it is going to
be solved, but we're going to be doubly, triply and quadrupally confident that it's going
to be solved before September of this year." Sen. Richard Lugar, telling
Indiana state legislators that government agencies and private companies should tell the
truth about possible problems looming from the Y2K computer bug to prevent possible panic:
"And even after all of our reassurances, some people are skeptical of the
government." Graeme Inchley, CEO of the Australian government-sponsored
Y2K industry program. "We're at the point where the majority of businesses that are
doing nothing have actually made a conscious decision to do nothing. They figure they'll
fix it if something goes wrong. I can sympathise with that position, but it's awfully
risky." Zimbabwe's Minister of Information Chen
Chimutengwende, whose responsibilities include information technology: "What
is this Year 2000 problem?" No wonder the Russians are in trouble: "...[L]ocal bankers who have worked on the problem
extensively are rendered nearly speechless when asked what they would do if their ATM
systems went down for an entire week. Their systems have been tested so thoroughly that
they can't imagine it happening, they say. "That would mean something very critical
has gone wrong," said a spokesman for LaSalle National Bank in Chicago." Paul Takemoto spokesman for the
FAA: "We are absolutely confident we will have everything ready. ... And that's not
just false boasting." Stupid Journalism Chicago Tribune staff writer James
Coates: "As just about anybody who ever tried to level a crooked 3-legged
stool using a handsaw can tell the world, sometimes trying to fix a problem just makes it
worse. You saw off the leg you think is too long and then it's too short. So you trim down
the other two legs to match the first boo boo. Now you've got a stool that still wobbles
but now it's too short as well as unstable. The parable of the milking stool and the
handsaw gets cited frequently to describe the situation as computer experts realize that
the very weapons they use to fight the Millennium Bug are, themselves, buggy." And now the the unofficial list: I recently overheard this from a couple of 16 year olds:
"Y2K?.... Isn't that the thing on my zipper?" (and lo and behold there is a Y
and 2 K's on that zipper!!!) At a recent gathering where people heard I was in charge of
a Year 2000 Program - someone said "Yeah, I heard the guy who invented the term Y2K
is making millions off the royalties!" I have to make this anonymous because these quotes come from
our client's legal eagles, and you can't offend a client. I've run into this legal
language several times, and I find it hilarious. It comes in contract addendum's and
warranty requests from our clients, and it usually goes something like this... "In
order for the software to be Year 2000 Compliant it must (i) accurately process date/time
data (including, but not limited to, calculating, comparing, sorting, sequencing and
calendar generation), including single century formulas and multi-century formulas, from,
into within and between the twentieth and twenty-first centuries..." etc. I
wondered how something could go on "between" centuries, so I asked the client's
lawyer. I actually had a lawyer try to convince me there was a little tiny chunk of time
that sits in between one year and the next. She couldn't tell me exactly how long that
time was, but she was sure it was there. The other thing I find amusing is the reference
to everything running properly, "...between the twentieth and twenty-first
centuries..." Since the calendar actually started with year 1 and not year 0, the
transition from the 20th to the 21st century will occur with the transition from December
31st, 2000 to January 1st, 2001. So the way the contract is worded, they don't have any
assurances that things will work from 1999 to 2000. Duh. I have an uncle who is an ex-military type from India and
now lives in the US. He suggested to his Nephew (from the other side of the family) back
in India who just finished high school this year (1999) that he should go to college and
then come to the USA to work on the Y2K problem! Must be one smart kid if he can finish
college in less than 9 months!!! Speaking of careers... I was in a meeting where we were discussing the upgrade of
our store time and attendance clocks and software to make the system Y2k compliant. The
manager in charge of the store IS area, upon hearing that his group would have to be
involved in the testing of the new clocks and software, became extremely irritated and
said, "We just put together our budget for 1999, and this wasn't included! We'll have
to go back, start over, and work it into our budget!" My wife works for a facilities maintenance mail-order supply
house, and talked with the supply manager of a major hotel chain who wanted to know if the
faucets he was ordering were Y2K compliant. My wife had to hit the mute button on her
phone headset, because she could not stifle her laughter. Recently overheard: "Y2K? It could be worse: we could
be trying to fix it without computers." |
This web site and all material contained herein is Copyright ©1998, 1999 The Ken Orr Institute. All Rights Reserved. The opinions expressed here are necessarily the opinions of the staff and management of The Ken Orr Institute. Any resemblance to any actual persons living or dead is purely intentional. No animals were harmed in the creation of this website, except for a small and reasonably insignificant squirrel that annoyed us at just the wrong instant. Elvis has left the building. Keep in mind that links to current news items change at the drop of a hat, so don't be surprised if the quote turns up 404 (internet-speak for "we're sorry, but that number has been disconnected or is no longer in service"). |