
Why this site exists
You’re standing in the kitchen, a recipe in hand, and something isn’t right. The measurements feel off. The steps skip a critical step. The result doesn’t match the photo—or worse, it doesn’t taste like what you expected.
Recipes are supposed to be trustworthy, but too often they’re just placeholders, missing the details that turn good into great.
This site exists to fix that. Every recipe here is tested, tweaked, and rewritten until it works in a real kitchen—with real ingredients, real tools, and real mistakes. No shortcuts. No guesswork. Just dishes that deliver.
Who writes this site

Marcus Lindgren writes this site.
Do you test every recipe yourself?
Yes. Even if I’ve made it a dozen times, I test it again—with a timer, notes, and at least one disaster along the way. If it’s not *this* version that works, it’s not on the site.
What’s the most common mistake you see in recipes?
Assuming the reader has the same tools or ingredients. A whisk isn’t a mixer. Brown sugar isn’t white sugar. I call those out up front.
Why isn’t [a specific dish] here?
Either I haven’t nailed it yet, or it doesn’t fit the site’s focus—no quick hacks, no overly sweet desserts, no dishes that rely on ‘magic’ instead of skill. If you ask, I’ll tell you why.
I still keep my abuela’s chipped wooden spoon in the drawer. It’s the one I used to stir her chocolate mole when I was eight, and it’s the one I reach for when I’m nervous about a new recipe.
How a recipe is built
A recipe starts with a memory—or a failure. Maybe it’s a dish from a family gathering that never quite worked, or a restaurant plate so perfect it haunted me afterward. Or maybe it’s a mess: a cake that collapsed, a sauce that split.
Either way, the first version is always rough.
The first draft

I write it down exactly as I do it—no smoothing out, no skipping steps. If I eyeball the salt, that’s what goes in. If I burn the garlic, I note it. Then I make it again, adjusting for what went wrong.
The goal isn’t perfection on the first try; it’s finding out what *actually* happens in the kitchen.
The fixes
After three solid attempts, I go back and rewrite the steps. What was unclear? What needed a better tool or a longer rest? I test with substitutions—less butter, more acid, a different fat—and keep only what works. The final version is the one that survives at least five successful runs.
What we will not do
This site won’t publish recipes that rely on gimmicks, expensive shortcuts, or ingredients you can’t find outside a specialty store. No ‘5-minute’ dishes that taste like they took five minutes. No ‘foolproof’ methods that only work if you’ve done it a hundred times before.
Things you will never find here
- Recipes with more than three obscure ingredients.
- Steps that assume you already know how to do them.
- Dishes that require a specific brand of equipment.
- Photos that don’t match the final result.
Where to start
If you’re new, begin with the ‘Rich Chocolate Recipes’ tag—those are the ones I’ve tested the most. The ‘Techniques’ section explains the ‘why’ behind the steps. And if you can’t find what you’re looking for, the search works, but so does asking: the contact page is where to go.
Say hello
I like hearing about the dishes you’ve made—or the ones you’ve fixed after trying a recipe here. Did it work? Did it fail spectacularly? Send it to the contact page.
And if you’ve got a recipe that’s been in your family for generations but no one’s ever gotten right, tell me about it.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.
