-=> Jas Hud wrote to Kurt Weiske <=-

 JH> i heard talk of y2k cobol armageddon but then i was unsure if that ever
 JH> came into fruition.  my friends in IT never brought it up.  i know on
 JH> the news they mentioned hiring cobol programmers for short contracts. i
 JH> am not sure how that panned out.

 It didn't, because IT departments spent billions updating code, in
 many cases bringing people out of retirement for a nice consulting
 fee.

 I was lucky; I worked in telecom, and most telecom hardware had been
 updated when they updated to the North American Numbering Plan.

 When area codes were first implemented, they had a 0 or a 1 as the
 middle digit as part of the logic for the phone company's systems to
 determine if a call was local or long distance. As telephone usage
 grew, they began to run out of usable area codes when trying to
 overlay a code over a busy area, and had to change all sorts of code
 to support this in the early 1990s.

 By the time Y2K cam around, we were all set.

 More phone trivia, area codes were designed so that the most populous
 areas had the lowest numbers, because they were dialed on a rotary
 phone and would be dialed more often. Compare New York (212), Los
 Angeles (213), Hawaii (808) and Alaska (907).





 KW>  Some people don't change. I've seen people that worked swing shifts
 KW>  swapping tapes, printing out reports and running through maintenance
 KW>  checklists, right up until they unplugged the last AS/400 and laid
 KW>  them off. Didn't know what hit them.
 KW>


 JH> man i miss as400. i could do so much with it. we switched to jdedwards
 JH> at my job and had a rough time in transition.

 JH> Companies just have stupid people that dont take accountability. they
 JH> let things fall apart.  some people wouldn't even  pull the fire alarm
 JH> if the place was on fire.

 JH> ... Carefull, we might be landing on your street

 JH> --- Renegade v1.30/DOS

... Is it finished?
--- MultiMail/DOS v0.52