Why this site exists
You’re reading a recipe that claims to be simple, but the steps assume you already know which pan to use, how long to rest the dough, or why the sauce tastes flat. The photos look nothing like what you end up with.
The comments are full of people saying ‘I added X’ or ‘This didn’t work unless…’—as if the recipe was just a starting point for guessing.
This site exists to cut through that. Every recipe here is tested until it works—not once, but enough times that the mistakes become predictable. No vague measurements, no ‘taste as you go,’ no steps that require a degree in culinary arts.
Just the version that finally *did* work, with the fixes already baked in.
Who writes this site
Marcus Calderon runs the kitchen and the site.
How many times is a recipe tested before it’s posted?
At least twice—once to see if it works, and once to see if the instructions make sense. If it still fails, it gets rewritten. If the instructions are confusing, they get simplified. No recipe is posted until it’s been made by someone who isn’t me.
What’s the most common mistake you make in the kitchen?
Overcomplicating things. I’ll add an extra spice or a new technique just to see if it works, then have to strip it back down to the basics. The best recipes are the ones that don’t need fixing.
Why isn’t there a recipe for X?
Either I haven’t figured it out yet, or it’s something I actively avoid because it’s a disaster. If it’s not here, it’s either not worth the effort or I’m still working on it.
The first recipe I ever wrote down was for scrambled eggs, and I still keep the notebook where I scribbled it. The margins are full of corrections—‘less heat,’ ‘stir faster,’ ‘don’t walk away.’ That notebook is somewhere in a box, but the habit isn’t.
How a recipe is built
A recipe starts with a question: *Why does this work?* Not ‘How do I make it?’, but ‘What’s the rule here?’ The first version is always a mess—too salty, too long, or just wrong. The second version is where the real work begins.
The first version
The first time, the goal is to get it *close*. That means burning something, over-simmering a sauce, or realising halfway that the instructions assumed you had a specific tool. Notes are scribbled in the margins: ‘Add the garlic at the end,’ ‘Use a heavier pan,’ ‘This needs twice the butter.’
If it doesn’t work at all, it goes back to the drawing board. If it’s *almost* right, that’s where the second version starts.
The fixes
The second version is about the mistakes you can’t see until you’ve done it wrong once. That’s when you notice the sauce separates if you don’t temper the eggs, or the crust cracks because the oven wasn’t hot enough.
The third version is where the recipe becomes reliable—not perfect, but *repeatable*.
After that, it’s tested by someone who isn’t me. If they get stuck, the instructions are rewritten. If they burn it, the method is adjusted. If they don’t understand a step, it’s simplified.
What we will not do
This site won’t post a recipe until it’s been made more than once, adjusted for real kitchens, and confirmed by someone who isn’t the author. No ‘as seen on TV’ dishes, no ‘5-minute’ hacks that require a blender you don’t own, and no steps that assume you’re a professional.
Things you will never find here
- Recipes that haven’t been tested more than once.
- Ingredients you can’t find at a normal grocery store.
- Steps that require a degree in culinary arts.
- Photos that don’t match the final dish.
Where to start
If you’re new, start with the ‘Essentials’ section—those are the dishes that teach the rules before you get to the exceptions. If you’re looking for something specific, use the search. If you can’t find it, it might not exist yet.
Say hello
I like hearing about the dishes you’ve made, the ones that failed, and the tweaks you had to make to get them right. The contact page is where to send those stories—or just to ask why a recipe doesn’t have something you expected.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Salads.