Guide to Software Revisions
 

1.0: Also known as "one point uh-oh", or "barely out of beta". We had to release because the lab guys had reached a point of exhaustion and the marketing guys were in a cold sweat of terror.

1.1: We fixed all the killer bugs ...

1.2: Uh, we introduced a few new bugs fixing the killer bugs and so we had to fix them, too.

2.0: We did the product we really wanted to do to begin with. Mind you, its really not what the customer needs yet, but were working on it.

2.1: Well, not surprisingly, we broke some things in making major changes so we had to fix them. But we did a really good job of testing this time, so we dont think we introduced any new bugs while we were fixing these bugs.

2.2: Uh, sorry, one slipped through. One lousy typo error and you wont believe how much trouble it caused!

2.3: Some jerk found a deep-seated bug thats been there since 1.0 and wouldnt stop nagging until we fixed it!!

3.0: Hey, we finally think weve got it right! Most of the customers are really happy with this.

3.1: Of course, we did break a few little things.

4.0: More features. Its doubled in size now, by the way, and its written in a different language now and you'll need a bigger server ...

:lick:

As a coder I can sign under this :p

As humorous as this is half of those steps should never happen ;)

- miSt

Funny, but also agree with Mist :)

Shouldn't, but nearly allways will. A majority of software (in particular Information Systems) allways fail. Software Engineers tend not to learn from past errors.

lol the funny thing is putting it along with vb.

Agreed.

You may be the richest person in the world.
You can hire the best coders money can buy.
You can have hundreds of people working on your code.
You can have a software which used by the entire world.
You can have a years of experience in this software.
But your miracle software does still fails even in your introduction to press conference. You will get that dreaded BLUE screen while your OS is booted and it is in live TV all around the would. :lick:

Sophisticed software had bugs, do have bugs and will have bugs, no matter what you do as there is no such thing as "PERFECT software".

A decent coder is the one who manages to avoid important, security related, major bugs and works hard to fix the rest.