My fascination with Nest thermostat, then product of Nest Labs, ended as abruptly as it began. It happened on the chilly afternoon of 2014 New Year’s Eve. I just landed in Seattle after two weeks in Europe. As soon as the plane stopped, I turned on the phone, launched Nest app (which happily measured 42 F in my home), and turned on the heating. Nest app responded with glowing indication that heating is on. Two hours later I stepped into my living room and it was as cold as outside. 44 degrees to be precise. What happened? Auto Away mode has kicked in and turned the heating back off before I even reached the parking lot.
Every software has bugs. This bug, however, was special not because of its sheer idiocy (admittedly, Apple’s infamous alarm clock bug was much worse), and not because a half-decent test engineer would find it in minutes after reading the spec. It was special because momentarily, it negated the whole purpose of Nest existence. From that point on, I think twice before enabling automation in any aspect of my life that directly translates into physical well-being.
Denny so you think with more data they will make better decisions? It's not like lack of data was the problem here, or with July morning heating. More data will probably mean more opportunity to screw things up. More chaos. Incidentally this is my problem with some of the "big data" startups.
So it's menu Chrome > Hide Notification Icon but command implementation is buggy so it doesn't always work. Why doesn't Chrome use Notification Center, which is more organic, more flexible, less buggy, less annoying way to deliver messages in OS X?
"All they're doing is trying to port a bug in the Internet over to the real world, and calling it progress." I have enormous respect for Maciej Ceglowski. So much good stuff in there. (Via O'Reilly, of course.)
Fairy tale. I don't believe it one second, but it nicely illustrates two important issues of 2014: a) Google search is now ripe for disruption b) cultural divide between ad-ridden and ad-less deepens.