You're Not Working on the Year 2000 Date Problem Because

	Sign In Sign-Up

You're Not Working on the Year 2000 Date Problem Because...

1. You're already in Chapter 11.

2. You're 95, on life support and haven't paid your electric bill for the last 3 months.

3. You're planning to retire next year.

4. You're not using computers yet, you're waiting for the prices to come down.

5. It's someone else's problem.

6. Someone smarter than you will come up with an automated solution.

7. You believe in the Tooth Fairy.

8. Your standards (found in a large red binder in the IS library) outlined how dates should be used in all applications.

9. You only use vendor software.

10. You lost the source code of your applications 3 years ago.

11. You just don't have the time right now. Ask me again next year when things slow down.

12. You don't believe in computers.

13. Government will pass legislation to roll back the clock to 1900.

14. You're moving your mission critical systems to client servers.

15. You'll have replaced your applications by then.

16. You don't have the budget.

17. You're too busy writing new applications (which can't handle the year 2000 either.)

18. You're planning to sell your company next year.

19. January 1st 2000 falls on a Saturday and Monday's a holiday... you'll have lots of time over the weekend.

20. You were planning to phase out computers anyway.

21. You can't believe 2 missing digits can cause that much trouble.

22. You don't thinks it's such a big deal... but you'll have a programmer wear a beeper just in case anything goes wrong.

23. You're planning a vacation that week.

24. There are no date problems in your code (you have faith in your programmers).

25. You have no programmers (your competition hired them away from you last week.)