About Recipes Compass

It started with one spice blend that kept burning

The first time I made *harissa*, it was a blistering July afternoon in a cramped apartment kitchen. The chili flakes were supposed to toast until fragrant, but by the time they smelled right, they’d already turned to ash.

The garlic, meant to sizzle just until golden, was blackened before I could pull the pan away. The cumin seeds, which should have bloomed with a nutty aroma, were bitter and acrid—like they’d been roasted too long for the pan’s uneven heat.

I adjusted the heat, tried a different pan, even swapped in fresh spices from the market. Nothing worked. The harissa either lost its depth or turned bitter, no matter how carefully I watched.

The recipe I’d followed for years—passed down from my mother—wasn’t translating to this stove, this altitude, this humidity. I had the ingredients right, the technique right, but the result was always wrong.

That failure sat in my mind for weeks. Every time I thought about harissa, I remembered the smoke, the burnt edges, the way the spices refused to cooperate. It wasn’t just the dish; it was the gap between what a recipe promised and what actually happened in a real kitchen.

That’s when I realised I wasn’t just making a spice blend—I was chasing the conditions that made it work.

Nine tries before it worked

The first five attempts were disasters. I toasted the spices too fast, too slow, in batches that didn’t bloom evenly. The cumin lost its warmth, the paprika turned dusty, and the garlic either burned or stayed raw.

I measured temperatures with an infrared thermometer, adjusted the pan size, even tried toasting the spices in the oven—only to come back to a kitchen smelling like burnt toast.

Then, on the sixth try, I changed everything.

Instead of toasting all the spices together, I did it in stages: first the cumin and coriander seeds until they smelled like a forest floor, then the garlic until it was golden but still held its shape, and finally the chili flakes, watched so closely that I pulled the pan the second they darkened.

The result was still imperfect, but it had *character*—a deep, smoky heat with layers of warmth beneath.

By the ninth try, I’d learned the rhythm. The pan had to be hot but not screaming, the spices had to move constantly, and the garlic had to be pulled out the second it looked right—no second guessing.

That batch was the first one that tasted like what I remembered from my mother’s kitchen: bold, balanced, and alive. It wasn’t perfect, but it was *true*.

The mind behind these pages

That’s how I ended up here: Loretta Boone, founder and editor of *Recipes Compass*, the person who kept adjusting the heat until the spices finally sang.

I run this site because I believe food should taste like *home*—not like a perfect photograph or a chef’s ideal, but like the messy, beautiful thing that happens when you pay attention.

I’m the kind of person who tries something nine times before giving up. My grandmother used to say I had ‘the stubbornness of a bad cook,’ and she wasn’t wrong. I’d rather ruin three batches than accept that a recipe ‘doesn’t work’ for me.

That habit cost me a few burnt dinners early on, but it’s what led me to test every single recipe here—because if it fails once, it’s not the dish’s fault. It’s the method’s.

Outside the kitchen, I’m the kind of person who plants too many seeds and forgets to water them. My windowsill is a graveyard of half-dead herbs, and my coffee table is always covered in half-finished projects. But in the kitchen, I’m precise—because I’ve learned that precision isn’t about perfection.

It’s about understanding what happens when things go wrong.

This site exists because of that harissa, because of the nine times it failed before it worked, and because I refuse to let a recipe stay broken.

Everything here is written the way that spice blend was

Every recipe on *Recipes Compass* is tested at least three times—once to learn the steps, once to catch the mistakes, and once to make sure it still works months later.

We don’t just write down what *should* happen; we write down what *does* happen, including the fixes for when things go wrong. If a dish needs an extra five minutes in the oven for your specific stove, that’s what you’ll read.

If a spice blend requires toasting in stages, that’s what you’ll follow.

The notes you see in the margins—like ‘pull the pan the second the garlic darkens’ or ‘reduce the heat if the oil smokes’—are there because someone, somewhere, burned a batch trying to ignore them. We include them because cooking isn’t about following instructions. It’s about adapting them.

And the only way to adapt is to know what happens when you don’t.

This isn’t a site for recipes that *could* work. It’s for recipes that *do* work, in your kitchen, with your tools, on your schedule. Just like that harissa, every dish here is the result of failure, adjustment, and finally—success.

What that means for you

You’ll never find a recipe here that promises ‘foolproof’ results. What you *will* find are dishes that have been tested for the chaos of real cooking: the stove that runs hot, the humidity that changes the texture, the ingredient that’s slightly off.

Every step is written to survive mistakes, not to demand perfection.

If a recipe here seems too detailed, it’s because we’ve already made it fail. The extra minute of toasting, the note about salt, the warning about overcrowding—they’re not there to complicate things.

They’re there to save you from burning a batch of spices (or your kitchen) while you figure it out.