Program development cycle

Boxes with software do not appear on the shelves by the wave of a magic wand. The program, the disc with which is packaged together with the vague guidance and the twelve-page disclaimer, passes the thorny path and the most stringent quality control on the planet before you get there.

1. The programmer writes, in his opinion, the perfect code.
2. The program is tested. Found 20 errors.
3. The programmer fixes 10 errors and explains to the testing department that the other 10 bugs are features.
4. The testing department finds out that 5 corrections do not work, and finds 15 more errors.
5. See 3.
6. See 4.
7. See 5.
8. See 6.
9. See 7.
10. See 8.
11. Due to the pressure from the market and the extremely premature announcement of the release of a software product based on an overly optimistic development schedule, the product is being released.
12. Users find 137 new bugs.
13. The programmer, who has already received money for the development, has disappeared and is not responding to the phone.
14. The newly created team of programmers fixes almost all 137 errors, but introduces 456 new ones.
15. The first programmer sends to the testing department, which is significantly underpaid, a postcard with Fiji. The entire testing department is fired.
16. The company is bought by former competitors for a profit from the latest release, which contains 783 bugs.
17. Board of Directors appoints new CEO. He hires a new programmer and forces him to completely rewrite the program.
18. The programmer writes, in his opinion, the ideal code ..