If my oven has enough of a computer to have a firmware that can be updated remotely, it is too dangerous to own.
If my oven has enough of a computer to have a firmware that can be updated remotely, it is too dangerous to own.
For some reason, they are often better along many axes: cheaper, easier to clean, more customizable, more powerful, more flexible, etc.
I really like the professional induction stoves, with actual physical dials, no touch crap.
And the best part, there is a huge used market for professional appliances in really good shape, for even lower price.
My oven stops working with some nonsensical error message when I try to use it above 350F, so I'm in the market for a new one.
Any particular brands on the induction stoves? I may want to move on from gas someday.
Other than that though, and I have a lot of professional cooking experience, I wouldn't. They're generally uninsulated, made of just sheets of stainless steel. Touching them can burn you, they can have sharp edges and corners that can badly cut.
Their safety assumes frequent and thorough cleaning regimes. Where a residential system will have safer failure modes if not maintained correctly, a commercial one may just become a grease fire instead.
Also the dimensions and their dynamics just are often not good for the kinds of cooking you do at home. It takes an hour to heat a full-size uninsulated commercial stove's oven to baking temp. Commercial gear is generally built around that assumption: that you will turn it on once, every single day, and run it for 12-18 hours straight. That completely changes the design, efficiency, and maintenance constraints in ways that may not work at home.
I used to want a big two-basic stainless commercial sink with sprayer. I stayed in an airbnb with that once, and it turns out it takes several gallons of water to fill that even a few inches, a minimal amount to wash dishes. A restaurant's water line can do that in seconds, it can take minutes on a home one, depending.
There are definitely specific, individual pieces where the commercial versions are easily adapted to home use and superior. There are many more cases where they aren't. A blanket "buy commercial" is not good advice imo.
If anything, the consumer grade stuff tends to all be made roughly the same, and in many cases is just someone slapping their brand on an OEM appliance.
https://www.homedepot.com/b/Smart-Home-Smart-Kitchen-Smart-F...
I would be concerned that Alexa would turn on the faucet silently without me knowing, potentially causing a flood.
I think this is the key right here. They want to reduce the life expectancy of kitchen appliances to force people to buy new ones sooner.
"Can you show me only the non-smart appliances, please? Oh, you don't have any? Are you sure, can you ask the manager? Alright, I'm not interested in anything, have a nice day."
Sure, it doesn't mean very much on your own, but neither does voting - the value is in collective action. If everyone who specifically doesn't want a smart appliance, smart car, or smart TV makes a big deal about it, then manufacturers and retailers will start to notice.
Last time I went to buy a refrigerator, there maybe only one or two that were freed of the extra features that I did not want, compared to the 30 or so that were on display. And TVs without wifi were nonexistent.
Even if a regulatory solution is ideal (which I'm leaning toward), corrupt politicians will make it very difficult to get that regulation enacted, which means that "voting with your wallet" and making a big deal about it are both still necessary in the meantime, and will provide some benefit if done en-masse.
I recently bought a thirty year old home complete with its contents whose owner was an old man. The newest thing in it was an air conditioner from 2007. Know what? Every single thing is in perfect working order. AC, fridge, stereo, dishwasher, washing machine, dryer, thermostat. The list goes on and on. Everything from electric can openers to garage door openers works like it was brand new. If Google can't match that standard it can get stuffed.
Many Texans discovered this the hard way.
Things like that is where I wish local-only home automation had become more prevalent. Imagine if your washer or dishwasher could send a "completion reminder" to your home assistant to push to you. No need for a dozen different apps and C&C servers, just a local MQTT or SNMP like message to the on-prem hub or listener.
This is a keeper.
EDIT for disbelievers: The software update meant for an oven successfully installed on a microwave, and bricked the microwave because it was writing instructions to the wrong addresses. Why believe the software would never accidentally write to the 'heating element relay' bit in an oven?
Specifically my laser printer has a thermal bypass switch, my smartphone(s) have charge controllers integrated into the batteries, my water heater has a pressure release valve, my oven is literally designed to withstand max heat for an indefinite period of time, my garage door is a death trap in four different ways (but has redundant safeguards for all of those), my kettle has has a thermocouple that trips when it boils dry etc. etc.
From a micro-morts perspective, adding “electricity” to an object makes it significantly more dangerous than adding “internet”. Ie going from a hand grinder to an electric grinder. But the utility is worth the trade off.
My threat model allows me to be completely cavalier with a dishwasher. I would be considerably more serious with safety concerns were I to put a chemo machine in my garage. My suspicion is that people who haven’t shipped home appliances connected to mains are not aware of how much of the engineering effort goes into making these machines safe relatively to how little it does for adjacent categories and are mis-indexing risk over bigger issues like vendor lock in as with the Sonos upgrade fiasco a few years back.
From what I recall your background was in industrial machines and I concede the point that if sent an inappropriate signal, disaster would ensue. I don’t connect my CNC machines to my network but I meant to scope this discussion to home goods which are meant to have a lot of protections built in - specifically against the “user” - which compared to “internet” or “electricity” will always trump unpredictableness :-)
The WiFi functionality is also such total garbage that it'll only stay connected for a few days, and requires physically unplugging and re-plugging the power to the oven to get it to reconnect.
That it's possible at all suggests that the oven is only one bad firmware update away from turning itself on when you don't intend it.
Conceivably such a limitation could be built into the hardware; e.g. with a button that works like a circuit breaker. Set to break after the oven starts once and requiring the user to manually reset it. But the odds of it actually being implemented in this way, rather than pure software, is virtually nil.
Also, because of the crappy WiFi it's almost never connected anyway.
I'm not sure I'd be willing to believe a manufacturer on this. This feature is probably implemented in software, rather than hardware - simply because it's cheaper.
The idea of any of these home appliances being internet connected really blows my mind.
I worry that agile is largely responsible, and has mutated into a pipeline for garbage, though I don't have any evidence to confirm that suspicion.
I got involved in that movement before the word "Agile" existed; I was really interested in the ideas coming from the Extreme Programming folks and had tried them out on a small project in 2000. All of the people I met early on really wanted to do software well; the question was how to do it well and responsively. Unit and acceptance tests were just part of the process [1], and Kent Beck also wrote Test Driven Development By Example [2] around then. So in my view there was strong early interest in quality.
But this was all happening during the rise of the internet, which changed people's expectations for software delivery. Previously, releasing every 18 months was seen as reasonable. Suddenly the web was changing people's expectations. (Although not as fast as you'd think; a consultant pal told me in 2004 that Weight Watchers still had an annual release cycle for their website.) Executives and managers were under pressure to deliver faster.
As I wrote about elsewhere [3], that created a need for Agile that was filled not by the humanistic culture and quality-oriented practices of my end of the Agile world, but by consultants and certification programs watering down the material until executives could slap some new labels on their same old bullshit and call it Agile.
It turns out that bullshit long predates Agile. If you go back to Royce's original 1970 paper on Waterfall [4], one of his big points is that it doesn't work. Why, then, did it become the predominant way to organize software projects? Because it feels good to managers. For most of the project, it gives them a feeling of control and competence. That feeling is false, as it just delays all of the real-world feedback until near the nominal end. But they can perform confidence and competence to their boss, which is vital in managerialist [5] organizations.
So I totally agree with you that Agile on average has mutated into a garbage pipeline. And that happened through a whole industry that produced manager-friendly process theater that threw out a quality focus and most of the Agile values, while using the Agile labels. But I think the real responsibility lies in our management culture and values, which both precedes Agile and whose harm extends well beyond it.
[1] http://www.extremeprogramming.org/map/loops.html
[2] https://www.oreilly.com/library/view/test-driven-development...
[3] https://web.archive.org/web/20170923232057/http://agilefocus...
[4] https://pragtob.wordpress.com/2012/03/02/why-waterfall-was-a...
[5] See, e.g., https://www.bloomsbury.com/us/confronting-managerialism-9781...
Waterfall is not just "feels good" - it decouples their evaluation from their performance.
Until the end, everything is good because there's no measurement to show otherwise. At the end, measurements that show things have gone wrong merely prove that some past manager failed.
The only way to fail is to be a manager throughout the whole project, and management rotations guarantee that that never happens.
It's not just software. The scheduled manager tenure at at least one of the largest semiconductor companies is one year shorter than the design->ship cycle.
And I'd add that at the end of the waterfall cycle, metrics often (and incorrectly) show that the workers failed. After all, they said they were 95% done just a bit ago, and now they're suddenly not done. It's very easy to shift blame to them.
As contrast, a lot of the effective Agile techniques don't actually fix problems; they just shorten the feedback loops so problems surface sooner. That's part of why fake Agile won out; managers didn't adopt any of the bits that would make them feel uncomfortable or expose the very real problems with how they run things.
If the grid is very slightly over 50hz it means demand exceeds supply and vice versa.
By automatically switching off the pump on thousands of fridges for a few seconds, networks would require less generation capacity on standby - saving $$$ and CO2.
Of course, like you say, this would leave potential for this to be used in reverse to destabilise an entire grid.
Not to be too pedantic, but it's actually the opposite. Frequency drops as demand goes up, which requires more supply to compensate. This is because the generators physically spin more slowly as they are put under more load.
Also occurs to me that it's 60hz in North America, but point roughly remains!
> It's a toaster, just like the one you already have on your counter, except it won't work unless you give the manufacturer a copy of your rolodex.
People then would laugh in your face, but today most people don't even seem to blink. The absurd has been normalized.