What's your Strategy?
https://forums.matrixgames.com:443/
I'm only allowing myself to use one of them though. The other two are playing golf and chasing nurses.ORIGINAL: Mike Solli
Well that sucks for your opponent.[X(]
ORIGINAL: Platoonist
I'll buy all the cans of ver 1.8 until they're out of stock. [&o][&o][&o]
ORIGINAL: Don Bowen
Laws of system development
1. No project has ever been brought in under budget, before scheduled completion, and free of bugs. Yours will not be the first.
2. All software has bugs - they just may not have been found yet.
3. Fixing one bug creates two more, one of which will be found and corrected immediately, which causes two more…
4. A discovered but unfixed bug, left long enough, becomes a feature.
5. Major bugs are always discovered during holidays or when the primary support programmer is on vacation.
6. Managers who set delivery dates to be end-of-year always get their Christmas vacations, no matter what.
7. New programmers assigned to maintain an old application will not make the same old mistakes - they will make interesting new ones.
8. An application reaches perfection when exactly half the users hate a new enhancement and the other half love it.
9. Attempting to put in an option to control #8 always irrevocably breaks something.
10. There is an inexhaustible supply of critical bugs. Once the one bug that "ruins the application" is fixed, the stack will pop a new one within a few days.
11. A new user will always like the application, except for all the features - which must be changed immediately.
12. A successful application will draw a larger and larger user base, who will eventually discover that the application is not good enough, after all.
ORIGINAL: Don Bowen
Laws of system development
1. No project has ever been brought in under budget, before scheduled completion, and free of bugs. Yours will not be the first.
2. All software has bugs - they just may not have been found yet.
3. Fixing one bug creates two more, one of which will be found and corrected immediately, which causes two more…
4. A discovered but unfixed bug, left long enough, becomes a feature.
5. Major bugs are always discovered during holidays or when the primary support programmer is on vacation.
6. Managers who set delivery dates to be end-of-year always get their Christmas vacations, no matter what.
7. New programmers assigned to maintain an old application will not make the same old mistakes - they will make interesting new ones.
8. An application reaches perfection when exactly half the users hate a new enhancement and the other half love it.
9. Attempting to put in an option to control #8 always irrevocably breaks something.
10. There is an inexhaustible supply of critical bugs. Once the one bug that "ruins the application" is fixed, the stack will pop a new one within a few days.
11. A new user will always like the application, except for all the features - which must be changed immediately.
12. A successful application will draw a larger and larger user base, who will eventually discover that the application is not good enough, after all.
ORIGINAL: Don Bowen
Laws of system development
1. No project has ever been brought in under budget, before scheduled completion, and free of bugs. Yours will not be the first.
2. All software has bugs - they just may not have been found yet.
3. Fixing one bug creates two more, one of which will be found and corrected immediately, which causes two more…
4. A discovered but unfixed bug, left long enough, becomes a feature.
5. Major bugs are always discovered during holidays or when the primary support programmer is on vacation.
6. Managers who set delivery dates to be end-of-year always get their Christmas vacations, no matter what.
7. New programmers assigned to maintain an old application will not make the same old mistakes - they will make interesting new ones.
8. An application reaches perfection when exactly half the users hate a new enhancement and the other half love it.
9. Attempting to put in an option to control #8 always irrevocably breaks something.
10. There is an inexhaustible supply of critical bugs. Once the one bug that "ruins the application" is fixed, the stack will pop a new one within a few days.
11. A new user will always like the application, except for all the features - which must be changed immediately.
12. A successful application will draw a larger and larger user base, who will eventually discover that the application is not good enough, after all.
ORIGINAL: Platoonist
Great lists. [:D] I'll keep the fingers crossed.
ORIGINAL: niceguy2005
I'm only allowing myself to use one of them though. The other two are playing golf and chasing nurses.ORIGINAL: Mike Solli
Well that sucks for your opponent.[X(]
ORIGINAL: niceguy2005
I do have 3 M. Michners (spelling) in my 1.8 game though. Apparently the allies perfected cloning before I upgraded to version 1.8, cuz I think its a legacy problem from 1.602.
