Discussion
pebblebed ventures
jeffbee: Bugs Georg, who is an outlier and should be excluded from the analysis.
petterroea: Not happy with the lack of statistical testing, some of the smaller differences in % could probably be coincidence
dogleash: These smell like the kind of metrics that cause someone to feel informed and then to miss the forest for the trees. The kind of data for a "data driven" decision maker who will just invent a narrative to explain the numbers, and then do what they wanted to do all along.The map is not the territory.
palmotea: > These smell like the kind of metrics that cause someone to feel informed and then to miss the forest for the trees. The kind of data for a "data driven" decision maker who will just invent a narrative to explain the numbers, and then do what they wanted to do all along.We need to increase reliability in the kernel, so the kernel team should fire the top 5 bug-introducers, to reduce the amount of bugs being introduced (https://pebblebed.com/blog/kernel-bugs-part2/05_author_analy...). Linus has got to go.
gchamonlive: > We need to increase reliability in the kernel, so the kernel team should fire the top 5 bug-introducers, to reduce the amount of bugs being introduced (https://pebblebed.com/blog/kernel-bugs-part2/05_author_analy...). Linus has got to go.You've cut bugs being introduced while also reducing development costs by slashing team size. You deserve a promotion and an increase in equity.
kittikitti: The author might have feared retaliation by corporations, even though retaliation is against corporate ethics. It might have also presented misleading statistics. However, I believe they're important to discuss. Therefore, I'm providing the bugs/commit ratio here, in the order of total number of bugs:Intel -> 11.86%Independent -> 1.42%Red Hat -> 9.74%Kernel.org -> 12.07%Linaro -> 12.73%Google -> 12.78%AMD -> 9.70%
charcircuit: I'd also like to see this broken down for C vs Rust.
kittikitti: I'm not sure why this isn't included in the blog, but I was curious about the ratio between bugs and commits. Presented here are my calculations in order of total number of bugs:Intel : 11.86%[1] Independent : 2.27%Red Hat : 9.74%Linaro : 12.73%Google : 12.78%AMD : 9.70%The above is based on the bug count table in the article.[1] I combined the total bug count for independent and kernel.org because they are combined for the total contributions here, https://github.com/quguanni/kernel-archaeology/blob/main/scr...This suggests that corporations are introducing significantly more bugs than independent developers. However, I have not done statistical testing on this nor have I recreated the numbers. If I had to speculate, I would assume that the analysis from the author was partly vibe-coded or they purposely left this analysis out due to fear of retaliation. Extending my speculation would also include that corporations are purposely introducing bugs out of malice such that there are backdoors available for them. The author mentions that there is no "corporate takeover" but perhaps there are more interesting conclusions to be found.
PowerElectronix: You can feel IC fear of being roasted by linus in those numbers.