Friday, July 18, 2008

UC Berkeley Wine Studies II, Fall

|

I’m once again teaching Fundamentals of Wine Studies II: Sensory Evaluation of Wines and their Components for UC Berkeley Extension, and I’d love to see some of you in the class. If you’ve ever wanted to see if I can actually babble about wine for 2 1/2 hours, now’s your chance. It starts on October 9 and continues for six weeks. By the end, you’ll have a great vocabulary for articulating what you taste in the glass, and you’ll be able to communicate your likes and dislikes with confidence. The class is less about regions (though some of that sneaks in) and much more about analysis. You can read my detailed description of the classes in earlier posts: Part 1, Part 2, Part 3, and Part 4.

This semester, given that I live and work in the East Bay, I’ve arranged to teach the class in Berkeley. I hope that means that some of you can take it who couldn’t make it into SF in the past. Let me know if you have any questions, and I hope to see you in class.

Labels:

Sunday, July 13, 2008

Some Recent Food/Wine Books

|

In March, Alder wrote a vinography.com post titled “Food And Wine Pairing Is Just A Big Scam.” The resulting comment thread surprised me: I didn’t think it was a particularly novel revelation that there’s never one and only one perfect wine for a meal. Some of the best wine writers in the industry — Karen MacNeil and Ed Behr to name two — have been arguing this point for years.

I disagree with Alder’s absolute stance about food and wine pairing — I have some basic guidelines that work well — but I don’t disagree that a major industry has formed around convincing people that they can only pick out a wine for dinner with an expert’s help.

How could I? I’ve been sent three food-and-wine-pairing books for review, and there are probably a dozen others out there. That gives me the chance to compare them instead of doing a full post for each.

He Said Beer, She Said Wine, Calagione & Old
Maybe you can’t judge a book by its cover, but its title is fair game. She’s an urbanely dressed sommelier; he’s a “guy’s guy” brewer. Together, they’re a couple that bickers about what to drink with dinner while maintaining outdated gender stereotypes. There’s even a photo of her standing with crossed arms and her back to him looking at the camera. I guess if they ever make a romantic comedy movie out of the book, they’re all set for the poster shot.

The frustrating thing about this book is that the eye-rolling gimmick hides decent information. It’s nice to see a food-pairing book give equal footing to beer — which in many ways is more food-friendly than wine — though it feels a little wrong that many of the recommended beers come from Calagione’s brewery. The two authors present wine and beer as a series of characteristics that expand your ability to find similar drinks: levels of oak in wine, for instance, and levels of hops in beer. The book encourages its readers to make their own judgment, though only after it has pre-biased them to the results. If someone says a wine smells like lemon zest, you’re likely to smell lemon zest on your next sniff. If a book says beer is the better choice for a dish, are you really going to be objective when you try it yourself?

But the information isn’t worth the cutesy dialog. Pick out a book that’s useful and not condescending. You’re an adult, and you deserve to be treated like one.

What To Drink With What You Eat, Dornenburg & Page
In the year and a half since I first reviewed this book, a mild annoyance of mine has become a full-blown rant: If you just tell a reader which wine goes with which food rather than explain why, you’ve abandoned that reader to ignorance. What To Drink is guilty of that sin, but it’s hard to argue with its voluminous lists, culled from the opinions of sommeliers around the country. If nothing else, it has the potential to introduce readers to new wines (and the book is mostly about wine, though there are other drinks in there) and provide brainstorming opportunities for jaded, cynical wine geeks like myself.

But I find it interesting that while I recommend it — even still — I almost never consult it. So why recommend it? I think the bulky lists offer something, even without an explanation as to why the wines work. They offer a wealth of possibilities and a reassurance that, in fact, there isn’t one wine for any food. There are tons. While it never says so, it underlines my basic food and wine premise: Most wines go with most foods. And that’s a lesson in its own right.

Williams-Sonoma Wine & Food, Joshua Wesson
I don’t look to the Williams-Sonoma books for the kind of cookbook I like. The ones I’ve seen are simple collections of recipes; I look for more technique in my tomes. So I listened politely but skeptically at a book launch party as the executive editor of the series told me how good their food and wine book is.

Then she sent me a copy.

The book organizes its sections by style of wine — Crisp Whites and Juicy Reds, for instance — just like the better modern wine lists. Each section describes the flavors and characteristics of the wine style. It then talks about how those traits affect the wine and food pairing. Finally, it gives several recipes that exemplify the kind of dish that suits the wine. Each of those recipes offers guidelines about the New World and Old World wines to seek out. It doesn’t give specific labels. It gives you terms you could use in a wine store: an Alsace Riesling, a Merlot-based Bordeaux. And for each of those recommendations, it offers a reason.

