|
|
|
|
|
|
by JamesBarney
2900 days ago
|
|
|
> The cost of fixing a discovered bug seems to grow exponentially with the amount of code in which the bug may appear. I don't think this is true.
Fixing a bug is comprised of four parts.
1. Understanding and reproducing the bug. 2. Finding the code responsible for the bug. 3. Coming up with code that fixes the bug. 4. Verifying that your fixing code does not introduce any new bugs. #2 is the only one that could even theoretically be exponential. The only bugs I've found where I've spent days on 2, were hard to reproduce, intermittent, race condition bugs, which units tests aren't very good at finding anyway. |
|
|