About Rice and Recipes

What changed, and what it changed for you

When Rice and Recipes started, it was a side project: a place to dump recipes I loved, with no real plan. The first few posts were just photos and instructions lifted from other sites, sometimes even with typos.

There was no system, no way to organize anything, and the whole thing felt like a half-finished notebook.

Now, every recipe is built to work. We test every ingredient, measure, and step before publishing. The site itself is faster, easier to navigate, and designed so you can find what you need without digging. The difference isn’t just in how it looks—it’s in how it *works* for you.

The one that took years

The biggest mistake was assuming recipes would work as written. I’d find a dish online, tweak it slightly, and post it without ever actually making it myself. Half the time, the results were disappointing—sometimes even inedible. But I kept doing it because it was faster than cooking from scratch.

It stayed this way for years because I didn’t realize how much it mattered. I thought ‘good enough’ was enough, and I was too busy adding new recipes to slow down and fix old ones.

The turning point came when a reader pointed out that a ‘5-minute’ pasta sauce actually took 45 minutes to make. That was the moment I stopped.

Now, every recipe is tested at least three times. That means more work—sometimes a single dish takes a full weekend to perfect—but it also means no more surprises. The cost? Time, mostly. But the payoff is recipes you can actually trust.

Meet the author

I used to think cooking was about following rules. My early recipes were stiff, precise, and full of assumptions—like every dish needed a specific temperature or a certain brand of oil. I’d spend hours researching techniques I’d never actually use, and the results were often boring. The worst part?

I never tasted my own food while cooking. I’d just read the instructions and hope for the best.

I also believed that if a recipe didn’t work, it was the cook’s fault. That mindset led to a lot of frustration—especially when I’d ruin a dish because I skipped a step or mismeasured an ingredient.

Once, I burned a batch of cookies because I ignored the oven’s preheating time, and I threw them out without tasting them. That was the moment I realized: if I didn’t care enough to taste, why should anyone else?

Everything changed when I started making recipes the way I eat them: imperfect, adaptable, and full of flavor.

Now, Clifford Hutchins runs this site. He tests every recipe, adjusts it until it’s just right, and writes about cooking like it’s a conversation—not a set of instructions. The kitchen is still his playground, but now the rules are his to break.

What did not change

The core idea hasn’t wavered: food should bring people together. Whether it’s a weeknight dinner or a holiday feast, the best meals are the ones that feel like home. That hasn’t changed, and it won’t. The other constant? No fancy ingredients, no gimmicks.

If it doesn’t taste good with what you already have, it’s not worth writing about.

I still cook with my mom’s old cast-iron skillet, and I still taste everything before serving. The tools might be better now, but the philosophy is the same: real food, real flavors, no shortcuts.

What is still being fixed

The biggest project right now is making the site even faster—especially on mobile. Some pages still load slower than they should, and that’s frustrating for everyone. We’re also working on better filters for dietary restrictions (vegan, gluten-free, etc.) so you can find exactly what you need without extra clicks.

If you’ve got ideas—whether it’s a recipe you’d love to see or a feature you’d use—let us know. The contact page is the best place to share them.