It educates and illustrates. It lets the reader understand what the author was thinking. What more can I ask for in a wine-and-food-pairing book?

Labels:

Saturday, June 21, 2008

Until It Looks Right

|

I was speaking with a friend of mine last week who wanted ideas for a dinner party. She’s in New York now (*sniff*), and she told me what was in season there: She was still seeing lots of springtime produce. I suggested a strawberry-asparagus salad and explained the basic process (blanch 2-inch chunks of asparagus, slice strawberries into wedges, dress with red wine vinaigrette, serve) and then told her I garnished with mint. “How much mint?” she asked. I answered with my normal response to such questions: until it looks right. Get the food to look the way you want, and it will be close to the way you want it to taste.

This insight may be one of the many things my friend Tom taught me. Or we may have arrived there independently. I forget. Certainly, “until it looks right” was a common direction of his.

It’s the rule I use for salads of various kinds and salsa. Probably other dishes as well, but those are the ones where I do it consciously. Come to think of it, I add chocolate chips to cookies until the mix looks right.

Consider my friend’s strawberry-asparagus-mint salad. If you looked at a bite and saw the dark green of minced mint, what would you expect it to taste like? What if you looked at a bite and saw chunks of strawberry and asparagus gilded with little flecks of green?

How you, as a cook, choose the look is up to you, of course.

Tonight I made myself (Melissa is away) a pasta salad with figs, tomatoes, and basil. I added the chopped figs and tomatoes and mixed. I looked in the bowl and saw a sea of creamy yellow pasta with islands of red and purple. I added more figs and tomatoes until there were equals amounts of each color. Then I added minced basil until each bite had 5 or 6 flecks of green, which looked about right. Then I tasted. It needed salt, a little lemon oil, and nothing more: The ingredients were balanced.

Maybe this is obvious: I don’t know. But in my quest to cook from technique and not from a set of instructions, it’s been one of my most valuable guides.

Some other notes on salads that may be helpful as the mercury climbs up the thermometer’s tube. Mix with your hands: You won’t damage the ingredients, and you’ll end up with a better mix. Cut ingredients into similar shapes: Don’t do horizontal slices of strawberries with wands of asparagus. Finally, taste is the final decider: Cooking by look just gets you most of the way there.

Incidentally, I would have loved a figgy Semillon or a crisp rosé with my tomato-fig salad. The Semillon would have complemented the figs in the dish and contributed acidity, while the rosé would have done the same for the tomatoes. But I had a simple Greek red in the refrigerator, so I drank that instead.

Labels:

Friday, June 20, 2008

Learning To Grill

|

I remember the first time I tried to grill. I was just learning to cook well — about 13 years ago — and I decided to make a grilled something-or-other as dinner for a friend. I thought I knew the basics of grilling — it’s called cooking over fire, right? — but the flame on my charcoal kept going out. I kept adding lighter fluid.

When you find yourself battling with your girlfriend about whether the food tastes too much like lighter fluid, you’ve already lost the war.

Since then, I’ve learned more about grilling theory: You want an ambient heat, not roaring flames. But I have almost no grilling practice under my belt. Melissa and I have always lived in apartments, and a potential grill has faced the same problem as our smoker: No outdoor space. Not even a tiny deck because, believe me, I’d have used it.

But now we have a modest backyard, and on Memorial Day weekend we took advantage of my one day off and signed ourselves up for Americana 101 by buying our very own grill. I asked meriko what I should buy, and she told me all the things she loved about her large Weber kettle-style grill with the ashcan below, the vent above, and the liftable wings on the grill itself. Other foodies have confirmed that it’s the one to get.

But many have asked why I didn’t get a gas grill. I have a gas stove. If I wanted to cook over gas I would use that. No, I want the experience of hot charcoal, the taste of fire and smoke, and the variable temperature.

Plus, a gas grill is too easy.

If you’ve never learned to grill, how do you give yourself a crash course? I started with Cook’s Illustrated’s How to Grill. (As an aside, of the magazine’s many attempts at repackaging their recipes, I have always liked their first, the diminutive How Tos, the best.) It gave me pointers on fuel (hardwood charcoal), fire starting (use a chimney), getting the heat up, and setting up a grilling environment (high stack of coals on one side for high heat, one layer on the other side for lower heat). Within half an hour, my grill was fired up.

I am by no means a grilling master — our thin, lean porterhouse steaks came out medium instead of the more flavorful rare — but the grill is a permanent fixture now, and, assuming I’ll have a less hectic schedule this summer, we plan to use it often.

