4 ms·
Actually, the idea that most bugs are produced by faulty modules, and that such faulty modules don't produce fewer bugs as a result of efforts to fix them (and
by gruseom 18y ago
Actually, the idea that most bugs are produced by faulty modules, and that such faulty modules don't produce fewer bugs as a result of efforts to fix them (and so are best thrown out), is one of the few interesting results produced by experimental studies of software development. So I don't think it should be dismissed so cavalierly.
I don't have time to track down the original sources on this, but I do remember that one of the places I read about it is in Robert Glass' Facts and Fallacies of Software Engineering, which is worth reading because it's (a) well-grounded in the research literature, yet (b) not stupendously boring.
It's worth noting that the findings in question have to do with rewriting faulty modules and not to do with rewriting entire systems (which is a quite different matter). But this is also what the OP was talking about, so I think this evidence, for what it's worth, supports her claim.
- jwilliams 18y agoAgreed - the distinction is between (1) the code is simply buggy and (2) the code is full of bugs because the design is wrong/inadequate. I've realised over time that fixing a bug in a decent design is a lot of the value (of software). A single line of bugfix can be worth reams of new code. It's why banks are still running COBOL mainframes.