Recipe Reviews Should Begin With What You Changed
FoodI once read a one-star review of a lemon cake from someone who had removed the lemon.
The reviewer had also reduced the sugar, replaced the butter and used a pan of a different size. The cake was described as bland and dry. This was delivered as a warning about the recipe.
I laughed, then remembered the pasta dish I had recently blamed for being too salty after substituting broth for water and adding the full amount of salt anyway.
Home cooks change recipes for sensible reasons. Ingredients are missing. Budgets are real. A person dislikes cilantro, owns only one baking dish or discovers too late that the milk is gone. Substitution is not disrespect; it is how dinner survives contact with a kitchen.
The problem begins when the review hides the change until the final sentence—or never mentions it at all. A rating appears to describe the published recipe while actually describing an experiment performed beside it.
I would like recipe comments to begin with a short disclosure: made as written, or changed. If changed, name the changes before the verdict. “Used chicken broth instead of water; result was too salty” is useful. It warns the next person about that choice. “Too salty, would never make again” sends everyone looking for a flaw that may not exist in the original.
This does not mean a recipe becomes immune to criticism whenever anyone adapts it. A good recipe can anticipate common substitutions or explain which parts are structural. Instructions can be unclear. Timings can fail across ordinary equipment. Sometimes a change reveals that the recipe is less flexible than readers need it to be.
Reviews also serve more than one audience. The author wants to know whether the written method works. Future cooks want to know whether a swap worked. Both kinds of information are valuable if they are labeled honestly.
The same rule should apply to praise. “Amazing!” is less informative if the reviewer doubled the cheese, added bacon and finished everything under the broiler. That may be an excellent variation, but the original recipe should not receive mysterious credit for ingredients it never contained.
I do not want a courtroom attached to every weeknight dinner. Nobody needs to file a complete substitution log before saying they enjoyed soup. I want the causal humility of admitting that once we change the method, we are reviewing both the recipe and our decisions.
What is the most useful way to describe a substitution: list every change, mention only the structural ones or simply say whether you followed the recipe as written?