3 ms·
> These huge CPU sinks making it through to release required nobody to even glance at a CPU graph. Every bug looks egregious in hindsight; just because an app
by fenomas 10y ago
> These huge CPU sinks making it through to release required nobody to even glance at a CPU graph.
Every bug looks egregious in hindsight; just because an app has one is no reason to assume the engineers who made it don't bother to test anything.
Also: that particular issue only hurt idle CPU usage, and the usage was something like 13% CPU usage IIRC. It wasn't exactly the kind of thing that sets off klaxons.
- josephg 10y ago> Every bug looks egregious in hindsight Most bugs are of the form "do X then Y then it doesn't work". These idle CPU bugs are reproduced simply by opening the application. I accept that 13% idle usage is invisible for most developers - but that's a bit disappointing. I notice stuff like this just by idly glancing at my CPU meter from time to time. An app that's sitting on high idle usage sets off klaxons for me.
- fenomas 10y agoYou're missing my point. All software has bugs; something always "makes it past test". Pointing at whichever bug did make it into production and saying "gosh those developers must not be testing anything" is silly.