About Recipes Bundle

Why I started Recipes Bundle

It was a Sunday afternoon in my mother’s kitchen, and I was supposed to be helping her make her famous *pollo al limón*—the one that always left the house smelling like lemon and garlic. I followed the recipe exactly, down to the ‘let the chicken rest for 10 minutes’ part.

Then I cut into it, and the meat was dry, the skin rubbery, the sauce watery. My mom looked at the clock, then at me, and said, *‘Hijo, you didn’t let it rest.

You didn’t even check the oven temp.’* That’s when I realized most recipes were missing the *why* behind the steps.

This site exists because I’ve spent years fixing dishes that went wrong—not because of bad ingredients, but because the instructions skipped the part where you actually *cook*. Every recipe here is tested until it works in a real kitchen, with real pans, real ovens, and real mistakes.

It’s for anyone who’s ever burned a casserole, over-salted a soup, or stood in front of an open fridge wondering what to do next. No shortcuts, no guesswork—just food that tastes like it was meant to be made.

Meet the founder

My mother’s kitchen was where I learned that cooking isn’t just about following steps—it’s about noticing when something’s off before it’s too late.

She’d hand me a wooden spoon and say, *‘Watch the color of the sauce, not the clock.’* I still do that today, even when I’m the only one in the kitchen.

That’s how I ended up testing recipes: not just once, but until the details—like the exact second a roast starts to brown or how long a dough *should* rest—stop feeling like guesswork.

The one tool I still use from those early days is a cast-iron skillet with a handle so warped it’s nearly useless. It’s got a dent from when I dropped it as a kid, and the seasoning is patchy where I scrubbed it too hard after that first burned pollo.

I keep it because it reminds me that the best recipes aren’t about perfect tools—they’re about paying attention. And because, no matter how many times I try, I still can’t find a replacement that sears like it does.

The dish that changed everything was a *risotto alla Milanese*. I followed a recipe word-for-word, stirring like I was supposed to, but the rice was mushy and the saffron flavor had vanished.

My mom walked in, tasted it, and said, *‘You didn’t toast the rice first.’* That’s when I realized recipes often skip the ‘before you even start’ part. Now, every recipe here includes those hidden steps—the ones that turn a good dish into a great one.

I have a habit of writing down every adjustment I make, even the tiny ones. If I add an extra pinch of salt or let something simmer 30 seconds longer, it goes in the notes.

It drives my friends crazy—I’ll pull out my phone mid-conversation to jot down a timing change—but it’s how I catch mistakes before they become permanent. And yes, I still hum while I cook. My mother did too.

Meet the mascot

The mascot started as a scribble on a napkin at a café in Lisbon, where I was trying to explain to a friend why a *pastel de nata* recipe had gone wrong.

I drew a rough circle for the pan, a wavy line for the caramelized top, and a question mark where the custard should’ve been.

The first version had too many details—the cracks in the crust looked like a topographic map—and the friend laughed and said it looked like a ‘confused meringue.’

The next draft was cleaner: just the pan’s silhouette, a single crack in the crust, and a dot for the custard. I added a tiny flame underneath to remind people that heat matters. The problem was, it still looked too static.

So I gave it a tilt—like the pan had just been pulled from the oven—and a wisp of smoke curling up from the side. That’s when it started to feel right: not just a drawing, but something that said *‘This is how things go wrong if you’re not careful.’*

The final version lost even more detail. The flame became a single line, the crack simplified to a jagged edge, and the smoke turned into a tiny loop. It had to work at the size of a browser tab, so every line had to mean something.

I named it *O Relâmpago*—the Lightning Bolt—not because it’s fast, but because it’s the sound you hear when a dish finally comes together after everything else has gone wrong.

What I promise you

This site isn’t about perfect food—it’s about food that works. You won’t find recipes here that require a $200 pan or a technique you’ve never heard of. What you *will* find is clarity: exact times, specific tools (or substitutes), and notes that explain *why* a step exists.

If a recipe says ‘simmer for 20 minutes,’ it’s because I’ve tested it at 15, 20, and 25 minutes. If it says ‘use a Dutch oven,’ it’s because a pot won’t cut it.

How I create a recipe

A recipe starts in my kitchen, but it doesn’t end there. The first version is always messy—I’ll write notes in the margins, cross out steps that don’t work, and circle the parts that feel *off*.

But the real test comes when I give it to someone who’s never made the dish before. If they get stuck, if they ask *‘Why?’* more than three times, or if the result doesn’t taste like what the photo promised, we go back to the drawing board.

The first test: hands-on

The first stage is always about *feeling* the dish. I’ll sear a protein until the edges release easily from the pan, then check the internal temp with a thermometer—no guessing. For sauces, I taste as I go, adjusting acidity or sweetness in 5% increments until it balances.

The moment something goes wrong is usually when I stop paying attention: a sauce boils over because I was distracted, a crust burns because I forgot to rotate the pan. Real times matter—‘until it looks right’ isn’t a step here.

The second test: the fix

If a dish fails the first test, I don’t just tweak the recipe—I retest the *method*. Maybe the protein needed to rest longer, or the sauce required a reduction at a lower heat. I’ll write down every change, then send it to a volunteer who’s never cooked this before.

If they still struggle, we scrap it or rewrite it entirely. The goal isn’t perfection; it’s reliability. A recipe that works for a beginner is better than one that only works for a chef.

How a page gets onto this site

Once a recipe passes the kitchen test, I write it down while it’s still warm—notes scribbled on paper, timings jotted in the margins, and a photo taken with my phone (no fancy lighting, just the real thing).

Then I sit at my desk, cut out anything that doesn’t serve the reader, and rewrite the steps so they’re clear even if you’ve never cooked this before. Some pages get rewritten months later because a reader pointed out a missing detail or a step that didn’t make sense.

That’s how you know it’s done right.

Write to me

I love hearing about the dishes you’ve made—or the ones that went wrong. Did a recipe here work for you? Did you try a substitution that changed everything? Or did you get stuck on a step and figure out a better way?

The contact page is where to tell me. (And yes, if your version is better than mine, I’ll update the recipe.)

This site exists because cooking should feel like less of a guessing game and more of a conversation. Thanks for being part of it.

—Hector Marchetti