6 ms·

> Once you hit start, no timer is present. You have no idea how long it's going to take (turns out, about an hour). The rice cooker doesn't know either, it wil

> Once you hit start, no timer is present. You have no idea how long it's going to take (turns out, about an hour). The rice cooker doesn't know either, it will take whatever is needed to take. Short of putting an extensive sensor array and ask you for the kind of rice you put in it, there's probably no way to actually predict it. On the quick/normal setting, they taste different. My best image would be on black tea: you can use 95C water or near 100C water, one is quicker than the other to fully extract the flavor, but won't result in the same profile (you might actually prefer the quicker one, your choice) On the UX...welcome to a world where you buy products of different cultures. If that helps, many people don't actually follow the dosing cup to the letter and adjust the amount of rice and water to their taste, relative the rice we're using at that time after a few tries (at least I do, and so does anyone I talked to), so there is no guideline that would help us. I'd perhaps compare it to coffee, there are machines doing it all automatically but they taste bland, and the better tools will expect you to know what you're getting into. Rice cookers are as serious business in Japan as espresso machine in Italy, you won't get a high end machine that catters to people who're not familiar with what's going on.

solardev 3y ago
Hmm, thanks for explaining the profiles. I'll try a few and see how they taste. > The rice cooker doesn't know either, it will take whatever is needed to take. Short of putting an extensive sensor array and ask you for the kind of rice you put in it, there's probably no way to actually predict it. Why doesn't it know when it's so consistent every time? How does the ninja know? How does this one know when it's closer to 10 minutes? Seems like you should be able to estimate it down to a within a few minutes at start, then refine that estimate if need be. It's helpful to know whether something will take 15, 20 min or 45 to an hour.
- kelipso 3y ago
  Different rice varieties have very different cooking times, also ratio or rice to water also influences the time, so the machine can't just estimate based on weight.
  - deleted 3y ago
    [deleted]
  - robocat 3y ago
    What sensor do high-end rice cookers have that varies the cooking dependent on the rice variety? Steam? Simple rice cookers have only a 100°C temperature sensor (or switch) that turns off the main element once the water is boiled.
    - kelipso 3y ago
      Some rice absorb water very quickly, some rice very slowly, some rice you want more water, some very little, sometimes you want to add other ingredients too. That's more than enough to vary cooking times but not be able to estimate cooking times via the sensor.
      - robocat 3y ago
        Obviously. My question is what sensor do they use to detect the difference? I did some Googling but couldn't find any info.
        azdle 3y ago
        IIRC, it's just temperature (and maybe time). Once the bottom of the pot goes above boiling, all the water has been absorbed/boiled off. Cheap rice cookers then just click over to warm, fancy ones might do something based on time, which can change based on other things like how log it took to come to a boil or how long between coming to a boil and the water finishing absorbing.
    - makeitdouble 3y ago
      Usually the cooker senses the temperature and amount of unabsorbed water left (conductivity ? ai forgot the exact input but Technology Connections had an excelent video on youtube on rice cookers for those interested). That's enough to manage a temperature curve and predict the last 10~15min of cooking (mine shows a time only 15min before the end), and doesn't require much input from the user.
- haswell 3y ago
  On the one hand, I can imagine some estimation solutions that all make me think about software installation progress bars. But on the other hand, if this is a piece of equipment you use regularly, you'll learn pretty quickly how long each thing typically takes, and after that initial learning period, the fuzzy progress indicator is no longer very valuable, and doesn't seem worth investing the engineering and UX time (and resulting higher product cost). As a software-oriented community, I understand the impulse to throw code at the situation, but this seems like a situation where the cost of doing so doesn't really help very much. And it might actually make things worse, since most users are conditioned to trust/believe the sensors/indicators they see, and a countdown that keeps dynamically changing/jumping/slowing will confuse quite a few people who don't understand why it's a hard problem to solve. And I think it's worth noting that this is par for the course with most things related to food prep. I'm always looking up cooking times for various things until I memorize the things that I cook often, and this seems like just another case of doing a quick search for a timetable.
  - kjkjadksj 3y ago
    Imagine you are making rice in this for the first time and you have no idea how long its going to take. That is ridiculous when you think about it. How do you even plan the rest of the meal assuming you won’t just be eating rice? Take the loss the first time and take 90 minutes to make dinner since the manufacturer didn’t have actually cooking with the thing in mind I guess.
    - Karellen 3y ago
      > Imagine you are making rice in this for the first time and you have no idea how long its going to take. How many times do you use it for the first time? Seems like a bit of an edge case to spend engineering time/add extra parts for.
      - solardev 3y ago
        I don't think this is some insolvable problem. It's literally estimating the time it takes to cook rice, and many other rice cookers (including other Z models, apparently) do this just fine. It's not some edge case, it's literally the biggest question after you push start.
- ilamont 3y ago
  > Why doesn't it know when it's so consistent every time? Because rice isn't consistent. This is most apparent with certain varieties - a cup of imported Basmati "Royal" brand will take longer and require more water than the same amount of "Three Elephants" Jasmine rice from Thailand. Even the same varieties produced by different brands/countries will turn out differently in terms of time required. This relates to differences in climate, storage, processing, and other factors.
- newsclues 3y ago
  It’s not a timer function but a sensor that detects signals the rices is done. Depending on environmental conditions (temperature, etc) and amount being cooked, will vary but the results are repeatable quality rice, rather than a fixed cook time and variable quantity rice. More expensive but better quality rice.
