My system looks like it was put together by a drunk person. That is somewhat true.
This made want to see it even more.
Much closer to genius is the thermomix: https://thermomix.com/
A malfunctioning lid caused hot liquid to escape from the bowl, giving several consumers severe burns. The Court found that Thermomix knew of this risk but still continued to promote and supply the faulty product.
Beware of genius inventions, you may get burned.
I've found that a lot of meals done via the slow cooker tend to taste the same because of the consistently and the type of ingredients typically involved in them.
1.) My hi/low setting probably doesn't match your hi/low setting. From the get go, we're cooking the same meal at two different temperatures.
2.) A lot of recipes seem to call for low setting for 8 hours. This works well for a lot of people with a standard American work day, since a stew/soup will stay above safe warming temperature in a nearly sealed pot. However, the cook times are too long. Thawed chicken for 8 hours on low almost never turns out with the right texture. In this case, it's convenience > taste.
3.) The flavor is cooked out of the ingredients, and/or there isn't enough seasoning or too many ingredients. When you get the seasoning right, too long of a cook time can dull the flavor. When there isn't enough seasoning, then your meal is bland from the start. When there are too many herbs and spices, you get a mish-mash of flavors that are all competing for attention. There was an article on here a long while ago that categorized foods into low and high amplitude flavors. Something sharply distinctive was high amplitude (think nacho cheese Doritos), while a low amplitude food had weak, hard to discern flavors (plain grits). Too many different ingredients can lead to low amplitude foods, and when I see an ingredient list with 15 different herbs and spices, I almost always steer clear.
Brown a flank steak in a pan. We're not sealing in juices - we're making a crust. Throw it in the slow cooker for a few hours. Check to make sure it's tender. Prep some veggies by cutting and portioning them in containers. Find a stew sauce that's simple. When you're ready to eat, saute your veggies in a little oil, and add a generous portion of sauce when your stir fry is near complete. Throw in the meat towards to end to heat. Serve over potatoes or rice or something simple.
While it does double as a slow cooker, I have never actually used that functionality.
Sous-vide much more specialized, but I find super useful not for saving time, per say, but being more flexible about it. It's great when you are doing other things at the same time as cooking dinner, i.e. - leave the steaks another 30 min while I do this chore? no problem....
"I am rarely happier than when spending an entire day programming my computer to perform automatically a task that would otherwise take me a good ten seconds to do by hand."
Sometimes it simply isn't about net time saved.
I don't really save much time. The real benefit is knowing that the food won't burn. Growing up my mother would make soups and stews, she'd leave them to simmer for 30 mins without checking. The food on the bottom of the pot would burn and make the whole thing taste nasty. I wanted to make a system that would prevent that, whereas my son just loves building robots and playing with motors.
It was as much a project for me and my son to mess around with as much as an actual kitchen time saver. But we have plans to develop it and just see where it goes.
It has a very "Wallace and Gromit" sounding vibe to me!
We recently started cooking meals for the week ahead on Sundays and then freezing them. The aim was to give us more time with the kids and to cut down on housework.
To save time on the Sunday cooking session I have cobbled together a very clunky, and I mean VERY clunky semi-automated cooking system. It comprises a Raspberry PI which controls a couple of WiFi mains switches attached to the induction hob and the slow cooker. A wooden spoon attached to a 360 degree servo motor hangs above the pot on the hob and can be activated by the Pi for stirring. Initially I tried to use one of those cheap three-legged novelty vibrating pot stirrers, but that didn't work out. Thermocouples feed back to the Pi to help control cooking.
The whole thing is controlled by a messy Python script and 'recipes' are JSON based text files. They just define how long each device should stay on, a max temp to turn them off and how often they should be stirred. I get an email when cooking is done.
I plan to add some functionality over the summer to tip in ingredients as needed. The biggest issue is that it doesn't handle chunky food, it works for soups, chili sauce, pasta sauce etc. I'd love to figure out a way to fry and separate mince as you would with a spatula..