Why this site exists
You’re standing in your kitchen, holding a recipe card that promises something simple—maybe a sauce, maybe a stew—and nothing turns out right. The onions burn, the sauce separates, the texture is wrong. You’ve followed the steps, but the result doesn’t match the photo.
The frustration isn’t in the failure; it’s in the silence between what the recipe says and what actually happens.
This site exists to close that gap. Every recipe here starts with the question *why did this go wrong?* and ends with a version that works—not just once, but reliably. No shortcuts, no assumptions.
Just the steps that turn ingredients into something that tastes like it was meant to be made.
Who writes this site
Dominic Dubois is the person behind the recipes. They write, test, and rewrite everything here.
Do you test every recipe yourself?
Yes, but not always perfectly the first time. Some recipes take three tries before they land right—especially the ones that sound easy but aren’t. If it’s not tested, it’s not here.
What do you get wrong?
Everything, at least once. Timing, heat, even basic measurements. The difference is that I write down what went wrong so the next person doesn’t have to guess.
Why is something missing that I’d expect?
Because it either doesn’t work, or I haven’t figured out how to make it work yet. If it’s not here, it’s not because it’s unimportant—it’s because it’s still a work in progress.
They keep a handwritten notebook by the stove where every failed attempt gets a single line: *‘too much salt, next time halve the stock.’* No erasures, no second thoughts.
How a recipe is built
A recipe here begins with a question: *What’s the one thing that always goes wrong with this?* It could be a sauce that splits, a crust that cracks, or a dish that’s dry no matter how much liquid you add. The answer isn’t just the fix—it’s the *why* behind it.
The first draft
The first version of any recipe is written after one successful attempt. That’s it. No notes, no adjustments—just the steps as they happened. The goal isn’t perfection; it’s a baseline. If the sauce worked once, it’s worth writing down, even if the texture isn’t ideal.
The second draft
The second version comes after three failures. That’s when the real work starts: measuring again, adjusting heat, testing substitutions. The recipe isn’t just about ingredients—it’s about the conditions that make them work. If it doesn’t hold up after three tries, it’s not published.
What we will not do
This site won’t pretend every recipe is foolproof, or that every technique is intuitive. Some dishes require patience, some demand precision, and some will never turn out the way you expect—but they’ll still taste good.
Things you will never find here
- Recipes that skip steps or assume prior knowledge.
- Photos of food that look nothing like the real thing.
- Claims about ‘authentic’ techniques without context.
- Advice that treats cooking like a performance, not a process.
Where to start
If you’re new, begin with the *Troubleshooting* section—it’s where most mistakes get solved. If you’re looking for a specific dish, use the search. If you can’t find what you came for, the *Contact* page is where to ask.
Say hello
The best emails are the ones that start with *‘This worked, but the specific thing was off—here’s what fixed it.’* Or just questions: *‘Why does this sauce need to rest?’* Or complaints: *‘The instructions for dish didn’t make sense.’* The contact page is where to send them.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.