About Recipes Juniper

What changed, and what it changed for you

The first version of this site was a mess. Recipes were copied from other blogs or pulled from memory, with no testing beyond a single try. Photos were taken in whatever light happened to be in the kitchen, and the instructions assumed the reader had the same tools and experience.

It was thin, inconsistent, and—worst of all—it didn’t trust the people reading it.

Now, every recipe is tested at least twice: once by me, and once by someone who isn’t a chef. The photos are shot in the same setup, with the same lighting and angle, so you’re not guessing what the final dish should look like.

The structure is tighter, the language is clearer, and the focus is on what actually works in a real kitchen—not just what sounds good in theory.

The difference is in the details. A recipe that once said ‘season to taste’ now lists exact measurements. A photo that used to be blurry or poorly lit now shows the dish as it should be.

And the site itself—once a scattershot collection—now feels like a place where every dish has earned its spot.

The one that took years

The biggest problem was trust. For years, I wrote recipes the way I’d been taught: pull from memory, tweak as you go, and hope it works. But that meant every dish was a gamble—even for me.

The first time I burned a batch of cookies because the oven ran hotter than expected, I realised how little I’d actually tested. The second time, I stopped pretending it was fine.

The real blocker wasn’t laziness. It was fear. Testing properly meant admitting that some recipes wouldn’t work, that certain techniques required more patience than I had, and that I’d have to rewrite everything from scratch. It also meant slowing down—a lot.

What used to take an afternoon now takes a week, from the first draft to the final edit.

The turning point came when I started sending recipes to friends who weren’t chefs. Their feedback was brutal, but necessary. ‘This says to bake for 20 minutes, but my oven takes 30,’ one wrote. ‘The spices are too vague,’ another said.

I took notes, adjusted, and realised that if *they* couldn’t follow it, neither could anyone else. Now, every recipe has a ‘real kitchen’ version—with extra time, troubleshooting, and a note if something might go wrong.

It costs time, sure, but the alternative was worse: a site full of dishes that sounded great but fell apart in practice. The price of doing it right? A slower start, more rewrites, and a few ruined batches along the way.

But the payoff is worth it—every recipe here is something you can actually make.

Meet the author

I used to believe that cooking was about instinct—throw in the ingredients, trust your nose, and hope for the best. My early recipes were a mix of family hand-me-downs and half-remembered techniques, written down in whatever order they came to mind.

I’d test a dish once, maybe twice, and if it worked, I’d call it done. The result? A site full of dishes that *could* work, but often didn’t—especially if you didn’t have the same tools, oven, or experience I did.

The worst failure wasn’t a burned dish or a recipe that flopped. It was the moment I realised I’d been lying to myself—and to the people reading. I’d written a guide to perfecting roasted chicken, but half the steps assumed you knew how to brine or why temperature mattered.

When a reader emailed to say their chicken came out dry, I had no real answer. That’s when I stopped pretending I knew everything.

What changed is that I stopped writing recipes. I started building them.

Now, Priya Rasmussen runs this site, and her work is in the details. Every recipe begins with a conversation: what’s the point of this dish? Who is it for? What could go wrong?

She tests in real kitchens—her own, borrowed ones, and those of friends who aren’t chefs—then rewrites until it works for someone who’s never made it before. The result isn’t just a recipe; it’s a plan. And the one thing that hasn’t changed?

The belief that the best dishes are the ones that turn a good meal into a story worth telling.

What did not change

The core idea hasn’t wavered: this site exists for the dishes that matter—whether they’re handed down from a family or stumbled upon by accident. The focus on juniper as a flavor hasn’t shifted either; it’s still the thread that ties the roasts, the cocktails, and even the unexpected twists together.

And the rule about no shortcuts? That’s been here from the start.

What hasn’t changed is the reason this site exists at all. It’s not about perfection—it’s about the dishes that feel like home, even when they’re new. The ones that make you pause mid-bite and think, *This is why I cook.*

What is still being fixed

Right now, the biggest project is making sure every recipe has a ‘troubleshooting’ section—because even the best-tested dish can go wrong. We’re also working on a better way to organise the archive, so you can find what you’re looking for without digging.

And yes, the photos still need one more round of consistency checks.

If you’ve got a recipe that didn’t work, a technique you’ve always wanted to master, or even just a dish you’d love to see here, the contact page is the place to say so.