Everyone likes to claim how they can "reproduce the bug," which is fine, but if you claim to know what causes the bug the you in theory can also turn off that bug. New York Times addresses this as confirmation bias ('') which is a huge problem in almost all problem solving. I suspect 99% of people seeing battery issues would see battery life change with a reboot whether or not they update their OS or not) * 99% of blaming new builds never tries to revert to an older build to compare the difference. * An update usually is accompanied by a reboot so all sorts of things can change even with a reboot (see this whole android ROM development scene story above. And then when there are commits, it's frequently translation updates only and all of a sudden you get battery posts about how the latest build makes a night and day difference. I worked on the Android ROM Development side of things and it was hilarious how people would blame bugs on nightly builds despite no commits in the past 48 hours. It's easy to blame 16.3.1 when it could be a whole host of issues. The issue is most people are horrendously bad at diagnosing complex issues. I don't like how Apple refuses to allow downgrades, especially when their upgrade screws something up. If you're the one person affected by the bug introduced in the newest OS, the newest OS is hot garbage in your eyes. One death is a tragedy, one million deaths is a statistic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |