6 ms·
It's wild to me that people expect computers to work, all the time. I just sort of shrug my shoulders and roll with it. Then again, people freak out when thei
by thrower123 7y ago
It's wild to me that people expect computers to work, all the time. I just sort of shrug my shoulders and roll with it.
Then again, people freak out when their car or their lawnmower doesn't fire right up on the first crank, too.
I guess I've just dealt with so much broken, flaky stuff my entire life that it doesn't even faze me anymore.
- adambatkin 7y agoNo one questions that there are bugs in software. The issue raised here is that users were unable to perform searches - even for local files - and the cause (apparently) inexplicably involves a network. In other words what could Microsoft possibly be doing that would prevent a local search from working due to a network or server failure. If I ran the *nix 'find' command on a local filesystem and it segfaulted, I'd be annoyed (I'd also know how to debug and possibly fix) but (like you said) sometimes stuff breaks and that's life. If I ran the same command and got an error message about a network or server failure, my next steps would likely involve a yanked power cord, some forensics of my disks and a format and reinstall of everything on my computer.
- thrower123 7y agoMy first thought would be somebody threw an unhandled exception in the telemetry code, and since there isn't anybody doing QA anymore, other than you and me and a billion other users. Probably a "worked on my machine..." I'm only half kidding.