- mook 3y ago
  > Why doesn't it know when it's so consistent every time? They had a feature (that I believe it's just integrated into every model now) labeled as "neuro fuzzy", decades before the neutral networks boom. I believe it's really just describing hysteresis. So it's doing things based on feedback from whatever sensors they have, but there's no learning from run to run (based on how you actually use the thing). I also hate its lack of estimated times.
viciousvoxel 3y ago
A bit besides the point, and not exactly disagreeing with you, but in my experience (living in Italy for over a year now) most Italians don't own a high-tier espresso machine. They have a cheap aluminum moka pot or a nespresso pod machine or perhaps a lower-tier Delonghi, etc. As a coffee nerd this surprised me a bit. I think part of it is that frequent and mainly fast coffee is prioritized over great coffee. Also, you can go get an espresso made on a god-tier machine at basically any corner for 1-2 euro.

solardev 3y ago

Hmm, thanks for explaining the profiles. I'll try a few and see how they taste. > The rice cooker doesn't know either, it will take whatever is needed to take. Short of putting an extensive sensor array and ask you for the kind of rice you put in it, there's probably no way to actually predict it. Why doesn't it know when it's so consistent every time? How does the ninja know? How does this one know when it's closer to 10 minutes? Seems like you should be able to estimate it down to a within a few minutes at start, then refine that estimate if need be. It's helpful to know whether something will take 15, 20 min or 45 to an hour.

kelipso 3y ago
Different rice varieties have very different cooking times, also ratio or rice to water also influences the time, so the machine can't just estimate based on weight.
- deleted 3y ago
  [deleted]
- robocat 3y ago
  What sensor do high-end rice cookers have that varies the cooking dependent on the rice variety? Steam? Simple rice cookers have only a 100°C temperature sensor (or switch) that turns off the main element once the water is boiled.
  - kelipso 3y ago
    Some rice absorb water very quickly, some rice very slowly, some rice you want more water, some very little, sometimes you want to add other ingredients too. That's more than enough to vary cooking times but not be able to estimate cooking times via the sensor.
    - robocat 3y ago
      Obviously. My question is what sensor do they use to detect the difference? I did some Googling but couldn't find any info.
      - azdle 3y ago
        IIRC, it's just temperature (and maybe time). Once the bottom of the pot goes above boiling, all the water has been absorbed/boiled off. Cheap rice cookers then just click over to warm, fancy ones might do something based on time, which can change based on other things like how log it took to come to a boil or how long between coming to a boil and the water finishing absorbing.
  - makeitdouble 3y ago
    Usually the cooker senses the temperature and amount of unabsorbed water left (conductivity ? ai forgot the exact input but Technology Connections had an excelent video on youtube on rice cookers for those interested). That's enough to manage a temperature curve and predict the last 10~15min of cooking (mine shows a time only 15min before the end), and doesn't require much input from the user.
haswell 3y ago
On the one hand, I can imagine some estimation solutions that all make me think about software installation progress bars. But on the other hand, if this is a piece of equipment you use regularly, you'll learn pretty quickly how long each thing typically takes, and after that initial learning period, the fuzzy progress indicator is no longer very valuable, and doesn't seem worth investing the engineering and UX time (and resulting higher product cost). As a software-oriented community, I understand the impulse to throw code at the situation, but this seems like a situation where the cost of doing so doesn't really help very much. And it might actually make things worse, since most users are conditioned to trust/believe the sensors/indicators they see, and a countdown that keeps dynamically changing/jumping/slowing will confuse quite a few people who don't understand why it's a hard problem to solve. And I think it's worth noting that this is par for the course with most things related to food prep. I'm always looking up cooking times for various things until I memorize the things that I cook often, and this seems like just another case of doing a quick search for a timetable.
- kjkjadksj 3y ago
  Imagine you are making rice in this for the first time and you have no idea how long its going to take. That is ridiculous when you think about it. How do you even plan the rest of the meal assuming you won’t just be eating rice? Take the loss the first time and take 90 minutes to make dinner since the manufacturer didn’t have actually cooking with the thing in mind I guess.
  - Karellen 3y ago
    > Imagine you are making rice in this for the first time and you have no idea how long its going to take. How many times do you use it for the first time? Seems like a bit of an edge case to spend engineering time/add extra parts for.
    - solardev 3y ago
      I don't think this is some insolvable problem. It's literally estimating the time it takes to cook rice, and many other rice cookers (including other Z models, apparently) do this just fine. It's not some edge case, it's literally the biggest question after you push start.
ilamont 3y ago
> Why doesn't it know when it's so consistent every time? Because rice isn't consistent. This is most apparent with certain varieties - a cup of imported Basmati "Royal" brand will take longer and require more water than the same amount of "Three Elephants" Jasmine rice from Thailand. Even the same varieties produced by different brands/countries will turn out differently in terms of time required. This relates to differences in climate, storage, processing, and other factors.
newsclues 3y ago
It’s not a timer function but a sensor that detects signals the rices is done. Depending on environmental conditions (temperature, etc) and amount being cooked, will vary but the results are repeatable quality rice, rather than a fixed cook time and variable quantity rice. More expensive but better quality rice.
mook 3y ago
> Why doesn't it know when it's so consistent every time? They had a feature (that I believe it's just integrated into every model now) labeled as "neuro fuzzy", decades before the neutral networks boom. I believe it's really just describing hysteresis. So it's doing things based on feedback from whatever sensors they have, but there's no learning from run to run (based on how you actually use the thing). I also hate its lack of estimated times.

viciousvoxel 3y ago

A bit besides the point, and not exactly disagreeing with you, but in my experience (living in Italy for over a year now) most Italians don't own a high-tier espresso machine. They have a cheap aluminum moka pot or a nespresso pod machine or perhaps a lower-tier Delonghi, etc. As a coffee nerd this surprised me a bit. I think part of it is that frequent and mainly fast coffee is prioritized over great coffee. Also, you can go get an espresso made on a god-tier machine at basically any corner for 1-2 euro.