The things we got wrong
This isn’t a list of what we do right. It’s a log of what we got wrong—mistakes that stuck, methods that failed, and the fixes that came too late.
The reader gets to see how we spot our own errors, which is how you judge whether the rest of the work is honest.
Most sites hide their failures. We publish them because the only way to trust a recipe is to know when it’s been tested, retested, and fixed. If you can’t find a mistake here, you’ve missed the point.
Three we had to fix
These are the three biggest errors that made it into the site before we caught them. Each one changed how we work—and how you can trust what’s here.
The salad that never wilted
- 1A recipe with no sour cream
The classic ‘Crispy Kale Salad’ promised a tangy dressing with sour cream—but the original photo showed a smooth, creamy sauce with no lumps. The dressing was supposed to be mayo-based, but the first dozen readers flagged it as ‘too rich.’ Desmond Schuster noticed when a reader emailed about the mismatch between the text and the image. It had been live for six weeks before we pulled it.
- 2The baking time that lied
The ‘Honey-Glazed Roasted Carrots’ called for 25 minutes at 400°F, but every test batch burned by 20. The original author swore by the time, but the notes in the draft said ‘watch after 15.’ Desmond Schuster dug through old emails and found the real method was 18 minutes, not 25. The page stayed up for three weeks with the wrong time before we corrected it.
- 3The ingredient that wasn’t there
The ‘Spicy Avocado Salsa’ listed jalapeños as optional, but the photo showed sliced serranos instead. No one caught it until a reader asked why their salsa lacked heat. Desmond Schuster verified the original recipe card: serranos were the correct pepper, but the text never updated. We fixed it within 48 hours—but the damage was done.
What those three changed
These mistakes taught us three things: never trust a photo over a draft, always double-check ingredient lists, and publish corrections faster than excuses.
Rules that came from mistakes
- 1. Photo vs. text must match (from *The salad that never wilted*): Every recipe photo gets a second review by Desmond Schuster before publishing.
- 2. Baking times need a margin (from *The baking time that lied*): All roasted recipes now include a ‘start checking at’ note in the text.
- 3. Optional ingredients must be optional (from *The ingredient that wasn’t there*): The site now flags ‘optional’ items with a warning: ‘If omitted, flavor changes.’
The people behind this
Desmond Schuster is the founder and editor of *Salad Recipes Garden*, and the one who still flinches when a reader points out a typo. You’ve just seen them fix mistakes—because that’s how you meet someone who cares about getting things right.
Keeping a log like this isn’t easy. It means admitting when you were wrong in public, and that’s uncomfortable. But the alternative—pretending you never make mistakes—is worse. Desmond Schuster writes this list because they’d rather be honest than perfect.
There’s a smaller mistake that never made the log: the first batch of ‘Lemon-Herb Dressing’ turned out bitter because the lemons were overripe. Desmond Schuster tossed it, made a new one, and never wrote about it—because some failures stay in the kitchen.
If you find another mistake, the contact page is where to tell us. No shame, no lecture—just a fix, and maybe a note in the next log.
There will be a next one
This list isn’t finished. The next mistake might be in the next recipe you read, or the one after that. If you spot it, say something. The contact page is open for corrections—and for the people who help us keep this honest.
The recipes are grouped by category: Appetizers, Beverages, Breakfast & Brunch, Desserts, Main Courses and Reviews.