Remember me? I used to blog here. I’ve missed writing for OWF, but I’ve been very busy at work. I wasn’t joking about having one day off Memorial Day weekend. If you haven’t done so yet, visit spore.com and see what I’ve been up to. And while I didn’t work on Creature Creator, you should check out the trial version of this truly fascinating toy. You can find my creatures by looking for MaxisPuzzle in our “Sporepedia”.

Labels:

Saturday, May 24, 2008

Root Beer Floats

|

On Fridays, my company has a TGIF gathering: They bring in beer and food, and we play the latest video games on the HD television nearby. It’s a descendant of the “beer bashes” that technology companies had in the boom period of the mid-90s, company-sponsored thank-yous for the hard work the staff had put in during the week. Those parties ended as funds dried up in the bust cycle of the late 90s and early 2000s, but Maxis has kept a modest version.

At some point in the past, my new team started its own Friday event. One member of the team brings in a pairing of a beverage — usually alcoholic — and food. This week, I volunteered to bring in root beer floats.

Melissa went shopping for ingredients — I haven’t been getting home in time to make it to the store — and I dug the Glace-A-Tron 6000 from its hiding spot in the basement. Thursday morning, I woke up early to make the custard base; Thursday night, I made the ice cream so that it would firm up overnight.

Everyone loved the throwback to their childhoods: digging spoons into the ice cream and then guzzling down the creamy root beer. Next time, I joked, I’ll make the root beer, too.

Tuesday, May 06, 2008

1998 Michele Chiarlo "Cerequio" Barolo

|

I planned the meal for five years.

Actually, it only took me an hour or so. We had just bought a bottle of Barolo, the tannic wine of Italy's Piemonte, at a wine shop in La Morra. We knew precisely when we would drink it: April 25, 2008. Though it ended up being April 26. The wine would be 10 years old by then — just about coming into drinkability &mdash and we’d be celebrating our fifth wedding anniversary.

Barolo is the Piedmont’s greatest wine. Osso buco is one of its greatest dishes. I couldn’t resist pairing them: The wine’s tannins and complex flavors could stand up to the braised veal shanks and the risotto milanese I planned to serve with it.

I conveniently forgot that late April can be scorching hot in the Bay Area. After all, it had rained on our wedding day.

So how appropriate that the weather was, once again, all wrong for the plans we had made. Fortunately, our part of Berkeley cools down quickly with the evening breeze off the Bay: Even if it wasn’t the dead of winter, we could enjoy the tender meat, creamy risotto, and rich sauce.

Any time you hoard a truly special bottle of wine, you fret about how it will be when you open it. And it turns out we had good reason to be nervous. At some point in the bottle’s life — presumably before we tucked it into its temperature-and-humidity-controlled storage unit — the cork had pushed out slightly. The cork was also soaking wet.

That’s not a good sign. It suggests that large amounts of oxygen have wormed their way into the bottle, probably ruining it.

But Barolo is a tannic wine, and tannins act as a preservative. Though we prepared for the worst, the wine had a heady aroma of spicy fruit and a rich flavor. It wasn’t perfect, but it was a lot better than it could have been.

A warm day for osso buco and a special wine that went awry. So what went right about our fifth-anniversary dinner? The only thing that really matters: my date. Before we ate, we clinked glasses, and I said, “To five years I wouldn’t have spent any other way.” Melissa and I have eaten together, drunk together, bought a new house together, traveled together, and more in the last 5 years, and I still say today what I said three years ago: She is the person I always want to see on the other side of the table.

Labels:

Post Slackage

|

I apologize for the slack in posting. I’m working a lot at my new job, which has not one but two looming deadlines. And Maxis has reawakened my videogame love, since the latest games are my office’s water cooler chatter. (In fact, if you’re on XBox Live, I’m oenoscribe.) So bear with me as I adjust to the new routine, and, as always, thanks for reading.

Labels:

Saturday, April 19, 2008

Technique: Chicken Rillettes

|

I often buy a whole chicken for a week’s worth of dinners. The first two meals are easy: something with the legs and then something with the breasts. But what about the wings?

There’s not much meat on them; certainly not enough for a main course. In the past, I’ve picked the meager flesh from the bones and added it to omelettes or soufflés, dishes where you don’t want a big hunk of meat with rich eggs. But for a few recent chickens, I’ve made the wings into rillettes, a spread of shredded meat and fat.

I think I got the idea after making rabbit rillettes from The Zuni Cafe Cookbook. While many books suggest treating rabbit rillettes just like pork rillettes — cook the meat slowly in fat — Rodgers takes a more complicated route that gives the delicate meat a chance to shine: Poach in water with mirepoix and white wine, add a pig’s foot for body, pound in a mortar and pestle, and dribble in fat in tiny amounts.

