About

I was terrified of cooking. Period.

Not just a little nervous — actually afraid. My mother was a fabulous cook, and I came from a family deep in the hospitality business with famous restaurants and thriving ventures. Everyone around me knew their way around a kitchen. Everyone except me.

When I got my first apartment in my twenties, my mother was concerned (rightfully so). Her solution was to give me two recipes that I cringe thinking about now. One was doctored-up jarred marinara with ground beef and garlic. The other was chicken breasts slathered in Dijon mustard and fried in a pan. She also taught me how to pot a chicken for soup. That was the full extent of my repertoire.

Meanwhile, I was working as an event planner for high-end VIP executive meetings. I was traveling across the country, going to fancy restaurants, eating refined meals prepared by actual chefs, experiencing food at a level most people only read about. This was the era when Wolfgang Puck and other celebrity chefs were just coming into the spotlight. I was tasting things I’d never imagined.

And then I’d go home to my Dijon chicken.

The frustration built slowly. I had tasted what was possible in food, and I wanted to create it. I wanted those flavors, that care, that intentionality — in my own kitchen, for myself.

The real turning point came on a trip to Morocco in 1996.

Everything changed. The spices, the layering of flavors, the techniques, the way food was approached — it was nothing like what I could access in America at that time. International food wasn’t really part of the American palate yet. You couldn’t just walk into a grocery store and find what I’d tasted in Morocco. I came home frustrated and determined.

I started hunting for cookbooks. I started trying to recreate those Moroccan dishes. And then something magical happened: I discovered cooking as stress relief.

My friends joked that I was “cooking on four burners” — on weekends, I’d use the kitchen as my laboratory and my therapy, making three or four recipes at the same time. My refrigerator and freezer became a carefully curated collection of dishes. As an event planner traveling across the country week after week, working late nights and long trips, I came home to something beautiful waiting for me. Restaurant-worthy food. Food that made me feel cared for, even if I was the one who’d made it.

It wasn’t just about having leftovers. It was about knowing that no matter how late the night had been or how long the travel, I had something good waiting for me. Something that tasted like I’d worked harder than I actually had.

That’s when I realized: cooking wasn’t just about feeding myself. It was about taking care of myself.

But something shifted during those kitchen experiments. The fear didn’t disappear overnight, but it became less important than the curiosity. I wanted to understand why certain spices worked together. I wanted to know what would happen if I adjusted something. I started to see recipes not as commands I had to follow perfectly, but as invitations to learn.

And then September 2001 happened.

I lost my job. Suddenly, I wasn’t going to fancy restaurants anymore. I wasn’t traveling across the country. I was home. I was on a limited budget. And I was craving those refined, delicious foods I could no longer afford to eat out.

That’s when everything crystallized. I couldn’t go out to eat, so I had to figure out how to recreate those flavors at home on a shoestring budget. No fancy ingredients. No expensive restaurants. Just me, my limited paycheck, and the hunger for food that made me feel something.

Around the same time, I discovered food writing as a genre — a whole new world of it was emerging in the early 2000s. Ruth Reichl, Anthony Bourdain, writers exploring the stories and emotions behind recipes and food traditions. I became absorbed in it. I realized that food wasn’t just about sustenance or even flavor — it was about memory, culture, emotion, connection.

I started reading recipes differently. Not as instructions to follow robotically, but as stories to understand. And something strange happened: I could taste them in my head before I ever made them. I’d read a recipe and immediately know if it would sing or fall flat. I could sense the balance of flavors, anticipate what would happen when ingredients met heat.

It wasn’t magic — it was years of tasting refined food, combined with an obsessive study of recipes and the reasoning behind them. I became what I’d describe as a fantastic recipe reader rather than a naturally gifted cook. That skill became my superpower.

I started curating recipes obsessively — not the ones that looked fancy or Instagram-worthy, but the ones that promised real impact. The ones where the first bite would make you stop and say “wow.” The ones that would make you feel like you’d worked much harder than you actually had. Budget-friendly recipes that delivered sophistication and flavor without pretension.

I was cooking for myself out of necessity, but I was learning something much larger: that the best food doesn’t have to be complicated or expensive. It just has to be intentional. It has to taste like someone cared.

I’m telling you this because if you’re scared of cooking, I get it. Truly. I’ve been exactly where you are. And I want you to know that the way forward isn’t about becoming some accomplished chef. It’s about learning to read recipes like a story. It’s about finding flavors that call to you. It’s about knowing that someone else has already tested that recipe and can tell you if it’s worth your time and money.

That’s why Fork in the Road Test exists. I test recipes so you don’t have to wonder. I read them the way I’ve learned to read them — for flavor, for impact, for that “wow” moment. I tell you what actually happened. And I’m here as a friend who remembers being terrified of her own kitchen, helping you find your way through.

You’ve got this. I promise.