|
There is something to be learned from a bugstorm. When meeting with a sudden shower of bugs, you try not to get crazy and debug quickly along thousands of lines of source code. But doing such things as watching for variables, commenting out some parts of code, inserting breakpoints you still get bugs. When you are resolved from the beginning, you will not be perplexed, though you still get the same number of bugs. This understanding extends to every software.
Perlagure -- The Way of The Perl Programmer |
Re: There is something to be learned from a bugstorm...
by Anonymous Monk on Nov 03, 2003 at 17:45 UTC
|
There is something to be learned from a bugstorm.
Well, one thing that can be learned from a bugstorm is the value of a
test first development model :-)
| [reply] |
|
|
Well, one thing that can be learned from a bugstorm is the value of a test first development model :-)
People test first before deployment? And there was me thinking my QA dept were just a like any other group of screaming users! Silly me - my QA dept and ${GROUP} screaming users are one and the same. Seriously now, Big Ball of Mud is such a familiar pattern by now that maintainers either take the "Don't touch - it will break" or "Fix it - fair means or foul" approach. I commend the later, even if sometimes foul means == bugstorm.
the only bad experience is the one you've learned nothing from
| [reply] |
|
|
| [reply] |
|
