Why this site exists
You’re standing in your kitchen with a recipe, a half-empty pantry, and no idea whether the result will taste like something or just cost you an extra trip to the shop.
The instructions are either too vague or too technical, and the photos make it look like the cook used a different planet’s ingredients.
This site exists to cut out the guesswork. Every recipe here is tested until it works—not just once, but enough times to know what goes wrong when you’re tired or distracted. Ingredients are listed in the order they’re used, with notes on what to swap if you’re missing something.
And the photos? Those are taken after the third attempt, not the first.
Who writes this site
Gordon Halloran runs it.
Do you test every recipe multiple times?
Yes. Sometimes three times. Once to see if it works, once to see if it’s still edible after sitting in the fridge, and once because I forgot to write down the fix for the first batch.
What do you get wrong?
Everything, at first. Salt instead of sugar. Overlooking the oven’s hot spot. Assuming ‘brown’ means ‘burned.’ The notes are where those mistakes go.
Why isn’t [that dish/technique] here?
Either I haven’t figured it out yet, or it’s something I actively avoid—like soufflés, which collapse faster than my patience. If it’s missing, it’s either too hard or too boring.
The kitchen table is where most of the real work happens—not the stove. That’s where the recipes get rewritten after the third try, the photos are taken in natural light (because flash lies), and the pantry gets raided for ‘emergency’ swaps.
How a recipe is built
It starts with a memory: a meal that stuck, a flavor that haunted, or a disaster that taught. Then it’s torn apart—ingredients, timing, temperature—until the parts that matter are left.
The first draft
The recipe is written exactly as it’s done: no fancy steps, no assumed knowledge. If you’ve ever wondered why a dish needs to rest or why folding batter too fast makes it dense, that’s here.
Numbers are real. ‘350°F’ isn’t a suggestion. ‘10 minutes’ means you’re not standing there staring at the clock. And if something’s optional, it’s marked—because the last thing anyone needs is another rule.
The fixes
The second draft is where the recipe survives the things that always go wrong: undercooked centers, over-salted sauces, forgotten spices. Every ‘pro tip’ here is something that actually fixes a problem, not just sounds impressive.
The third draft is for the people who’ll read it at 11 PM with half the ingredients. That’s when the swaps, the shortcuts, and the ‘don’t panic’ notes go in.
What we will not do
This isn’t a place for recipes that require a degree in culinary arts, a $200 tool, or the patience of a saint. No ‘deconstructed’ anything, no dishes that need to be plated like a museum exhibit, and no ‘fusion’ unless it’s the kind that actually works.
Things you will never find here
- Recipes that assume you have a mandoline, a sous-vide machine, or a ‘perfect’ kitchen.
- Dishes that take longer to explain than they do to make.
- Photos of food that looks like it was staged by a food stylist (it wasn’t).
- Claims about ‘authentic’ anything—just the best version we could make with what we had.
Where to start
If you’re new, try the ‘Beginner’s Pantry’ section—it’s for the five ingredients you probably already have. If you’re looking for something specific, use the search bar. If you’re still stuck, the ‘Troubleshooting’ page lists the most common kitchen disasters and how to survive them.
Say hello
I like hearing about the dishes that went right, the ones that went wrong, and the weird swaps people make when they’re out of an ingredient. If you’ve got a question or just want to say hi, the contact page is the place.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.