You have read a hundred of these
You’re right to be sceptical. Most recipe sites promise ‘foolproof’ dishes, then hide the fact that their ‘test kitchen’ is a single person who’s never cooked before—or that the photos were taken after three retakes with a different pan.
We’ve all been there: a dish that sounded simple turns into a lesson in frustration, and the only thing ‘foolproof’ about it is how quickly it ends up in the bin.
But here’s the difference: we don’t test recipes. We *fail* them. Then we fail them again. The caramelized crust in the tagline?
That’s the second secret—because the first one is that every recipe here has been burned, overcooked, or left to sit too long on the counter before we got it right. The only way to know if a dish works is to break it until it does.
And no, we’re not just talking about ‘adjust seasoning to taste.’ We mean measuring the exact time it takes for a sauce to thicken in your oven, not someone else’s. We mean testing the same recipe in three different pans to see which one actually browns the meat.
We mean knowing when to throw out a batch because the technique is wrong, not just because you messed up.
Because it never is—until you’ve seen a recipe that actually works the first time.
Anyone can write that they test things
Here’s what ‘tested’ looks like in practice: a single recipe might take 12 attempts before we stop tweaking. That’s not exaggeration—it’s the average for anything with a crust, a sauce, or a technique that relies on timing.
The first five tries are usually thrown out: the crust cracks, the sauce splits, the meat stays tough. The next three are adjusted for oven quirks, pan material, and humidity levels (yes, that matters). Only after the seventh or eighth attempt do we start calling it ‘right.’
And that’s just the cooking. Every recipe is also tested for clarity: we give the steps to someone who’s never held a knife, then watch them follow it. If they pause for more than 10 seconds on any step, we rewrite it.
If they ask ‘why?’ more than twice, we add a note. The goal isn’t just a dish that works—it’s one that *anyone* can make without second-guessing.
We also track the ‘failure modes’: what goes wrong if you skip a step, use the wrong fat, or forget to rest the meat.
Those mistakes aren’t hidden in a footnote—they’re in bold at the start of the recipe, because the point isn’t to make you feel dumb for not knowing. It’s to make sure you *do* know before you start.
We don’t just test once—we test until the numbers stop lying.
About the author
Angelo Abernathy is the one who still flinches when garlic bread comes out of the oven—because that’s how this site started.
The rules I work by
- 1No shortcuts for flavor
Every spice, herb, and acid is measured by weight, never volume. A ‘pinch of salt’ is 0.2 grams—because if you guess, the dish guesses back. This costs time, but it saves you from starting over.
- 2The pan matters more than the recipe
A stainless steel skillet sears differently than cast iron. We test every dish in three pans before picking the one that works. It’s why some recipes say ‘use a heavy pot’—not because we’re picky, but because the alternative ruins the texture.
- 3If it doesn’t work the first time, it’s not ‘you’
The first three attempts of any recipe are for us, not you. We burn, over-salt, and undercook on purpose—to find where the process breaks. That’s how we know when to warn you, not just when to tell you what to do.
- 4Photos aren’t the goal
They’re a last resort. If a dish looks ‘perfect’ in the picture but falls apart in your kitchen, we’ll replace the photo before we replace the recipe. That’s why some images look like they’re from a home kitchen—not because we’re lazy, but because the real test is what happens after you close the tab.
- 5Silence is a failure
If a recipe doesn’t mention resting time, don’t assume you know it. If it doesn’t explain why the acid is added last, don’t skip it. We’d rather you ask ‘why?’ here than ruin a dish because we assumed you’d figure it out.
Breaking a rule isn’t a mistake—it’s how we find the real one. The time we thought ‘resting meat is overrated’ led to a rack of lamb that fell apart before it hit the plate.
The time we skipped the ‘bloom the spices’ step gave us a curry that tasted like dirt. Those failures aren’t in the archives; they’re why the rules exist in the first place.
This will not be right for everyone
Close this page if you want recipes that sound fancier than they are, or if you’d rather scroll past the ‘why’ to get to the ‘do.’ This isn’t a place for ‘5-ingredient meals’ or ‘dishes you can make while watching TV’—it’s for people who care enough about food to notice when a recipe doesn’t add up, and who aren’t afraid to spend 20 minutes on a technique if it makes the difference between ‘good’ and ‘unforgettable.’
If you’d rather have a site that tells you what to do without explaining why, or one that treats cooking like a series of unconnected steps, there are plenty of others.
But if you’ve ever walked away from a recipe thinking ‘I’ll do better next time’—only to realize the problem wasn’t you—this is the place where ‘next time’ starts working.
You could just be told what you want to hear
We could say we’ve been featured in magazines, or that our methods are ‘revolutionary.’ We could tell you this is the ‘only’ site you’ll ever need. But the only thing worse than a recipe that lies is one that pretends to be honest while hiding the part where it failed.
Worth telling us
- The exact temperature your oven runs at (hotter or colder than it says), and how it affects timing.
- What you’ve tried that didn’t work—and why you think the recipe (not you) let you down.
- A dish you’ve made 10 times but still can’t get right, even when you follow the steps.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.