Why this site exists
You’ve got a pantry full of dried beans—black, pinto, lentils—but no idea how to turn them into something that doesn’t taste like boiled cardboard. Or maybe you’ve tried, and the texture is wrong, the flavor flat, the timing off.
The recipe said ‘simmer until tender,’ but your pot boiled dry before the beans even softened.
This site exists to fix that. Every recipe here starts with the beans themselves—what works with them, what doesn’t—and ends with a dish that actually tastes like the first green bite you remember, followed by the last savory whisper. No shortcuts, no assumptions about your pot or your stove.
Who writes this site
Emmett Marchetti writes this site.
Do you test every recipe more than once?
Yes. The first time is to get it right. The second is to make sure it doesn’t fall apart when you’re tired, when the beans are old, or when the stove hisses instead of hums. If it does, I cook it again.
What’s the one thing you still get wrong?
Timing. Even after years, I still underestimate how long beans need to soak—or overestimate how fast they’ll soften. The fix is always the same: taste them early, and don’t walk away.
Why no recipes for canned beans?
Because canned beans are a different problem. This site is for dried. If you want a recipe that starts with a dented can, there are plenty of others. Here, we start with the raw ones.
The first pot of beans I ever cooked was a failure—they split into mush, the broth turned bitter, and my roommate asked if I’d poisoned them. I ate them anyway. Now, I keep a jar of those beans in the freezer, just to remind myself.
How a recipe is built
A recipe here starts with a question: *What’s the one thing that always goes wrong with this?* The answer isn’t always obvious—sometimes it’s the soak, sometimes it’s the salt, sometimes it’s the heat. But every recipe begins by naming the problem before it happens.
The first test
The first batch is cooked exactly as written, with no shortcuts. If the beans turn out gummy, the broth weak, or the texture wrong, the recipe gets torn apart. Numbers are checked: minutes, ratios, temperatures. Then it’s rewritten—not to fix the mistake, but to prevent it.
The second test
The second time, the recipe is cooked with one deliberate flaw: old beans, a crowded pot, or a stove that won’t stay at temperature. If it still works, it’s ready. If not, it gets rewritten again. The goal isn’t perfection—it’s survival.
What we will not do
This site will not publish recipes that require rare ingredients, obscure techniques, or a kitchen you’d need to rent. No ‘deglazing with white wine’ when you’re feeding four people and only have beer. No ‘let it rest for 30 minutes’ when the table is set and the kids are hungry.
Things you will never find here
- Recipes that assume you own a mandoline, a food mill, or a pressure cooker you’ll use once.
- Dishes where the beans are an afterthought—like a salad where they’re just ‘added for color.’
- Instructions that say ‘adjust to taste’ without telling you what to adjust or how.
- Photos of food that looks nothing like what you’ll actually get.
Where to start
Start with the ‘Beginner’ section if you’ve never cooked dried beans before. If you’re looking for a specific dish, use the search—it’s sorted by what actually works, not just what sounds good. And if you can’t find what you came for, the contact page is where to ask.
Say hello
We like hearing about the beans you’ve tried, the dishes that worked, and the ones that didn’t. If you’ve got a question or a suggestion, the contact page is the place to leave it. No email address needed—just your words.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.