London Stabbie has been quite annoyed today. He has resurrected his old computer in order to ensure that everything useful is removed, and exported his recipe book this morning. Now there is nothing more useful in keeping and disseminating and sharing recipes than a computer. One would think that after many years of storing recipes on computers someone would have figured out a good way of exporting recipes and then importing them into another computer or another program. One would be wrong. Very wrong. As wrong as drinking shiraz with lemon sole.
Stabbie was amazed at the speed of the export from a very old version of Mastercook into a text file. Less than 5 seconds for 2MB of recipes (Stabbie has lots of recipes).
Stabbie then copied the file into his new computer and fired up Mastercook 11, guaranteed to work with Windows 7. Then he imported the recipe file, and while there were a few mistakes (reported by the software) most of the recipes seemed to be imported fairly well.
So Stabbie took at look at his mother's recipe for spaghetti and meatballs. He was surprised to learn that it required no meat, no tomatoes, but a lot of flour and sugar and baking powder. Somehow Mastercook had slipped a gear and missed out several recipes, putting the wrong labels on the subsequent ones.
So Stabbie deleted all the recipes, and opened the text file with the exported recipes in it. He now has to import them 10 or 20 at a time and go through each. Some have ingredients misplaced, and others don't have the instructions or notes correct. Stabbie has more than 1500 recipes in his database. He's not looking forward to the next four months.
Cooking software is written by dweebs for noobs.
This is also true for geneological software.
Stabbie would like to get the programmers, and especially the people who arranged the user interfaces and the import and export engines, into a very small dining room, lock them in, and feed them chocolate cake iced with Ex-Lax. The toilets will not be accessible.
Stabbie was amazed at the speed of the export from a very old version of Mastercook into a text file. Less than 5 seconds for 2MB of recipes (Stabbie has lots of recipes).
Stabbie then copied the file into his new computer and fired up Mastercook 11, guaranteed to work with Windows 7. Then he imported the recipe file, and while there were a few mistakes (reported by the software) most of the recipes seemed to be imported fairly well.
So Stabbie took at look at his mother's recipe for spaghetti and meatballs. He was surprised to learn that it required no meat, no tomatoes, but a lot of flour and sugar and baking powder. Somehow Mastercook had slipped a gear and missed out several recipes, putting the wrong labels on the subsequent ones.
So Stabbie deleted all the recipes, and opened the text file with the exported recipes in it. He now has to import them 10 or 20 at a time and go through each. Some have ingredients misplaced, and others don't have the instructions or notes correct. Stabbie has more than 1500 recipes in his database. He's not looking forward to the next four months.
Cooking software is written by dweebs for noobs.
This is also true for geneological software.
Stabbie would like to get the programmers, and especially the people who arranged the user interfaces and the import and export engines, into a very small dining room, lock them in, and feed them chocolate cake iced with Ex-Lax. The toilets will not be accessible.
no subject
Date: 2011-09-20 07:23 pm (UTC)What I really want to do is snag my granma's recipe box and scan those puppies in to my computer before she's gone and my cousin steals it all :P
no subject
Date: 2011-09-21 02:23 am (UTC)no subject
Date: 2011-09-21 06:18 am (UTC)Recipes are, theoretically, simply a rather complicated multi-level database. The difficulty is this: No recipe program actually enforces rules strictly enough (and, of course, loosely enough in other ways) to ensure that the database is clean. Exporting recipes (unless the user has been unnaturally strict and consistent in how s/he enters and cleans the recipes) thus becomes a Cecil B. de Mille production ("I'm ready for my soufflé, Mr. de Mille."...)
The recipes that I actually entered myself are good. The problem comes when, for example, a recipe has no ingredients, just a "method" or "instructions". This can happen with a recipe with a small number of ingredients, or some ingredients with no amounts. The program should not throw up its electronic hands, slip a gear, and put the next recipe's ingredients and instructions under the previous recipe's title.
What I would expect is that the program that exports the recipes to the text file would, if it finds something like that, make some indication that there's a rogue recipe in there and, perhaps, ask what to do with it or, perhaps, put that recipe in another file to await human intervention.
So, instead, I have to go through every one of the recipes fixing it. That's more than 1500 recipes. It'll take months unless my OCD takes over, in which case I shall be in the funny farm in a week or two, muttering about how much garlic it takes to stuff an elephant.
no subject
Date: 2011-09-21 06:19 am (UTC)no subject
Date: 2011-09-21 02:44 pm (UTC)how much garlic does it take to stuff an elephant? I actually have a recipe for stuffed camel of all things, from some middle eastern country. It's bizarre... you stuff the camel with sheep and stuff the sheep with chicken and veggies and blah blah blah... roast in ground for some huge amount of time. Heh, the recipe ends with the line "feeds friendly group of 100" LOL
no subject
Date: 2011-09-21 02:45 pm (UTC)no subject
Date: 2011-09-21 02:45 pm (UTC)no subject
Date: 2011-09-21 03:39 pm (UTC)no subject
Date: 2011-09-21 03:43 pm (UTC)I also have zillions of cookbooks. I hardly ever refer to them anymore. Craig Claiborne's "The New York Times Cookbook" is really almost as quaint now as "Mrs. Beeton's Cookbook".
no subject
Date: 2011-09-21 03:47 pm (UTC)