Why this site exists
You’re standing in the kitchen, a recipe open in front of you, and something isn’t right. The sauce is too thin, the timing feels off, or the flavors just don’t click. Maybe you’ve tried the same dish three times and still can’t get it. Maybe you’re tired of guessing.
This site exists to cut through that frustration. Every recipe here is tested until it works—not just once, but until it works for someone who might be cooking it for the first time.
No shortcuts, no vague measurements, no ‘taste as you go’ when you don’t know what ‘good’ tastes like yet.
Who writes this site
Corinne Beaudry runs the site and writes most of the recipes.
Do you really test every recipe multiple times?
Yes. If a dish doesn’t work the third time, it doesn’t get published. That’s why some recipes look simple—they’ve been simplified down to what actually works, not what *should* work.
What do you get wrong the most?
Timing. I’ll overcook something by two minutes and think it’s perfect, then realize it’s mushy. That’s why every recipe has exact times—and why I always say ‘remove from heat’ instead of ‘let it simmer.’
Why isn’t [a popular dish] here?
Either I haven’t found a version that works for a home kitchen, or it’s something I don’t actually like. If you’re missing a dish, it’s probably because I haven’t figured it out yet—or I’m stubborn about it.
The first thing I do when a recipe fails is check the salt. Not because I’m perfect at it, but because salt fixes more things than anything else.
How a recipe is built
A recipe starts with a question: *What’s the one thing that always goes wrong in this dish?* For lasagna, it’s the noodles getting soggy. For roasted chicken, it’s the skin burning before the meat is done.
The goal isn’t to make the ‘best’ version—it’s to make the version that won’t make you want to throw the pan out the window.
The first test
I cook it exactly as written, using the cheapest ingredients I can find. If it works then, it’s ready. If not, I adjust one thing at a time—temperature, time, or technique—until it does. No substitutions, no shortcuts.
The first test is always the hardest because that’s when you realize what you don’t know.
The second test
I give it to someone who’s never made the dish before. If they can follow the steps without guessing, it’s done. If they get stuck, I rewrite the instructions. The second test isn’t about perfection—it’s about clarity. A recipe should work even if you’re tired, distracted, or both.
What we will not do
This site won’t publish recipes that require rare ingredients, obscure techniques, or more than 15 minutes of active work. We won’t pretend every dish is a ‘showstopper’—some recipes are just for feeding people without stress. And we won’t ignore mistakes just to keep the numbers up.
Things you will never find here
- Recipes that take longer than an hour to prepare.
- Dishes with more than five ingredients (unless they’re pantry staples).
- ‘Fancy’ plating instructions—if it looks good on the plate, you’ve already won.
- Anything that requires a specialized tool you don’t already own.
Where to start
If you’re new, begin with the ‘Weeknight Essentials’ section—those are the dishes that feed a family without turning the kitchen into a battlefield. If you’re looking for something specific, search by ingredient or technique.
And if you can’t find what you came for, the contact page is the best place to ask why.
Say hello
We like hearing about the dishes that worked, the ones that didn’t, and the weird substitutions people try. If you’ve got a question or a suggestion, the contact page is where to leave it. No emails, no exceptions.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.