About Soup Recipes Kettle

What changed, and what it changed for you

When *Soup Recipes Kettle* started, it was a scrapbook of recipes I’d collected—some from my grandmother’s yellowed notebooks, others from cookbooks I’d dog-eared. The instructions were copied as written, the measurements assumed perfect tools, and the photos looked nothing like what actually happened in a home kitchen.

If a recipe failed, it wasn’t the instructions’ fault; it was *your* fault for not measuring carefully enough or not owning the right pan.

Now, every recipe is tested in the same conditions we expect readers to use: a standard oven that runs hot or cold, a kitchen where the scale might be off by a few grams, and tools that aren’t chef-grade.

We adjust the timings, rewrite the steps for clarity, and photograph the dish in the same space where it was made—no staged backdrops, no professional lighting. The goal isn’t to make cooking feel like a performance; it’s to make it work the first time.

The one that took years

The biggest mistake we made was assuming that if a recipe worked for me, it would work for everyone.

For years, the site treated cooking as a science where the variables didn’t matter—until readers started sending messages like *‘Your ‘easy’ pie crust cracks every time’* or *‘The risotto turns to glue in my apartment oven.’* We’d reply with vague advice (*‘Check your humidity’* or *‘Use a heavier pan’*), but it wasn’t fixing the problem.

It was just shifting the blame.

The turning point came when I realized we were testing recipes in a kitchen that was too controlled. The oven ran perfectly, the scales were calibrated, and the pots were the exact size the recipe assumed. But most people don’t cook in a lab.

They use hand-me-down pans, ovens that run 25°F hotter than they say, and measuring cups that lose a tablespoon somewhere between the cabinet and the counter. So we started testing in *those* conditions—deliberately making things go wrong to see how to fix them.

It cost us time. Testing a single recipe now takes three days instead of one: a full cook for me, a second cook by someone who’s never made the dish, and then rewriting the steps based on where it fell apart.

We’ve ruined more pans than we’d like to admit, and the photo shoots are now twice as long because we’re not just documenting the final dish—we’re showing the messy middle.

But the alternative was worse: a site that only worked if you had a perfect kitchen, which is about as useful as a recipe that assumes you own a mandoline.

Meet the author

I grew up in a kitchen where the rules were more like suggestions. My grandmother measured flour by the handful, salt by taste, and time by how long it took to hum *La Vie en Rose* twice. If a dish failed, it wasn’t a disaster—it was just the next experiment.

But when I tried to write that instinct down, it came out as a list of impossible assumptions: *‘Use a heavy Dutch oven’* (I didn’t have one), *‘Simmer for exactly 40 minutes’* (my oven didn’t know what 40 minutes were).

I’d write a recipe, test it once, and call it done—only to get emails from readers who’d followed the steps exactly and still ended up with something inedible.

The worst moment came with a recipe for a family-style lasagna. I’d tested it three times, all in my grandmother’s kitchen, where the oven never lied and the pasta sheets were homemade.

When I posted it, the comments were a litany of failures: *‘Mine burned on the bottom,’ ‘The cheese didn’t melt,’ ‘It stuck to the pan.’* I’d assumed the problem was the readers. It was the recipe.

What changed: I stopped writing for the kitchen I wished I had and started writing for the one most people actually use.

Now, I’m here to build recipes that work in the kitchen you’ve got—not the one you’ll buy someday.

Whether it’s adjusting a sauce for a pot that’s not deep enough or rewriting a baking time for an oven that runs hot, the goal is the same: a dish that delivers on its promise, no matter what tools you’ve got. *Soup Recipes Kettle* isn’t about perfection.

It’s about the meals that actually happen.

What did not change

From the start, this site has been built on two things that haven’t wavered: the belief that good cooking should be approachable, and the refusal to treat mistakes as failures.

The first recipes I ever wrote were for dishes my grandmother made by feel—no exact measurements, no step-by-step instructions, just *‘until it looks right.’* That instinct never left, even as the site grew more precise.

The difference now is that we’ve translated *‘looks right’* into terms anyone can use, without assuming you’ve got a chef’s eye or a perfect kitchen.

The other thing that stayed the same is the focus on stories, not just steps. A recipe is more than a list of ingredients; it’s the reason you’re making it in the first place.

Whether it’s the way a certain spice reminds you of a summer in Sicily or the way a dish brings a group of people to the table, that’s what we’ve always tried to capture.

The methods have gotten sharper, but the heart of the site—the idea that every meal has a tale behind it—hasn’t.

What is still being fixed

Right now, we’re working on two things: making the site faster to load (because no one wants to wait for a recipe to appear) and adding more visual guides for techniques that trip people up—like how to properly fold dumpling wrappers or tell when a stock is done reducing.

Neither is glamorous, but both matter. The first makes the site usable on a slow connection; the second cuts down on the messages that start with *‘I followed the steps, but…’*

If there’s something you’d add to make *Soup Recipes Kettle* work better for you, the contact page is the place to say it.