
Why I started beanrecipessimmer
I was twenty-two, standing in a rented kitchen with a pot of black beans that had turned into a science experiment—too salty, too long simmered, and somehow also bitter.
My roommate, who’d lent me the recipe card, just shrugged and said, *‘You didn’t let it rest.’* That’s when I realised recipes weren’t just instructions. They were conversations, and the best ones had a little room for error.
This site is for those conversations. It’s for the person who’s measured everything twice and still ended up with a pot that looks like soup. For the cook who wants to know why a dish works—or why it doesn’t. No perfect photos, no ‘foolproof’ guarantees.
Just recipes that have been tested, trusted, and left a little room for rebellion, just like my grandmother’s mac and cheese.
Meet the founder

The first time I cooked, I was eight, standing on a stool in my grandmother’s kitchen, stirring a pot of mac and cheese with more butter than the recipe called for.
She laughed when I asked why the instructions didn’t say to add *‘a lot,’* and that’s when I knew cooking wasn’t about following steps—it was about taste, memory, and a little bit of rebellion.
This site is where I share those lessons: recipes that are tested, trusted, and just a little bit imperfect, because that’s where the best flavors live.
My grandmother’s cast-iron skillet is still in my kitchen. It’s got a dent from when I dropped it (the cheese didn’t burn, but the skillet did), and the handle is warped from years of dragging it from stove to table.
I keep it because it’s the only pot that ever made her laugh like that.
The failure that changed everything was a batch of adobo where I forgot to add the vinegar until the meat was already tender.
The sauce was flat, the flavors dull, and I spent the next week adjusting ratios until it tasted like the version my abuela made—sharp, bright, and impossible to mess up. Now, every recipe here starts with that lesson: taste as you go.
I still tap the pot with my knuckles before tasting. It’s a habit I can’t shake, a way to check if the sauce is thick enough without burning my tongue. My grandmother did it too, and I swear it’s the only way to know if a dish is ready.
Meet the mascot

The first scribble was on a napkin at a café in Oakland, where I’d gone to complain about a recipe that called for ‘a pinch of salt.’ I drew a bean pot with a face because I was frustrated, and the face ended up looking more like a wry grin than anything else.
The napkin got stained with coffee, so I redrew it properly on paper—this time with a spoon in one hand and a question mark floating above the pot, like the dish was still figuring itself out.
The proper version had to lose the café’s chipped table in the background and the smudge of my thumbprint on the pot’s lid. What stayed was the spoon (because stirring is half the work) and the question mark, because the best recipes always leave one thing unsaid.
The final version had to be simple enough to read at the size of a browser tab, so the spoon became a line and the question mark turned into a little cloud of steam.
We call it *Simmer.* It’s not a chef’s hat or a whisk or any of the usual symbols—it’s just a pot with a face, because cooking is the one place where mistakes don’t ruin the dish. They just make it better.
What I promise you
You’ll never see a recipe here that hasn’t been made at least twice—in my kitchen, and in someone else’s. If it’s not tested, it’s not posted.
What you can hold me to
- Every recipe includes a ‘What went wrong’ section—because even the best dishes have a flaw.
- If a step feels vague, it’s because we’re still figuring it out. You’ll see the notes where things go wrong.
- The tagline isn’t just decoration: a simmered sauce *does* hide the dish’s second secret.
- No recipe is ever ‘done.’ If you’ve made it better, tell me how.
How I create a recipe
A recipe here starts with a question, not a list. It could be *‘Why does my mole taste like cinnamon?’* or *‘How do I fix a sauce that’s too thin?’* The first version is always messy—half notes, half guesses—because the real work isn’t in the steps. It’s in the tasting.
The first simmer

The first stage is hands-on: stirring, tasting, adjusting. I don’t use timers unless I have to—most dishes know when they’re ready. A pot of beans should bubble gently before you add the salt; a sauce for chiles should darken at the edges before you pull it off the heat.
If the pot sticks, you’ve gone too fast. If the flavors taste flat, you’ve rushed the simmer. Real time? It depends. But 45 minutes is never enough for adobo, and 10 minutes is always too long for a quick salsa.
The second taste
The fixing comes after the pot’s off the heat. That’s when you adjust the salt, add a splash of acid, or let the dish rest. A good sauce should coat the back of a spoon; a proper bean dish should hold its shape when you spoon it up.
If it’s too thin, you simmered too fast. If it’s too thick, you didn’t taste as you went. The second taste is where the recipe becomes itself.
How a page gets onto this site
The notes get written down while the dish is still warm, before the flavors fade. The first draft is always messy—half recipe, half grocery list—because the real work is in the cutting. What stays is what worked, what didn’t, and why.
A page gets rewritten months later if someone sends me a better way to do it. That’s how you know it’s ready.
Write to me
I love hearing about the dishes you’ve fixed, the recipes you’ve ruined, or the flavors you can’t replicate. Did you add an extra spice? Let the sauce sit overnight? Tell me how you made it work—or how you’d make it better. The contact page is where to send it.
This site is for the cooks who know there’s always another way.
Warren
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Salads.