Cupcake Friday Project

A one-woman test kitchen meets nano-bakery

Category: ice cream

Tasty treats from ACHIEVEability’s Food for Thought

Last Saturday, Ray and I attended ACHIEVEability’s Food for Thought 2013. The event was hosted at Urban Outfitter’s AMAZING Philadelphia Naval Yard headquarters, and the night was full of great food, drinks, and charitable giving.

We enjoyed a lot of the dishes served, and I was pleased to see that desserts weren’t neglected. Some of the offerings were:

  • Peach cobbler with bacon ice cream from Desserts by Dana
  • Birch beer vanilla bean ice cream cone and non-dairy coconut chai ice cream cone from Little Baby’s Ice Cream
  • Banana white chocolate walnut pudding from  
  • Opera Cake from Le Bec-Fin
  • French toast bites with mango lime curd, raspberries, ricotta and shortbread cookie pieces, topped with a pineapple-berry-apricot chutney and a white chocolate coconut glaze from Sabrina’s Cafe
  • Gulab Jamun Creme Brulee from Tashan
  • Salted caramel budino from Barbuzzo, Jamonera and Lolita

Of the desserts I tried, I found they fell neatly into 3 categories: outstanding, middle-of-the-road, and overwrought. My favorites of the evening were both ice cream cones from Little Baby’s Ice Cream and Marcie Turney’s salted caramel budino (which I’ve had before at Barbuzzo).

And to finish the night off right, Ray had a wonderful Italian macchiato from Rival Bros mobile coffee truck … hands down some of the best coffee in Philly.

Disclosure: ACHIEVEability gave Ray and me 2 press passes to attend the Food for Thought 2013 event.

Share

How recipe testing made me a better recipe writer


I’m a member of the Food52 online community and threw my hat in the recipe-testing ring for the first time a couple weeks ago. It was for the ice cream community picks, and a lot of the recipes were based off of Jeni Britton Bauer’s ice cream base for home ice cream machines (which she kindly posted on the site). First, I love ice cream; second, I wanted to try a new non-egg custard base; and third, I wanted to do more with the Food52 community–which is sometimes difficult when there are only 24 hours in a day.

I selected a recipe that looked intriguing and wouldn’t require the purchase of a new pantry, and jumped in. The ice cream was a chocolate coffee base with a separate orange caramel to be layered into the finished confection once packed. Easy enough, right? Well, yes and no.

There was a lot of swearing that day in my kitchen. I took a lot of notes, like a good recipe tester, and gritted my teeth every time I wanted to do something differently than the recipe called for (that’s not testing). The process for making an ice cream using Jeni’s Splendid base is a bit complicated, but if you write out the steps clearly, it’s manageable. However, because the Food52er had clumped the instructions into large paragraphs, it became difficult to read. I ended up making a mini flow chart of steps so I could follow along with ease–something that’s important when there are hot liquids and precise timing involved. I also found some of the steps to be vague, meaning I had to fill in the blank. Sure, I’m a fairly experienced cook and baker, but recipe should spell everything out clearly … especially when there’s a chance that a novice cook or baker is taking your recipe for a spin.

However, for all of my swearing and fist shaking, I have to say that testing someone else’s recipe put recipe writing into a clearer perspective for me (I know some of my recipes need a bit of clean-up, as well). In the end, the ice cream turned out rather tasty and I think I can become a better recipe writer based on this experience.

Here are two tips to improve your own recipe writing:

1. Never be vague. Provide a time range (ex., whip for 5-7 minutes until stiff peaks form), especially if the process is something that can go from right to horribly wrong in a matter of seconds. My biggest beef with this is when making caramel. Sure, tell me to let it cook until it’s amber colored, but if you provide me an approximate time range as well, that gives me something else to judge against, and thus lower my chance of errors.

2. Break out your recipe into 1-2 sentence (or action) steps. In the ice cream recipe I tested, 1 paragraph had upward of 11 steps! That’s way too much! Even if your recipe has a variety of components (like cake, filling and frosting), don’t lump all the instructions for one component together. Recipes should be easy to scan … you don’t want someone picking through text trying to find the next step while a pot boils over.

Share
Optimization WordPress Plugins & Solutions by W3 EDGE