Jump to content

How a program is made.


Recommended Posts

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 overly-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, but introduce 456 new ones.

15. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.

16. Company is bought in a hostile takeover by competitor 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....

Link to comment
Share on other sites

... and then see 2. :biggrin:

 

Nice one!

[sIGPIC][/sIGPIC]

 

К чему стадам дары свободы?

Их должно резать или стричь.

Наследство их из рода в роды

Ярмо с гремушками да бич.

Link to comment
Share on other sites

11. Due to marketing pressure and an extremely pre-mature product announcement based on overly-optimistic programming schedule, the product is released.

 

 

Number 11 is the biggest Problem in PC Gaming Industry

 

Today its normal to release buggy software. Sometime im asking how a publisher would react if he would visit a dentist for example and then while he is drilling the teeth of a CEO the driller would brake in two parts. Then the dentist should say: "Sorry its brand new, but it has some errors and they will be repaired in the next months"

Link to comment
Share on other sites

0.1 - general feature requirements are compiled

0.2 - each requirement is analyzed and relationships between requirements are established

0.3 - data necessary for each feature are established

0.4 - data structure is rationalized

0.5 - features are designed

0.6 - features are tested at design stage

0.7 - revision of design is performed based upon results of tests

0.8 - repeat 0.6 and 0.7 until design passes test

0.9 - touch the keyboard.

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...