A couple months back, I found some recipes in a favorite cookbook calling for an ingredient I didn't have. The ingredient, asafetida, is a funky powder that comes from a plant and a fairly common ingredient in Indian cooking. By the time I found some, though, I forgot which recipe it was in, and I spent an hour before bed rifling through that same cookbook to find the recipes again—not unpleasant, but not a particularly efficient use of my time.
In that hour, though, I remembered a website that I'd signed up for a few years ago, then failed to use. The site, Eat Your Books, is niche, but if you cook a lot and own a bunch of cookbooks, it's excellent. As a quick gauge of utility, imagine stacking all of your cookbooks in a pile on the floor. If that stack comes up to your waist, Eat Your Books will likely be very helpful.
To begin, you tell it all of the cookbooks you own—the company's database has indexed almost 10,000 of them with 1.5 million recipes—then you search for the recipe you want to cook, or ingredients you want to use. The results page gives you recipes from the books you own, usually with the page number. From there, narrow your choices, pick your winner, pull the book from the shelf and tuck it into your cookbook holder. When I plugged in "asafetida," it not only found the recipes I was looking for, but also 21 other recipes in two of my other books.
I signed up for a subscription. A premium membership is $3 a month, or $30 per year. (You can use the website for free, but you can only keep track of five cookbooks unless you pay.) Sitting down one evening in front of my shelves, I plugged in my books and learned I own 68 cookbooks with 14,447 recipes. There were a couple books that it didn't recognize, but those were on the obscure side.
