What changed, and what it changed for you
The first version of this site was a mess. Recipes were copied verbatim from cookbooks and blogs, with no adjustments for real kitchens—ovens that run hot, pans that don’t conduct heat evenly, or the way dough behaves when it’s cold.
The instructions assumed you had every tool mentioned, and the photos looked nothing like the actual result. It was just a list of things I liked, with no rhyme or reason beyond ‘this worked for me once.’
Now, every recipe is tested in at least two different kitchens—mine, and someone else’s who has never made the dish before. We adjust for altitude, humidity, and the quirks of home cooking.
The steps are written to work with what most people actually have in their pantries, not what a professional chef might. And the photos? They show the real thing, not a staged version that looks impossible to replicate.
| It used to be | Now it is |
|---|---|
| Recipes copied directly from other sources without testing | Every recipe tested twice—once by me, once by a volunteer who cooks it blind |
| Photos taken in whatever light was available | Every shot lit to match the final dish, with no shadows hiding the texture |
| Instructions assumed you had specialized tools | Steps written for real kitchens, with substitutions for common gaps |
| No structure—just a list of favorites | Every page follows the same clear format: ingredients, steps, timing, and troubleshooting |
The one that took years
The biggest mistake was trusting photos over taste. For years, I’d pick recipes because the photos looked impressive, only to find the flavors were off or the texture was wrong. I’d tweak things in my head but never actually test them properly—just assume the next attempt would work. It didn’t.
The site was full of dishes that looked great but tasted mediocre, and I didn’t even notice until readers started pointing it out.
The problem wasn’t laziness; it was pride. I believed that if a recipe was in a well-known cookbook, it must be perfect. I’d spend hours debating whether to adjust a pinch of salt but never question the core method.
It took a reader sending me a message—‘I followed your recipe for the chocolate tart, and it’s delicious, but the crust is too crumbly’—to make me realize I’d been wrong the whole time.
Fixing it cost time, money, and a lot of ruined batches. Testing a single recipe now takes at least a week: I make it twice, then send the notes to a volunteer who cooks it from scratch without any prior knowledge. If something goes wrong, we troubleshoot it together.
So far, we’ve had to scrap or rewrite nearly half of the original recipes. But the result? Every dish on this site now tastes as good as it looks—and that’s something I can actually trust.
Meet the author
I used to think cooking was about following rules. If a recipe said ‘preheat to 375°F,’ I’d set the oven to exactly that, no matter what. If it called for ‘one cup of flour,’ I’d measure it precisely, even if the dough turned out dense and heavy.
I believed that if you did everything right, the result would always be perfect. It never was. The first time I burned a batch of cookies because I ignored the ‘watch closely’ warning, I swore I’d never make that mistake again—but I did, a dozen times over.
I also used to write like I was giving instructions to a robot. ‘Cream the butter and sugar until light and fluffy.’ ‘Fold in the flour in thirds.’ No room for doubt, no allowance for the fact that some ovens run hot or that flour can vary in weight.
The recipes were clinical, and the results were often disappointing. The worst part? I didn’t even notice until someone else pointed out that my ‘perfect’ sourdough loaf was dense and heavy, not airy and crusty.
What changed: I stopped pretending I knew everything.
Now, I write like I’m talking to a friend who’s never baked before. The recipes include troubleshooting tips, substitutions for missing ingredients, and notes on what to do if something goes wrong. And I test everything—twice—before it goes live.
My name is Dominic Tanaka, and this is where I share the recipes that actually work, the way I’ve learned to cook: with patience, a little chaos, and no illusions about perfection.
What did not change
The core belief behind this site hasn’t wavered: the best recipes are the ones that bring people together. Whether it’s a Sunday family dinner or a last-minute weeknight meal, cooking should be something that connects us—not something that stresses us out.
That’s why every dish here is designed to work in a real kitchen, with real ingredients, and real people who might not have years of experience.
Another thing that stayed the same? The focus on tradition. I don’t believe in throwing out old methods just because they’re not ‘modern.’ Some of the best recipes are the ones that have been passed down for generations, even if they don’t fit into today’s trends.
The goal isn’t to reinvent the wheel; it’s to make sure the wheel still rolls smoothly.
What is still being fixed
Right now, we’re working on adding more troubleshooting guides—step-by-step fixes for when things go wrong in the kitchen. Too many recipes assume you’ll never have a problem, but we know that’s not true. We’re also testing more recipes with budget-friendly ingredients, so everyone can try them without breaking the bank.
And we’re still refining the testing process: every recipe should be tested in at least three different kitchens before it goes live.
If you’ve got a recipe that didn’t work—or a tip that saved your dinner—we’d love to hear about it. The contact page is where you can share your thoughts, your failures, and your successes. Let’s make this site even better, together.
Things that would help
- A recipe that worked for you after multiple failures—what did you change?
- A tip for fixing a common kitchen mistake (e.g., ‘if your cake sinks in the middle, try this’)
- A dish you’ve never seen a good recipe for—we’d love to test it ourselves
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.