Hi, I'm Aisha — the cook, tester and writer behind this site

Where this started

I grew up in a house where the kitchen was the busiest room in the place. Nobody wrote anything down — my mother cooked by feel, a handful of this, a splash of that, and somehow it came out right every single time. I spent years standing next to her without really paying attention, the way you don't when you're young and dinner just appears.

Cooking properly came later, once I had my own family and my own kitchen to fill. I'm 44 now, and I've been feeding hungry people across a dinner table for the better part of two decades. Somewhere in there, the guessing turned into something more deliberate: writing recipes down, testing them, and figuring out why the good ones were good.

Why I write recipes the way I do

The honest reason is frustration. I lost count of the recipes I tried online that looked beautiful and simply didn't work — cookies that spread into one flat sheet, cakes that sank in the middle, "30-minute" dinners that took an hour. Somewhere along the way I decided I'd rather share the tested version, including the parts that go wrong, than another pretty photo with a shaky method underneath.

So everything here is food I've actually made, usually several times, in an ordinary home kitchen with an oven that runs a little hot and the same tools most people own. If a step feels fussy, there's a reason for it, and I'll tell you what that reason is instead of leaving you guessing.

What you can trust here

• Every recipe is properly tested. If it's on the site, it's been developed and refined — often over several attempts — before publishing.
• Ordinary ingredients. I stick to what you can find in a normal grocery shop, and I always list a swap when something's less common.
• Honest notes. If a recipe is finicky, sweet, or easy to overbake, I say so. No overselling.
• Real reasoning. I explain the why behind the method so you can adapt it with confidence.
• Estimates flagged as estimates. Nutrition figures are a rough guide only — always check for your own needs.

How a recipe gets tested

Before anything goes up, I make it at least once from my own written notes — not from memory — to catch the gaps. If it's a bake, I usually run it again to check the timing and the texture hold up on a second try. Anything that needs a specific temperature, a rest, or a particular order gets flagged, because those are exactly the details that decide whether it works in your kitchen too. When a recipe finally earns its place here, it's because it did the job reliably, not just once by luck.

Say hello

This site is a one-woman kitchen, so hearing from readers genuinely matters. If you make something and it works, I'd love to know. If it doesn't, I'd love to know that even more — it's how these recipes keep getting better. You can email me any time at hello@xymic.click, drop a note through the contact page, or browse everything I've published on the recipe index.