-
Senior Member
SH software did'nt just appear on the shelves by magic. That program shink-wrapped inside the box along with the manual of features that were never there and 12-paragraph disclaimer notice actually came to you by way of an elaborate path, through the most rigid quality control on the planet. Here, shared for the first time with the general public, are the inside details of the program development cycle.
1. Programmer produces code he believes is bug-free.
2. Product is tested. 20 bugs are found.
3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
4. Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
5. See 3.
6. See 4.
7. See 5.
8. See 6.
9. See 7.
10. See 8.
11. Due to marketing pressure and an extremely pre-mature product announcement based on over-optimistic programming schedule, the product is released.
12. Users find 137 new bugs.
13. Original programmer, having cashed his royalty check, is nowhere to be found.
14. Newly-assembled programming team fixes almost all of the 137 bugs, produces patches 1.2 to 1.4, but introduce 456 new ones.
15. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
16. Company is threatened by hostile action (a bunch of users who are really ticked off) but defends itself using profits from their latest release, which had 783 bugs.
17. New CEO is brought in by board of directors. He hires programmer to redo program from scratch.
18. Programmer produces code he believes is bug-free...
19. They give up in disgust and work on SH4...
20. A bunch of people no one has never heard of outside the forums and who are talented amateurs out produce and out feature the original programmers, adding the most interesting bits and pieces as add ons...for free!
Oh get a sense of humour! I thought it was funny 
But I still 
this game!
-
Senior Member
SH software did'nt just appear on the shelves by magic. That program shink-wrapped inside the box along with the manual of features that were never there and 12-paragraph disclaimer notice actually came to you by way of an elaborate path, through the most rigid quality control on the planet. Here, shared for the first time with the general public, are the inside details of the program development cycle.
1. Programmer produces code he believes is bug-free.
2. Product is tested. 20 bugs are found.
3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.
4. Testing department finds that five of the fixes didn't work and discovers 15 new bugs.
5. See 3.
6. See 4.
7. See 5.
8. See 6.
9. See 7.
10. See 8.
11. Due to marketing pressure and an extremely pre-mature product announcement based on over-optimistic programming schedule, the product is released.
12. Users find 137 new bugs.
13. Original programmer, having cashed his royalty check, is nowhere to be found.
14. Newly-assembled programming team fixes almost all of the 137 bugs, produces patches 1.2 to 1.4, but introduce 456 new ones.
15. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
16. Company is threatened by hostile action (a bunch of users who are really ticked off) but defends itself using profits from their latest release, which had 783 bugs.
17. New CEO is brought in by board of directors. He hires programmer to redo program from scratch.
18. Programmer produces code he believes is bug-free...
19. They give up in disgust and work on SH4...
20. A bunch of people no one has never heard of outside the forums and who are talented amateurs out produce and out feature the original programmers, adding the most interesting bits and pieces as add ons...for free!
Oh get a sense of humour! I thought it was funny
But I still this game!
-
Senior Member
Shhh, I think I see targ coming.
Many a true word is spoken in jest
-
Senior Member
-
Member
What stuns me is the manual. It had to be thrown together by someone who looked at some design notes and didn't really play the game.
For SH4 I hope they let some actual simmers test the game and then have them write the manual.
-
Member
True to every word... 
although we all, I'm sure, had worked this out over time. 
