h a l f b a k e r yThese statements have not been evaluated by the Food and Drug Administration.
add, search, annotate, link, view, overview, recent, by name, best, random
news, help, about, links, report a problem
browse anonymously,
or get an account
and write.
register,
|
|
|
Please log in.
Before you can vote, you need to register.
Please log in or create an account.
|
Getting a large meal prepared can be a complicated process. Even a two-pan deal can stretch the novice. Enter the "Interactive Event Driven Recipe Book".
First step is to search for the recipes that can be completed to time and cost e.g. 6 hours to go, not using a blender, under $10 per head. You
have selected "English Roast Beef Dinner".
[Start]
IEDRB> Please check you have all the ingredients (various check boxes appear).
[Continue/Re-choose Recipe]
IEDRB> Please select a meal time and cooking expertise
[20:00]
[Novice/Average/Expert]
IEDRB> Your first cooking step will begin at 17:30
IEDRB Alert> First step: Prepare joint of beef.
(instructions follow etc until the event driven portion takes over)
IEDRB Event Chooser> (Please check all relevant events)
[Fork test on potato pan (top left) has succeeded]
[Broccoli pan (top right) has started boiling]
[The meat is looking very brown]
[Smoke detector has sounded]
IEDRB> Turn the potato pan ring (top left) off. Drop the broccoli into the pan (top right).
---------------------
This could be of use to people trying complicated recipes, but while writing it could have well applied to me making boiled eggs with toast. I could neither judge a perfect soft boiled egg (is "large" the large where I am), or just remember that 6 rounds of toast takes longer than 5 minutes.
Dinner party tip: Dishwasher the plates just prior to the meal and then it doesn't matter if some side-dishes are going cold as the plates will be hot. Either that or place them in turn over the veg. pan to steam heat them.
IEDRB Alert> Start the dishwasher.
Shamless small business promotion.
http://www.dinnersolutionscanada.com/
There's no need to be Alfredo. [2 fries shy of a happy meal, Dec 18 2008]
[link]
|
| |
Sounds like that cooking game for DS. |
|
| |
sounds neat, but a cookbook & basic math skills... |
|
| |
//Sounds like that cooking game for DS// |
|
| |
Sounds very close indeed apart from the event driven stuff. That games looks like quite a refinement from a print-out, but I wonder if it goes as far as using user-event acknowledgements to modify the cooking process e.g. ackowledging the time between a boiling pan of water and the time it takes to re-boil after chucking a portion of frozen veg. in. The idea doesn't express that explicitly but that was the intention i.e. a meeting of what you have available and what the recipe expects you to have. Less training, more coping. |
|
| |
I'm one of those people who think that cooking ability can only be achieved through experimentation and practice. Like playing a musical instrument - you can buy as much sheet music as you like, but it'll all come out bollocks if you haven't figured things out like scales and arpeggios. Yes, it's possible to explore without these fundamentals. Cheese on toast is the cooking equivalent of 'chopsticks'. |
|
| |
I see your event-based analogy - and I'm guessing that 'event based' in this context is referring to the way that VB is 'event-based' as opposed to, say normal 'basic' which just runs normally. Which is fine, except VB is only superficially event-based. Really, it's just the same as normal basic, it's just been embedded within a semi-opaque layer of proprietary stuff. |
|
| |
If you take away the Microsoft mystique, 'event-based' things just mean having to go through tedious sets of ticklists that test the prevailing environment for its current status before activating the appropriate procedure. |
|
| |
Which, I suppose isn't a bad way of cooking - some actions "DO" things, while others just "TEST" that a certain set of criteria has been met. People who get confused by cooking might find it helpful to be shown explicitly that some actions are "DO"ing actions (stuffing a turkey, stirring the sauce, or placing an egg in a pan of boiling water), while others are merely "TEST"ing ones (throwing pasta at the wall, prodding vegetables, waiting for a rolling boil etc). |
|
| |
Failing to be able to tell the difference might make all of that activity you see in the kitchen seem quite arcane. |
|
| |
I sort of agree with [z_t] here - bombarding the person who's preparing a complex multi-dish meal with a big list of step-by-step instructions and tests won't actually help if they haven't already acquired the base skills necessary to carry out those instructions. E.g. the fork test on the potato pan - you only know from experience exactly how hard potatoes need to be, and how hard they need to be if you've got 15 minutes until you start eating and you've got to take into account that they'll carry on cooking a bit after you take them off the heat. |
|
| |
Not sure this is event driven cooking, more of a paged tutorial. Event driven cooking, to me, would be a system by which certain events in the cooking (the water reaching boiling point) would directly drive an action (water being pumped into a pan). |
|
| |
[Smoke detector has sounded] |
|
| |
I burnt your croissant, sorry. |
|
| |
I like that idea [vince³]- some Reub Goldbergian arrangement of ingredients, cutlery and springs that manages to both cook and serve itself on a plate. |
|
| |
I like the concept, if not the idea (if you know what I mean). What you describe, [bigsleep], appears to me to be a procedural or algorithmic approach that isn't necessarily event-based. |
|
| |
The advantage of an event-based system is that you schedule the events and then only have to deal with them at their scheduled time. (In simulations, this means that the program zooms forward to next event in the queue, rather than waiting until the allotted time). |
|
| |
Therefore, I think your description needs to make clear that there would be a system clock, to which events are attached (in a queuing system) and then made easy for the user to deal with:
ON pan - scehdule TEST event 20 minutes from now.
...
TEST potatoes; if done, OFF pan - schedule new event: serve in 5 minutes
etc. |
|
| |
Nice. Sounds almost exactly like what I've been doing after work every day for months now. |
|
| |
//The advantage of an event-based system is that you schedule the events and then only have to deal with them at their scheduled time// |
|
| |
The system was meant to be real event driven and not scheduled event e.g. when the pan starts boiling click here. This may raise scheduled events as a consequence e.g. take the pan off the heat now. In fact the whole concept is that a recipe should not be scripted down to the microsecond but should be interactive according to the timings you find yourself actually using e.g. forgetting to turn a pan on or putting the oven on the wrong setting. The novice setting would build in enough spare time to redo some steps e.g. getting a sauce wrong. |
|
| |
If you haven't already acquired some basic skills, the instructions would have to be ridiculously detailed... most likely to the point of totally overwhelming the hapless novice. |
|
| |
This might be great for the cooking automatons of the future but people seem to learn better by imitation. |
|
| |