About Bread Recipes Board

What changed, and what it changed for you

When this started, it was a scrapbook of recipes I’d found online, some good, some terrible.

The notes were scribbled in the margins, the photos were stolen, and the only rule was ‘if it worked, it stayed.’ There was no structure, no way to find what you needed unless you already knew it was there.

Now it’s built to answer the question you ask when you’re in the middle of baking: *‘Why isn’t this rising?’* or *‘How do I fix this dough if I forgot the yeast?’* Every recipe has a ‘troubleshooting’ section, and the search knows the difference between a sourdough starter and a poolish.

The one that took years

The first version of the site had no way to track what worked. I’d test a recipe, write it up, and move on—no notes, no failures, just the ones that turned out.

That meant the site was full of ‘lucky’ recipes that wouldn’t repeat, and readers kept asking why their results never matched mine.

It stayed that way for two years because I didn’t want to slow down. Writing a recipe felt like the end of the process, not the start. But the complaints piled up, and I realized: if I didn’t document the mistakes, I was lying to everyone who trusted the site.

The fix was simple but brutal: I rewrote every recipe to include a ‘first attempt’ section—what went wrong, how I fixed it, and what to watch for.

That meant going back through hundreds of posts, but it also meant the site stopped being a museum of ‘perfect’ dishes and became a real workshop. Now, the ‘failed’ versions are just as valuable as the ones that worked.

Meet the author

I used to think recipes were like math problems: if you followed the steps exactly, the result was guaranteed. So I wrote them that way—no room for doubt, no room for the kitchen being too hot or the flour too old.

The first version of this site was a series of instructions, not a conversation.

I also believed that if a recipe didn’t work, it was the reader’s fault. I’d get emails like ‘Your sourdough didn’t rise,’ and my answer was always ‘Did you feed it enough?’—no patience, no second guess.

That changed the day a reader sent me a photo of their collapsed loaf and wrote, *‘I did everything you said.’* I realized I’d been treating cooking like a test, not a craft.

That was the hinge.

Now I write like I’m standing next to you in the kitchen. Every recipe includes a ‘what could go wrong’ section, and the comments are moderated to turn arguments into troubleshooting guides.

My name is Lamar Kessler, and this is where I test recipes until they’re reliable, then write them down so they’ll work for you too.

What did not change

The core rule is still the same: if a recipe doesn’t work three times in a row, it gets rewritten or removed. That’s how we’ve kept the site from becoming a graveyard of ‘almost’ good ideas.

The other thing that hasn’t changed is the focus on tradition *and* innovation. Some recipes are straight from my grandmother’s notebook; others are experiments with ancient grains or forgotten techniques. The line between the two isn’t important—what matters is that both are tested the same way.

What is still being fixed

Right now, we’re working on a ‘baking buddy’ system—pairing readers with similar skill levels to share real-time troubleshooting.

It’s slow because it requires new tools, but it’s the next step after ‘here’s what went wrong.’ If you’ve got ideas for how to make that work, or any other way to improve the site, the contact page is where to send them.