About Recipes Orbit

What changed, and what it changed for you

When Recipes Orbit started, it was a list of dishes I’d made and liked—no structure, no testing beyond my own kitchen.

Recipes were copied from blogs or books, sometimes with minor tweaks, but rarely adjusted for the real world: the oven that runs hotter than the dial says, the humidity that makes dough stick, the fact that most home cooks don’t own a mandoline. The result?

Instructions that felt like guesswork, even for simple dishes.

Now, every recipe is tested at least twice—in my kitchen and in someone else’s—with notes on what went wrong and how to fix it.

The site isn’t just a collection anymore; it’s a system built around balance: how much acid cuts through richness, how long to rest meat for the best texture, why a pinch of salt at the right moment makes all the difference.

You won’t find vague terms like ‘cook until done’ here. You’ll find timings, temperatures, and troubleshooting for the things that actually happen in a real kitchen.

The one that took years

The biggest change—the one that took years to fix—was the idea that a recipe could be ‘perfect’ the first time it was written. For years, I treated recipes like instructions for a machine: precise, unchanging, and assumed to work the same way every time. But cooking isn’t like that.

A dish that works in my kitchen—with its specific oven, humidity, and tools—often fails in someone else’s. The problem wasn’t the recipes; it was the assumption that they didn’t need to adapt.

It took years to admit that the real work wasn’t writing the recipe, but testing it in enough different conditions to make it reliable.

That meant cooking the same dish in apartments with tiny stoves, in kitchens with ovens that ran hot, in places where the air was thick with humidity. It meant asking volunteers to make the recipes and report back when something went wrong.

And it meant accepting that some dishes would never be ‘foolproof’—just better than they were before.

The cost? Time. Every recipe now takes at least three times as long to finalize as it did before. But the payoff is that when you open a page here, you’re not just getting instructions—you’re getting a dish that’s been stress-tested for the things that actually break in real kitchens.

And that’s worth the wait.

Meet the author

I grew up in a small apartment where the kitchen was a single burner on a counter, and my first ‘cooking’ lessons were learning how to boil pasta without burning the water or over-salting it.

I believed that good cooking was about following rules—measuring precisely, timing exactly, never deviating from the original. That approach worked for a while, until I realized that most recipes were written for professional kitchens, not home cooks.

The first time I made a dish that turned out wrong because of an oven quirk, I doubled down on the rules instead of questioning them.

The breaking point came when I asked a friend to test a recipe I’d spent weeks perfecting. They followed the instructions exactly—and still ended up with something that tasted off. That’s when I realized the problem wasn’t the cook; it was the recipe itself.

It wasn’t written for the messes that happen in real kitchens.

What changed is that I stopped treating recipes as fixed instructions and started treating them as living things—something that needs to be tested, adjusted, and rewritten until it works in as many conditions as possible.

Now, I’m Hector Trujillo, and this is where I write recipes that are tested for the things that actually go wrong: the oven that runs hot, the humidity that makes dough stick, the fact that most home cooks don’t own a mandoline.

Every dish here is built to work the first time, not because it’s perfect, but because it’s been pushed until it stops breaking.

What did not change

The core idea behind Recipes Orbit hasn’t shifted: this site exists to share dishes that work, not just sound good on paper. That means no shortcuts, no vague instructions, and no assumptions about what you already know. The belief that cooking should be reliable—even when life isn’t—has stayed the same.

And the focus on traditional techniques alongside modern twists? That’s been here from the start.

What hasn’t changed is the kitchen itself. The stove where I test every recipe is still the same one I used when this site began—a small apartment model with quirks that force me to think like a home cook, not a chef.

The tools are the same, too: no high-end gadgets, just the kind of things you’d find in a real kitchen. The only difference is that now, I know how to work around their limitations instead of pretending they don’t exist.

What is still being fixed

Right now, the biggest project is building a system to track how recipes perform across different altitudes and climates. Some dishes need adjustments for high humidity, others for thin mountain air, and most recipes don’t account for either.

The goal is to create a database of ‘what usually goes wrong’ in specific conditions, so every recipe can include troubleshooting tailored to where you live.

If you’ve got a kitchen quirk—an oven that runs hot, a stove that won’t simmer, or a climate that messes with your baking—let me know. The contact page is the best place to share what you’ve learned, and what still frustrates you.