Menu
What's new
By:
Filters

The Software Development Cycle (Humor) (Think Windows)

Cyberman

Cyberman

Moderator
Moderator
The software 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. Repeat steps 3 and 4 three times.
  6. Due to marketing pressure and an extremely premature product
    announcement based on overly-optimistic programming schedule, the
    product is released.
  7. Users find 137 new bugs.
  8. Original programmer, having cashed his royalty check, is nowhere
    to be found.
  9. Newly-assembled programming team fixes almost all of the 137 bugs,
    but introduce 456 new ones.
  10. Original programmer sends underpaid testing department a postcard
    from Fiji. Entire testing department quits.
  11. Company is bought in a hostile takeover by competitor using
    profits from their latest release, which had 783 bugs.
  12. New CEO is brought in by board of directors. He hires a
    programmer to redo program from scratch.
  13. Programmer produces code he believes is bug-free.
This is the way to Redmond I think .. right? :)

Cyb
 
Toasty

Toasty

Sony battery
Haha. :happy: There's something to be said for a small, dedicated programming team. Definitely sounds like the "progression" from DOS to Windows ME.

Code: 
b = Number of bugs
c = Lines of code
p = Number of programmers

b = (c/50)^p
 
OP
Cyberman

Cyberman

Moderator
Moderator
I thought Windows Vista was coded using managed code and c# myself ;)
(note sarcastic tone) This should prevent any bugs!

Cyb
 
Toasty

Toasty

Sony battery
Yes, with the advent of .NET, Microsoft can now hire programmers that don't even know how to manage memory properly. This will lead to some revolutionary improvements! :p
 
OP
Cyberman

Cyberman

Moderator
Moderator
The programers at Microsofts biggest complaint about using .NET for the OS Core coding (64 bit that is), has been that DirectX 10 is slower than watching marshmellows melt in winter, using the managed code. They believe this is a problem with there virtual IO system and dynamic recomplainer (err compilor) for the DirectX sequences, and have decided that it needs to use Virtual Speed instead of Real Speed. This will give there numbers a large boost and it should virtually eliminate the problem with speed. All new games should run full Virtual Speed under the new changes.

I'm sure that this is a great thing for gamers as it means instead of having 6 fps it will be actually 60fps ... Virtually speaking of course.

:D

Cyb
 
You must log in or register to reply here.

Top