Showing posts with label industrial. Show all posts
Showing posts with label industrial. Show all posts

Saturday, November 5, 2011

Local food is elitist? Part II

So I knew I had more to say in response to Mark Bittman's article, "Local Food: No Elitist Plot," which I blogged about a few days ago, but it took a Saturday afternoon at the playground to work through some ideas and thoughts regarding the absurdity of calling local food elitist.

(Here's a total side note: A friend of mine asked today if "eating local" included squirrel. I'd say yes, probably; not much meat on 'em though. Maybe a stew? But I digress....)

So this idea that eating local is trendy or elitist stirred up such an angry ant's nest in my mind. But why? Why did it make me so mad?

Let me step back a little. Throughout our existence as human beings (and probably before that), most food was local. Furthermore, seasons, geography, and weather restricted the availability of ingredients. However, these limitations unleashed human creativity (if for no other reason than to stave off the boredom of eating the same dish for the sixth week in a row because that's all that's left after a long winter or dry season). All across the globe, cooks got imaginative, developing techniques to bring out new flavors in foods, tweaking textures and forms, trying new things they found in their environment--continually innovating, refining, experimenting to make the most of what they had.

Local cuisines and flavor profiles arose around the world based in large part on what foodstuffs were available. And with the Columbian Exchange new ingredients spread throughout the world--peppers bringing their heat to the far east and wheat and apples coming to the new world, redefining what local food was, yet maintaining an essential uniqueness, localness, and authenticity.

Here's the contrast: Industrial food--whether you are talking about fast food restaurants, meals in a box, frozen dinners, snacks, sodas, franchise restaurants of any stripe--promotes sameness. National and international brands of industrial foods value consistency almost above all. As a consumer, the idea is that the soda you find in Waukegan, Illinois, will taste the same as the one you find in Oahu, Hawaii.

So, is consistency bad? Well, no. I am an editor, for pete's sake, I crave consistency. But not in food. In food, it gets boring and generic.

More than boring though, consistency trains the public palate; consistency trains people to expect specific kinds of flavors and textures--most of which are nothing like the tastes and textures of home-cooked food made from seasonal ingredients. It takes away people's freedom to develop their own palates, to make their own judgments about how they think a food tastes. If the standard in taste is a fatty, salty snack with a vaguely chicken-y or cheesy flavor or a sugary, squishy-soft thing with a vaguely chocolate-y flavor, how are beets and turnips and quinoa supposed to hold their own? In other words, if a person were raised with a concept of bread as a ghastly white supersoft substance with a slightly chalky taste, how long would it take for him or her to cease to regard a loaf of home-baked, whole-wheat bread as kind of foreign?

And so millions of industrially trained palates continue to crave the same tastes and textures, with a slight tweak from time to time to keep things "interesting," themselves end up being the product of industrial food.

And it bothers me, because it comes back to this idea that people are incapable of taking care of themselves, of making things for themselves, of making decisions for themselves. We are continually sold the idea that this company can make that easier for you, can take away your concerns about this or that. We are continually trained to lack faith in ourselves. It comes back to this idea that people are just too dumb to take care of themselves. (Michael Ruhlman rails against the idea that Americans are too stupid to cook in this blog post.)

But, hey, maybe it's true. News used to be mostly facts, leaving the work of forming an opinion up to the news consumer. Now people are served prefab opinions. People used to (grow and) cook their own food. Now it's served up in boxes, cans, and freezer bags--all prefab because people can't do it for themselves. Most people used to make their own clothes and furniture--now most people are too scared to even try.

But I don't really believe people are incapable of doing and thinking for themselves. Well, to be completely honest, I don't want to believe they are incapable. I want to believe that ordinary people are capable of making their own meals; adapting to local conditions, flavors, and ingredients; developing their own palates and judgments based on real, natural, whole foods. If that belief is elitist, then I'm an elitist. Then local food is elitist.

But you know it's not. Believing people can do, make, and think for themselves is the antithesis of elitism; what it is is faith in everyperson.

Wednesday, November 2, 2011

Local food is elitist? Part I

I am fan of Mark Bittman. I don't always agree with him, but I do more often than not. His recent post, "Local Food: No Elitist Plot," really pissed me off. Not because I disagree with Bittman, but because of this notion that eating local food in season is in some way elitist and snobby. Really? The method of sourcing food that we've used to get our food for about 250,000 years is elitist? Wow. The fundamental reason for the planet's many and distinctive food cultures is snobby? What a thoroughly ridiculous, absurd idea.

So what's perceived as elitist about it? For one thing, local food is nearly always placed in direct opposition to fast food, junk food, convenience foods of any kind--sort of the local, liberal, environmentally friendly yin to the industrial yang of cheap food. (Don't get me wrong: I know several local farmers, and their political leanings run the gamut.) Fast food is cheap and noncomplex and requires no work to prepare and eat; thus it appeals to many fundamental American values. By providing a lot of food for what seems like little money (here's another Bittman piece about the supposed cheapness of fast food), it wraps itself in a robe of thriftiness, of good old American hard-workingness. By dimming our senses with blasts of salt and sugar, it ensures we are incapable of experiencing the subtler pleasures of real food. And finally, by being so easy to get, it suggests respect for the value of our time. It seems to say, "I understand you don't have time for this fancy food nonsense; here's something that'll get the eating job done so that you can get on with the hard work of your day."

In contrast, local food does not seem cheap, especially if you are used to getting groceries from discount chains. If you typically buy a dozen eggs for 99 cents, $5 for a dozen will sting. However, you pay for that cheap-looking 99 cents in a lot of other ways both financial and, well, moral: taxes that pay for industrial farm subsidies, farmworker abuse, environmental costs, mass food poisoning events, other health costs, and so forth. (I would love to see a study that calculates the real cost of a dozen eggs. If anyone has ever seen one, please let me know.) When you  realize that the farmer at the farmer's market is demanding prices that cover his or her real costs and that you already paid extra for the cheap food at the grocery store, those high prices seem a lot less unreasonable and elitist(1). (Also, you start to ask yourself, who asked my permission to spend my money on appeasing on giant, industrial corn producers?)

Another problem with the seeming cheapness of industrial food is that when you make something seem cheap, people will start to treat it that way. In other words, it loses its value. This may not seem like that big a deal; why would it matter that people think food is cheap? Well, for one thing, cheapening food devalues the very hard labor that people put into growing it (and if you are a meat eater like me, minimizes the life of the animal). And that just kind of sticks in my craw a bit.

But devaluing food also has implications for human culture and health. Sharing food, eating together, teaching one another to cook--all these food-related activities and more comprise some of the most important ways that people create and transmit culture as well as form bonds with one another. When the food you eat loses value, you are less likely to engage in those kinds of behaviors. When you pick up that  super-extra-duper-value meal at the drive-through window and eat it in the car on the way home, you lose opportunities to communicate with other people, to learn something, to teach something, or even to just relax and enjoy your food--to enrich your life. So the food and the eating experience don't satisfy. You end up wanting more (whether food or human interaction is another question). Food loses it specialness; it becomes something to engage in any time, any place. So you eat more. And more. And then the portion sizes seem off if they aren't huge. And the taste seems bland if the food isn't drenched in salt or sugar. And suddenly you find yourself weighing more, struggling with hypertension and/or diabetes, wondering how the heck it happened.

Speaking of wondering what happened, I seem to have gotten off track of my original topic, which was the absurdity of the elitism charge on local food, so I will get back to that in a future blog post. (I've also got some nice recipes for cream of tomato soup and finally made some great red beans and rice.)

(1) Of course, not everyone can afford food from the local farmer's market, but that has a lot to do with the way the current system is set up. If more farm subsidies were shifted from producing mass quantities of cheap commodity grain to local fruit and vegetable farms, it seems fairly certain that local farmers could and would lower their prices. That's more of a political issue, not just a change your personal habits and the market will come kind of issue.

[This was also published (with a prettier picture) at Pick-a-Pepper, a great website devoted to connecting local farmers, food artisans, and producers with local consumers, restaurants, and institutions. Check it out!]

Friday, April 8, 2011

So what am I doing with this blog anyway?

For weeks, perhaps months, I have been planning to start this blog about sourcing, making, and eating food, but I have procrastinated. I kept trying to decide what blog service to use and what to call it and what is it going to be about and do I have a point of view that's fresh.I hesitated, hemmed, hawed. A few nights ago, I was trying to sleep and writing my First Blog Post in my head, and I asked myself: What's taking so long? Why haven't you done this yet? The service and the name aren't that big a deal, are they? Then a tiny voice piped up from the back of the room (because I view my mind as a vast conference room with lots of people there to listen to what I have to say--no, I don't really, but I thought it was kind of fun to imagine anyway), so, where was I? Oh yeah, little voice, back of room, said "But what if it isn't any good?" Yeah, you nailed it, tiny voice: I was scared. I am scared. What if this isn't any good? What if no one wants to read what I have to say about food? And what is it exactly that I want to say about food? Food is good. Enjoyed with friends, it's wonderful. A lot of people are out there talking about food. What do I have to bring to the table?

Well, these are some reasons I want to write about food:

About a year ago in January, my husband Mike and I borrowed an audiobook version of Michael Pollan's In Defense of Food. When we were done with that, we went on to Omnivore's Dilemma, which more than any other book made us want to opt out of the industrial food chain and so we set out to do that. It wasn't easy, and it still isn't. We have changed our behaviors with regard to getting and making food, and we have changed the way that we think about food, but the practices of avoiding food shipped from halfway across the world (especially in winter), of making your own, of trying to eat mostly local and sustainably raised food are hard. But to us they are incredibly meaningful and so we keep at it. In fact, trying to eat the way that we want to eat is so meaningful to us that I hope to be able to share some of what we have learned and hopefully get others to opt out of industrial food too. Because I also think that the more people opt out of it, the easier getting local, sustainable, nonindustrial, and seasonable food will become as local food distribution becomes more efficient. So there's a selfish aspect to it: I want you to do what I do so that it gets easier for everyone.

Then, there is the love and passion aspect to it, and that encompasses so many different components that I easily get lost. There's the quality of the food that I get from people I directly support. There's the sense of belonging to a community, a place, where I have a stake in the soil, in the air and water, and in the people who live near me. One of the most potent ways I know to connect to the world is to eat. Food is a distillation of sun, soil, place, air. In his book,  NOMA: Time and Place in Nordic Cuisine and in his food, chef Rene Redzepi talks about this connection between what we eat and where we are as a way to create sense memories, and in a sense to create an ephemeral art. I cannot create the kind of art that Rene creates, but to take some of that spirit and infuse it into the quotidien is something I want to strive for. I think that the practice of thinking and writing about food can help me to make daily life an art form, which makes my life more meaningful and more beautiful and hopefully does the same for my family.

Finally (at least for this post--there are more reasons and I will develop them as we go along), I want to teach what I know about cooking by passing along my successes and sharing my failures. Hopefully in the process I can keep getting better and learning more.

So this blog will be a mish-mash of recipes and tips, of food politics, of raving about the good (and perhaps the bad), of sharing stuff I learn, of creating art. Hopefully it will entertain, inform, inspire--I mean, why else would anyone write?

And to get started with the recipes, here's my recipe for roast chicken (which I planned to have for dinner tonight, but a family thing suddenly came up):

1 whole chicken (I get mine from Haskins Family Farm, which I will rave about at another time)
salt, white pepper
2 lemons (unfortunately usually not local, but I do have a lemon tree now!), one juiced, the other cut in half
herbs to taste or as available
unsalted butter

  1. Preheat the oven to 425 degrees
  2. Butter a baking dish (you want it to be deep so that it can hold some water)
  3. Rinse the chicken with cold water, inside and out
  4. Pat the chicken dry with paper towels
  5. Grab about a tablespoon of salt and rub the inside and outside of the chicken (sometimes you will need more--don't be afraid to salt a lot!)
  6. Rub the inside and outside of the chicken with white pepper
  7. Stuff the lemon halves inside the chicken along with any herbs that you have available (if you don't have any, you can skip this)
  8. Place the chicken in the baking dish, fill the bottom wiht about an inch of water
  9. Put it in the over for 30 minutes
  10. After 30 minutes, pull it out, turn the chicken over in the dish, and pour lemon juice all over it
  11. Back in the oven, 20 minutes
  12. Pull it out, turn it over, and rub the chicken with 1 tablespoon of butter
  13. Back in the oven, 20 minutes
  14. Out of the oven, pour pan drippings over the chicken, flip it over, in again, 15 minutes (you will keep doing this last step for 2-3 more times depending on the size of the chicken). I usually check doneness by poking the joint between the leg and the body to see if the juices that run out are clear. Others prefer a thermometer, which should read about 165 degrees in the thickest part of the thigh.
  15. When it is done, remove the chicken from the dripping and let it stand and rest on a platter for about 10 minutes.
In the meantime, you can make gravy with the drippings. Use a fat separator and let the drippings divide into two layers. Grab about 2-3 tablespoons of the fat and put it into a pan. Add 2-3 tablespoons of flour to the fat and cook for a few minutes (don't let it burn). Then whisking fast, add the drippings (minus fat) to the fat and flour in the pan. It will thicken quickly. If it gets too thick, you can always add some milk, cream, or stock to thin it. Salt and pepper to taste (mine is usually pretty salty, so I definitely check the salt before adding any).

I usually serve roast chicken with roasted root vegetables (whatever is in season or I have around the house) and some kind of salad. Again, it really depends on what's available and looks good at the farmer's market.