About Chicken Recipes Plate

Welcome to Chicken Recipes Plate

You’ve got a recipe that sounds perfect—until you realize the ‘golden-brown crust’ is impossible in your oven, the ‘rest for 20 minutes’ turns into an hour, and the ‘juicy’ result is more like a soggy brick. Recipes are supposed to work, not just sound good on paper.

This is where they actually do.

Here, every dish is tested not once but twice—first by us, then by someone who isn’t a chef. No shortcuts, no assumptions about your kitchen. Just meals that taste like they were made with care, even when you’re not.

Our story

It started with a stack of yellowed cookbooks—my dad’s, passed down from his grandmother—where the pages were dog-eared from use, but the writing was smudged from hands that didn’t always measure carefully.

I’d trace the recipes with my finger as a kid, wondering why the roast chicken in the book never tasted like the one my mom made.

The first time I tried to recreate one of those recipes, I failed. The skin wasn’t crispy, the meat was dry, and the timing was all wrong.

I spent the next year testing, adjusting, and learning why recipes don’t always work—until I realized no one else was writing about the fixes.

By 2022, I was in a tiny apartment in Brooklyn, testing recipes at 3 AM after a long shift, with a cast-iron skillet that had seen better days. That’s when *Chicken Recipes Plate* began—not as a blog, but as a place where recipes actually delivered.

What we stand for

We believe recipes should be honest. No fake shortcuts, no photoshopped results, no instructions that assume you own a $300 thermometer. If a dish takes 30 minutes, we’ll say so. If it needs a rest, we’ll tell you why.

Meet the team

Behind every recipe is a team that knows what it’s like to burn dinner at 9 PM, to run out of salt mid-recipe, or to stare at a roast chicken wondering why the skin isn’t crisping. We’re not chefs by trade—just people who cook, test, and fix what doesn’t work.

Desmond Castellano

Desmond Castellano runs the site with the same stubbornness he used to argue with his mom over oven temperatures as a teenager. His background is in restaurant kitchens, where he learned that ‘perfect’ is a myth—but ‘good enough’ is what keeps people coming back.

Now, he tests every recipe twice: once in his Brooklyn apartment (where the oven runs hotter than it should) and once with a volunteer who isn’t a chef.

His desk is cluttered with a well-worn copy of *The Food Lab*, a thermometer that’s seen better days, and a notebook where he scribbles down every mistake. He always gets the rest times wrong—either underestimating how long meat needs to sit or forgetting to let it rest at all.

How we create our content

Every recipe starts with a question: *Why does this work?* (Or, more often, *Why doesn’t it?*) We dig into the science, the technique, and the real-world fixes—then test it in kitchens that aren’t showrooms. No recipe here is just copied from a cookbook or a blog.

The first test

We cook the recipe as written, using standard kitchen tools—a home oven, a basic thermometer, and whatever pans we have on hand. If it fails (and most do), we adjust: more salt, less time, a different fat.

We note every mistake—like when a roast chicken dries out because it rested too long or when a sauce splits because the heat was too high.

The first test takes 2–3 hours, with notes scribbled on a legal pad. We never skip this step. If a recipe doesn’t work the first time, we don’t publish it—we fix it.

The second test

The fixed recipe goes to a volunteer who isn’t a chef—someone who might not own a meat thermometer, who has a slow oven, or who burns toast. They cook it exactly as we write it, with no adjustments. If *they* run into problems, we go back to the drawing board.

Only after two successful tests—one by us, one by someone else—does a recipe get published. That’s how we know it’ll work for you.

Join our community

This isn’t just a site—it’s a conversation. Ask a question about why your pie crust turned out tough, or send in a recipe you’ve been struggling with. If we can fix it, we’ll publish the solution. If not, we’ll tell you why—and how to work around it.

The best suggestions come from readers who’ve tried the recipes, spotted a missing step, or found a better way. We’ve turned dozens of those into new posts, and we’re always looking for more.

Let's connect

We love hearing about the meals you’ve made, the mistakes you’ve fixed, or the recipes you’ve been meaning to try. If you’ve got a question, a tip, or just a story about cooking chicken the way it should be done, the contact page is where to start.

Welcome to the table.