Sunday, April 25, 2010
Monday, October 05, 2009
Software Development Cycles
Software Development Cycles
- Programmer produces code he believes is bug-free.
- Product is tested. 20 bugs are found.
- Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.
- Testing department finds that five of the fixes didn’t work and discovers 15 new bugs.
- Repeat three times steps 3 and 4.
- Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.
- Users find 137 new bugs.
- Original programmer, having cashed his royalty check, is nowhere to be found.
- Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.
- Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.
- Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.
- New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.
- Programmer produces code he believes is bug-free…
Via: http://stackoverflow.com/
Posted by
Anurag
at
Monday, October 05, 2009
0
word of wisdom
Friday, August 14, 2009
Flying colors of India
Fully decorated Auto Rickshaw
Waiting for the passenger to board
All superstar willing to find the place
Posted by
Anurag
at
Friday, August 14, 2009
0
word of wisdom
Labels: Colors of India
Thursday, August 13, 2009
Thursday, July 09, 2009
QA Words of Wisdom
* FAME! I wanna test forever! I want to get to the bug. FAME!
* I know one thing. Indecision may or may not be my problem.
* This is not a bug. It’s a feature! (Product Manager’s Dictionary)
* Confidence is the feeling you have before you understand the situation.
* Never say “Oooops” … always say “Ahhh, interesting…”
* Inside every large problem is a small problem struggling to get out
* Weiler’s Law says that nothing is impossible for those who don’t have to do it themselves.
* Developer when code doesn’t work: ‘I thought I fixed that.’
* Developer when code doesn’t work: ‘It works, but it hasn’t been tested.’
* “Shhh!!! Be vewwy vewwy quiet! I’m hunting bugs!”
* Going to add a bug ??? remember !!! the QA team is always the last one at the door
* Ok, UNICODE is…. Wait, which Unicode are you talking about?
* Klingon software does not have bugs. It has features, and those features are too sophisticated for a Romulan pig like you to understand.
* Computers are like bikinis. They save people a lot of guesswork.
* If debugging is the process of removing bugs, then programming must be the process of putting them in.
* Testing can only prove the presence of bugs, not their absence.
* A known bug is better than an unknown feature.
* Real Programmers don’t comment their code. If it was hard to write, it should be hard to read.
* I know one thing. Indecision may or may not be my problem.
* This is not a bug. It’s a feature! (Product Manager’s Dictionary)
* Confidence is the feeling you have before you understand the situation.
* Never say “Oooops” … always say “Ahhh, interesting…”
* Inside every large problem is a small problem struggling to get out
* Weiler’s Law says that nothing is impossible for those who don’t have to do it themselves.
* Developer when code doesn’t work: ‘I thought I fixed that.’
* Developer when code doesn’t work: ‘It works, but it hasn’t been tested.’
* “Shhh!!! Be vewwy vewwy quiet! I’m hunting bugs!”
* Going to add a bug ??? remember !!! the QA team is always the last one at the door
* Ok, UNICODE is…. Wait, which Unicode are you talking about?
* Klingon software does not have bugs. It has features, and those features are too sophisticated for a Romulan pig like you to understand.
* Computers are like bikinis. They save people a lot of guesswork.
* If debugging is the process of removing bugs, then programming must be the process of putting them in.
* Testing can only prove the presence of bugs, not their absence.
* A known bug is better than an unknown feature.
* Real Programmers don’t comment their code. If it was hard to write, it should be hard to read.
Posted by
Anurag
at
Thursday, July 09, 2009
1 word of wisdom
Subscribe to:
Posts (Atom)