Comment by mjw1007
2 years ago
Well, I'm baffled then. From where I'm sitting that point 8 is clearly talking about what happens after a bug is discovered, and not about discovering bugs.
The longer paragraph doesn't seem to contradict the notion either. My impression (based on the "How Many Eyeballs Tame Complexity" chapter) is that Raymond thought that "debugging" means "fixing bugs".
If I were criticising this part of essay, I'd say the main weakness is that the things Raymond thought of as "taming complexity" weren't really addressing the hard problem of reducing the number of bugs.
As I mention upthread, a lot of the talk at the time was about overall quality of the software. So an interpretation that the total number of bugs (known and unknown) would be reduced is well aligned with this outlook.
If the objective is just to fix bugs that have been found, well, that doesn't really feed into this narrative. Also, ESR was making many claims about the efficacy of OSS, and limiting the scope to bugs already discovered would not really align with the rest of the goings-on at the time.
"Characterizing problems" reads to me like "discovering bugs," particularly given that he specifically mentions having lots of beta users.