
You have read a hundred of these
You’re right to be sceptical. Most recipe sites either regurgitate old instructions or pretend every kitchen is identical to their own.
We’ve seen the ‘foolproof’ methods that fail when the humidity changes, the ‘easy’ recipes that assume you own a sous-vide machine, and the ‘classic’ dishes that taste like they were written by someone who’s never actually cooked one.
This isn’t about flipping a script. It’s about admitting what we know: recipes don’t work unless they account for the real world.
The oven that runs 25°F hotter than it says, the cast-iron skillet that warps if you don’t preheat it right, the moment you realise you’re out of salt halfway through seasoning. We don’t ignore those things—we build around them.
If you’re here because you’ve burned a dish that *should* have been simple, or because you’ve spent an hour adjusting a recipe that *should* have worked as written, you’re in the right place. The rest? They’ll tell you what you *want* to hear. We tell you what actually happens.
That’s what every ‘About’ page says—and then it’s not.
Anyone can write that they test things

Every recipe here is made at least three times, with deliberate mistakes in between: wrong temperatures, skipped steps, substituted ingredients. The first version of the *Duck Confit* was ruined when the fat didn’t render enough—so we tried it again, this time rendering the fat separately first.
The *Neapolitan Pizza Dough* failed twice before we realised the flour needed to rest overnight, even in summer.
We don’t just test once in ideal conditions. The *Chicken Cacciatore* was simmered on a gas stove, an electric coil, and a camp stove to account for heat differences. The *Beef Bourguignon* was made in a Dutch oven, a heavy pot, and a skillet to see how the sauce behaved.
If a recipe doesn’t work in a rental apartment with a finicky oven, it doesn’t stay on the site.
And yes, we’ve thrown out pans. The first batch of *Cast Iron Cornbread* cracked the pan so badly we had to buy a new one—and now every recipe notes whether it’s ‘pan-friendly’ or not. No shortcuts. No excuses.
We test until something breaks—or until we run out of time, pans, or patience.
About the author

Meet Dolores Ruggiero, the founder and editor of Potato Recipes Pan, who still cooks with her father’s cast-iron skillet—now holding everything from stir-fries to holiday roasts.
The rules i work by
- 1No recipe survives first contact
Every dish is rewritten after the first attempt, even if it ‘works.’ The question isn’t whether it’s edible—it’s whether it’s *better* than what you’d make yourself. That’s cost me 12 failed batches of risotto, but it’s why the ones that stay taste like home.
- 2Measurements matter, but not like that
Grams over cups, yes—but only if the ingredient behaves the same way in your kitchen. We test with both scales and volume measures, and note when ‘1 cup flour’ actually means ‘120g bread flour’ or ‘110g all-purpose.’ The margin for error is smaller than you think.
- 3Time is the real ingredient
A dish can’t be rushed, even if the instructions say ‘30 minutes.’ The *Osso Buco* takes 3 hours because the bones need to break down—that’s not flexible. But the *Tomato Sauce* can simmer for 2 or 4 hours, as long as you check it. Some things are non-negotiable; others are a choice.
- 4If it’s not memorable, scrap it
A recipe that blends into the background doesn’t belong here. The *Smoked Eggplant* isn’t just ‘good’—it’s the kind of dish that makes your neighbours ask for seconds. If it doesn’t leave a mark, it’s not worth keeping, even if the technique is sound.
- 5The kitchen is a story, not a lab
We don’t just list ingredients and steps. We explain *why* the smoke should curl when you sear the steak, or how the dough’s windowpane test tells you it’s ready. The goal isn’t a perfect dish—it’s a dish that feels like *yours*.
Breaking the rules happens. The *Pasta alla Norma* failed when the eggplant turned mushy because we forgot to salt it—so now every recipe includes a ‘prep note’ for that exact mistake. The *Beef Short Ribs* nearly overcooked because the oven thermometer was wrong, so we added a calibration step.
Every failure becomes a lesson, not just for the reader, but for the next version of the recipe.
This will not be right for everyone

Close this page if you’re looking for ‘5-Ingredient Meals’ or ‘Dinner in 15 Minutes.’ We don’t do quick fixes, and we don’t pretend that good food is fast. If you want recipes that treat cooking like assembly-line work, this isn’t the place.
If you’d rather scroll past photos of charred edges and smoky aromas, look elsewhere.
This site is for people who’ve burned a dish and still want to cook it again. For those who’ve followed a recipe exactly and ended up with something that didn’t taste like the photo.
For cooks who know the difference between a meal and a memory—and who refuse to settle for anything less. If that’s not you, that’s fine. But don’t blame us for expecting more.
You could just be told what you want to hear
We could say every recipe here is ‘foolproof’ or that our methods are ‘revolutionary.’ But we’d be lying—and you’d know it the first time you tried a dish that didn’t turn out.
Instead, we tell you when a recipe demands patience, when a substitution ruins the texture, and when the only way to get it right is to start over.
Worth telling us
- The oven’s quirks—why your ‘375°F’ setting might as well be 400°F, and how to adjust without a thermometer.
- The ingredients you *can’t* skip, even if the recipe says they’re optional (spoiler: salt is always one of them).
- The moments when you should walk away, even if the timer says ‘done’—like when the risotto looks dry but needs five more minutes.
If there’s something we’re missing—or something you’d rather we admitted upfront—you’re welcome to tell us on the contact page.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.