What had worked so well for rabbit might also work well with chicken, I thought. I modified the recipe — I don’t have pigs’ feet in my freezer on a regular basis, no matter what you think — but the results were still delicious, and the dish has been a recurring favorite.

Except I make them in an ad hoc way. You could argue that Rodgers’ recipe has little in common with my technique, but they share key kinships.

First, salt the wings. Sprinkle a handful of kosher salt onto a plate, press the wings (both sides) into the salt and set them on a dish in the refrigerator for 24 hours or so. The first time I made the dish, I tried to skin the wings: I urge you not to do this; it is time-consuming and ineffective.

The next day, poach the wings in a stick of butter and just enough water to cover them. (If you want to add a little dry white wine or white wine vinegar, please do. If you want to add spices and aromatics, please do.) Cook them at barely a simmer until the meat falls off the bone with even the glancing blow of a fork, about an hour to an hour and a half. Pull the wings from the liquid and let them cool briefly, and remove the liquid from the heat. Using your fingers, strip the bones of the meat and skin and put them into a mortar. Pound the meat with the pestle until it begins to flatten. Now dribble in a tiny bit of the fat from the pot — it will have risen to the top. Pound the meat some more. Dribble in a little more fat, and continue to pound. I probably add two or three teaspoons of fat over five or six doses. You want a spreadable paste of shredded meat, but you also want the flavor front and center: Too much fat will mute it. Season with pepper, smush into a ramekin, cover, and refrigerate. If you won’t use the rillettes that day, you can let the fat continue to cool and then spoon it over the rillettes to seal them in.

Then what? I smear rillettes onto bread or put it into dumplings. Two chicken wings do not yield a lot of rillettes, but two people can get a decent dinner out of them. The other night for a potluck, I smeared a dollop of rillettes and butter onto baguette slices and topped the smear with sliced radishes to make 18 bites of finger food. The rillettes added flavor, while the butter added richness and volume.

Labels:

Saturday, April 12, 2008

San Francisco Chronicle: Marlborough Sauvignon Blanc At A Crossroads

|

When Melissa and I visited wineries in Marlborough, I was struck by the number of winemakers who said something along the lines of “Well, Sauvignon Blanc is kind of boring.” or “Sauvy keeps the accountants happy, I guess.” I was also surprised by the wide array of other grapes that wineries were bottling. Other than the occasional Pinot Noir, we rarely see anything other than Sauvignon Blanc here. It struck me that Marlborough has been so successful with the grape that it’s become difficult to get drinkers to buy anything else.

I wrote about these observations for the lead story in the Chronicle’s Wine section. And while you all may have gotten used to these announcements, this article has a special OWF bonus: Melissa took one of the pictures they used for the piece.

Labels: ,

Friday, April 11, 2008

Food/Wine Pairing Tasting Notes

|

Here is a question I often ponder. If you are going to suggest a wine to go with a particular dish (or vice versa), why would you just write a regular tasting note and not reference the dish? That thought crept into my mind again as I noticed this post on Personal Wine Buyer, whose author will be suggesting wine pairings for Design*Sponge. (And I only single him out because I just read his tasting note; I can’t think of the number of times I’ve seen this.)

Here is his write-up of the wine he chose to go with Matt Armendariz’s Sautéed Beet Greens with Sun-Dried Tomatoes and Pancetta:

Beautiful golden straw in color. Not extremely forward or exotic on the aromatics — a bit subdued on the nose. On the palate, this wine shows beautiful grapefruit and citrus, nice apple with some butter and almonds. Really nice minerality with great weight, balance and acidity with a nice crisp finish. This is a good value at about $18 a bottle — and just a really nice wine. Recommended.
Sounds like a wine I would like. But why, exactly, did he choose it to go with Matt’s dish? It doesn’t matter if you agree with him: Why that wine?

In my wine writing, I try to also be a wine educator. I want people to finish my pieces and think, “Hmm. I learned a little something.” I can and do write adjective-heavy tasting notes, but I don’t kid myself about the number of people who actually read them: very few, I think.

To me, his tasting note and its siblings in the bulk of the wine press are wasted opportunities. The author could have talked about how structure, weight, acidity, and flavor led him down that road. He could have given readers something to think about: a better way to think about wine than as a bag of descriptions. He could have empowered them in the wine shop. What happens when the average reader goes to their local hooch supplier and can’t find the wine? He’s stranded them: They have no way to articulate what they want. Furthermore, he hasn’t given them a language they can use in the future. He has described a wine and failed to give it any context. I, too, have done this in my professional writing. That doesn’t make it right.

Give a man a fish, the saying goes, and feed him for a day. Teach a man to fish, and feed him for a lifetime. As wine writers, we owe it to our readers to teach them to fish.

Labels: