Amazing story! I maintain a network library on iOS where we have automated this process: a merged pull request earns the author an automatic invitation to join the project. The code is at https://github.com/Moya/Aeryn if anyone is interested.
The scapegoat for what was clearly an organizational failure. Why was the system using multiple units of measure. Did it pass navigation tests prior to launch? Was the test flawed?
I think OP was making a subtle joke about titling it "5 bugs" but providing metric 5 aka 6 in the article to cause a buffer overflow in the article itself. Which the buffer overflow in the article the 7th bug. Personally I think a recursion fail would have made a funny additional article bug, but buffer overflows are funny in their own way too. Or a picket fence / off by one error would have been funny like iterating from 1-5 to output the bug list where the bugs are enumerated beginning at zero... so why didn't we see bug 0 and the crash at bug 5 would have been pretty funny.
The story is normie clickbait anyway, and most of the bugs aren't mismatches between the source code and the (possibly non-existent) unit testing infrastructure, they're just cultural examples of blaming the lowest social status individual involved, that usually being a programmer. There was a programmer involved, someone in management screwed up and doesn't feel like taking the blame, therefore its the programmer's fault. In the olden days they'd just have blamed the closest (insert ethnic group here) or (insert religious group here), nothing really to be proud of.
