About Rice Recipes House

What changed, and what it changed for you

Rice Recipes House started as a scrappy blog where I’d scribble down recipes I’d found online, tweaking them just enough to call them my own. There were no photos, no structure, and definitely no thought given to how someone else would actually use the page.

If you landed here, you got a list of ingredients and a prayer.

Now, every recipe is built to work—tested at least three times, with adjustments for altitude, stovetop vs. rice cooker, and even dietary swaps. The site looks different too: clear headings, ingredient breakdowns, and a search that actually finds what you’re looking for.

The goal wasn’t just to share a dish; it was to make cooking feel like less of a guessing game.

The one that took years

For the first two years, I refused to photograph my own food. I’d take blurry shots with my phone in bad light, or steal images from other sites and call it a day. The problem wasn’t laziness—it was fear.

I didn’t trust my eye, and I knew if I put my name on a photo, people would notice if the rice was undercooked or the colors were off.

It stayed that way because I convinced myself ‘good enough’ was the same as ‘professional.’ I’d see chefs with fancy cameras and think, *That’s not me.* Meanwhile, the site felt half-finished. Recipes were trustworthy, but the presentation made them seem amateurish.

The turning point came when a reader emailed—*not* to complain, but to say they’d made a recipe but ‘couldn’t tell if the jasmine rice was done because the photo didn’t show the texture.’ That stung. I bought a used DSLR, set up a cheap light setup, and started over.

Now, every recipe has at least three photos: the final dish, a close-up of the texture, and one mid-cook so you know what ‘done’ looks like.

It cost $300 upfront for gear, and another $200 last year to upgrade the lights, but it was the first change that made people say, *This site actually helps me cook.*

Meet the author

I used to think cooking was about following rules. My abuela would sigh every time I measured spices ‘by the pinch’ instead of the teaspoon, and I’d argue that ‘close enough’ was good enough.

I’d post recipes online with no notes on why a dish mattered—just the steps, like a math problem with no story behind it. The worst part? I’d get frustrated when readers asked for help troubleshooting, because I’d never written down what *I* did when things went wrong.

There was one recipe I ruined so badly it nearly killed the site. A risotto I’d adapted from a French chef’s book turned out gummy and bland because I’d ignored the ‘toast the rice in butter’ step.

I deleted the post, but not before a few dozen people had tried it—and complained. That was the day I realized: if I didn’t treat my own mistakes as part of the story, why should anyone else?

What changed: I stopped pretending I knew everything.

Now, I run Rice Recipes House the way Wesley Grimaldi does—with a camera, a notebook full of ‘what went wrong’ scribbles, and a rule that every recipe must include at least one thing I learned the hard way.

My abuela would roll her eyes at the photos, but she’d nod when I’d say, *This is how it’s supposed to taste—and here’s how to fix it if it doesn’t.*

What did not change

The core belief hasn’t wavered: rice isn’t just food. It’s the glue that holds a meal together, the thing that turns a pile of ingredients into something you actually want to eat.

That’s why this site will always prioritize dishes where rice—or another grain—is the star, not just a side note.

Neither has the approach to teaching. I still think the best way to learn is by doing, which is why every recipe includes a ‘troubleshooting’ section. If you burn the bottom of your paella, or your fried rice turns out dry, you’ll find a fix here—no mystery, no shame.

That’s not going to change, even if the site gets fancier.

What is still being fixed

Right now, the biggest project is making search work for *real* questions.

You shouldn’t have to scroll through 20 ‘best rice recipes’ to find answers to ‘why did my basmati turn mushy?’ or ‘how do I cook rice on a camp stove?’ I’m rewriting the backend to prioritize those kinds of searches, but it’ll take another year to get it right.

If you’ve got a recipe question that’s stumped you, or a dish you’d love to see here, the contact page is the place to tell me about it.