Getting <100% coverage means you have no idea what some of the code does when run in dumb, non-parallel mode. Thar be bugs! And those bugs are easier to find t

Getting <100% coverage means you have no idea what some of the code does when run in dumb, non-parallel mode. Thar be bugs! And those bugs are easier to find than the ones that might still exist if you have 100% coverage. No one ever anywhere (except for numerous strawmen) has claimed 100% coverage "will eliminate all bugs and produce the perfect software." > This article is useless. Everybody knows that 100% code coverage doesn’t eliminate bugs. A double-secret strawman is still a strawman, dude. > Junior developers certainly don’t know this. Misguided team managers don’t know it as well. Great. Do they read your clickbait? If so, do they believe it (on authority, I guess)? Because unless they do, you're certainly a problem and not part of a solution.