25 more reasons you're ignoring the Year 2000 Date Problem:

 

 

------------------------------------------------------------------------

26. You can't afford the cost of maintenance (but can afford the cost of going out of business.)

 

27. You're waiting for someone to convince you the problem is real.

 

28. It's not your job to worry about this.

 

29. You believe a comet is due to hit Earth in 2000. So why bother?

 

30. Your management has not asked you to work on it yet.

 

31. You've outsourced your IS function, they're taking of this ... you hope.

 

32. You're sure your vendor has taken care of this.

 

33. Bill Gates will solve it.

 

34. You have no programmers (you downsized last year).

 

35. You have no programmers (you outsourced last year).

 

36. You have no Cobol programmers (they all moved to Client Server last year).

 

37. It's too complex.

 

38. You've got a headache.

 

39. You don't like large maintenance projects.

 

40. What date problem?

 

41. Nostradamus never mentioned this problem.

 

42. You don't want to.

 

43. You're a disgruntled employee.

 

44. Computers have no impact on your life.

 

45. You like the excitement of system crashes.

 

46. Your multi-million dollar company, doesn't really depend on computers.

 

47. We can hire enough people to replace computers as they fail and even save money too.

 

49. You believe in the sanctity of all life... even computer bugs.

 

50. You want to surprise your stockholders.

 

51. (a bonus) It's Politically Incorrect to tell management they have a problem... (especially one they didn't budget for!)

 

Copyright 1995 by Peter de Jager. Reprint permission is usually granted but must be requested first by contacting Peter de Jager at Pdejager@year2000.com or (905) 792-8706.