While clearing bookself space for several new cookbooks that arrived in the mail this week, I began leafing through many of the books, wondering why I own so many cookbooks. The stuffed shelves overflow with hardbounds and soft covers, spiral- and plastic-bound books. Plus, I have a collection of cooking magazines and single pages ripped from other periodicals, all boasting delicious recipes.
If you were a guest in my home, you may wonder how often I use each of these treasures. How often does each get pulled from the shelf and pages flipped through in search of a delectable recipe?
If you know me well, you know I enjoy cooking. But while I flip through each book, I realize I seldom use a cookbook to cook. No, if I need to whip up a fancy dessert or a quick Italian dish, I just know how it goes together. I really don't need a recipe to follow.
Last month, I shared a blog post about the unwritten stories told through recipes. It's true. Many recipes have a story behind them, a back story that blends to create a combination of narrative and culinary roots.
And I got to thinking: how do I read a cookbook? Do I glance at the photos? Read each recipe in detail?
I read a cookbook like any other book. I read it cover to cover. In the introduction, I discover what motivated the author/cook to assemble this collection. A lot of times I learn new information about a specific technique or why certain ingredients are important. And I definitely learn more about the author.
I peruse each recipe and the step-by-step instructions. If a page includes narrative, I savor it. And of course, I pour over each picture, gleaning details about presentation and photography.
You can learn a lot by reading a cookbook. The writing requires precision and attention to detail. A sense of place develops through most, and readers generally feel a sense of connection with the cook/author.
It's unique, but at the same time, the elements of writing are so similar to other genres. Cookbook and fiction writers can learn from one another. Perhaps the most important lesson is that writers don't always need to follow a recipe.
How do you read a cookbook?
by LuAnn Schindler Read more of LuAnn's work at her website.
Read More »
If you were a guest in my home, you may wonder how often I use each of these treasures. How often does each get pulled from the shelf and pages flipped through in search of a delectable recipe?
If you know me well, you know I enjoy cooking. But while I flip through each book, I realize I seldom use a cookbook to cook. No, if I need to whip up a fancy dessert or a quick Italian dish, I just know how it goes together. I really don't need a recipe to follow.
Last month, I shared a blog post about the unwritten stories told through recipes. It's true. Many recipes have a story behind them, a back story that blends to create a combination of narrative and culinary roots.
And I got to thinking: how do I read a cookbook? Do I glance at the photos? Read each recipe in detail?
I read a cookbook like any other book. I read it cover to cover. In the introduction, I discover what motivated the author/cook to assemble this collection. A lot of times I learn new information about a specific technique or why certain ingredients are important. And I definitely learn more about the author.
I peruse each recipe and the step-by-step instructions. If a page includes narrative, I savor it. And of course, I pour over each picture, gleaning details about presentation and photography.
You can learn a lot by reading a cookbook. The writing requires precision and attention to detail. A sense of place develops through most, and readers generally feel a sense of connection with the cook/author.
It's unique, but at the same time, the elements of writing are so similar to other genres. Cookbook and fiction writers can learn from one another. Perhaps the most important lesson is that writers don't always need to follow a recipe.
How do you read a cookbook?
by LuAnn Schindler Read more of LuAnn's work at her website.
