News for hackers. Stuff that matters.
Re:How Big Is YouTube? by pants2 on Saturday December 23, 2023 @01:07AM (#38742042)
That's typically the Lincoln-Petersen Estimator. You can use this type of approach to estimate the number of bugs in your code too! If reviewer A catches 4 bugs, and reviewer B catches 5 bugs, with 2 being the same, then you can estimate there are 10 total bugs in the code (7 caught, 3 uncaught) based on the Lincoln-Petersen Estimator.
Re:How Big Is YouTube? by mewpmewp2 on Saturday December 23, 2023 @02:05AM (#38742278)
But this implies that all bugs are of equal likelihood of being found which I would highly doubt, no?
Re:How Big Is YouTube? by pants2 on Saturday December 23, 2023 @02:40AM (#38742407)
Yes, it's obviously not a perfect estimate, but can be directionally helpful.

You could bucket bugs into categories by severity or type and that might improve the estimate, as well.

Re:How Big Is YouTube? by cpeterso on Saturday December 23, 2023 @02:17AM (#38742309)
A similar approach is “bebugging” or fault seeding: purposely adding bugs to measure the effectiveness of your testing and to estimate how many real bugs remain. (Just don’t forget to remove the seeded bugs!)

https://en.m.wikipedia.org/wiki/Bebugging

Re:How Big Is YouTube? by rightbyte on Saturday December 23, 2023 @05:56AM (#38743251)
Oh this is a really interesting concept.

I guess it underestimates the number hard to find bugs though since it assumes same likelyhood to be found.