About Chicken Recipes Fry

What changed, and what it changed for you

When this site started, it was just a way to keep track of the recipes I’d scribbled on napkins or typed into my phone’s notes app.

The instructions were shorthand—‘brown the chicken well’ meant until it smelled like heaven, not ‘8-10 minutes.’ Measurements were guesses, timings were flexible, and if a dish failed, I’d just try again until it didn’t. The photos?

Taken in whatever light was available, often at 3 AM after a long shift at the diner.

Now, every recipe is tested in two kitchens—mine and someone else’s—with adjustments for oven quirks, sheet pans that don’t fit, and the chaos of home cooking.

The instructions are broken into steps that actually make sense, the photos show the real result (not a staged shot), and the ‘why this works’ section explains the science behind the sizzle.

The goal wasn’t to sound like a chef’s manual; it was to make sure you could follow along without second-guessing every move.

The one that took years

The biggest mistake was assuming that if a recipe worked for me, it would work for everyone.

My dad’s old cookbook had handwritten notes like ‘let it rest 20 mins (or until you’re bored)’—useful if you’re cooking in a restaurant kitchen with a timer, useless if you’re staring at a clock waiting for the meat to hit 165°F.

For years, I ignored that problem because fixing it meant rewriting every recipe from scratch, which felt like admitting the old ones were wrong.

It took burning a batch of fried chicken—*again*—to realize the issue wasn’t the recipes. It was the instructions. The first time I tested a recipe with a volunteer who’d never cooked before, they followed the steps exactly and still ended up with dry wings.

That’s when I started breaking things down: ‘preheat oven to 375°F (that’s 190°C if you’re outside the US)’ or ‘batter should coat the back of a spoon—if it slides off, add more flour.’ Small changes, but they turned a guess into a plan.

Now, every recipe includes a ‘what can go wrong’ section with fixes—like ‘if your pan isn’t hot enough, the chicken will steam instead of sear.’ It’s not just about the steps; it’s about the *why*. The cost? Time.

Rewriting 50 recipes took months, and I still catch myself wanting to cut corners. But the alternative—leaving someone stuck with rubbery chicken or burnt edges—wasn’t worth it.

Meet the author

I grew up in a kitchen where the only rule was ‘if it tastes good, it’s done.’ My dad’s cookbook collection was my first teacher—yellowed pages, smudged margins, and recipes that assumed you already knew how to ‘brown meat properly.’ I’d stand on a stool, stirring a pot of beans or flipping pancakes, convinced that if I followed the steps exactly, everything would turn out right.

It rarely did. The first time I made a dish that didn’t taste like ‘close enough,’ I was eleven, and I cried because the biscuits had collapsed.

For years, I treated cooking like a puzzle to solve on the fly. If a recipe failed, I’d tweak it until it worked—no notes, no second attempts, just muscle memory.

I’d take photos with my phone in whatever light was handy, upload them to the site without a second thought, and move on. The result? Recipes that looked great in the photos but tasted like ‘almost right’ in real life.

The worst was a batch of fried chicken that turned out greasy because I’d rushed the oil change. I threw it out and swore I’d never make that mistake again.

What changed was realizing that ‘good enough’ wasn’t enough for anyone but me.

Now, I run this site the way I wish I’d learned to cook: with patience, a notepad, and a willingness to admit when I’m wrong. Nolan Barrera tests every recipe twice—once in my kitchen, once in someone else’s—and writes the instructions like they’re for a first-time cook.

The photos are shot in the same light, the measurements are precise, and the ‘why this works’ section explains the science behind the sizzle. If a dish fails, we figure out why before we post it.

It’s slower, but it’s how I cook now: no shortcuts, no guesswork, just food that tastes like it was made with care.

What did not change

The core hasn’t shifted: this site is still for the recipes that feel like coming home. Whether it’s my abuela’s chicken soup or a modern twist on fried chicken, the goal is the same—dishes that taste like they were made with love, not pressure. The tone hasn’t changed either.

No chef-speak, no pretentious language. If I’d write it to my younger self, that’s how it stays.

The other constant? The people behind the recipes. Every dish here is tied to a memory—a family gathering, a late-night diner meal, or a volunteer’s first successful attempt at something they’d given up on. Those stories don’t disappear; they’re just told better now.

The ‘why this works’ section isn’t just science—it’s the reason this recipe matters.

What is still being fixed

Right now, we’re working on making the site faster—loading times matter when someone’s mid-recipe and waiting for a photo to appear. We’re also testing more recipes with volunteers who’ve never cooked before, to catch the steps that still assume too much.

And yes, the contact page is still the best place to suggest a recipe or point out a mistake. (We read every message.)

If you’ve got a recipe that’s worked for you—or one that’s always failed—tell us about it. The contact page is where it starts.