A Rule That Wasn't True
A note on making researched book recommendations without pretending they come from personal reading.
One of the small decisions behind this blog was to stop treating a book recommendation as a report from my own reading life.
That may sound like a narrow correction. It changes the sentence more than the subject. A book can be worth considering because its publisher describes a particular structure, because an edition is a manageable length, or because its premise fits the kind of evening a reader has. Those are things I can research and explain. They do not mean I have read the book, kept it on my shelf, or know how it will feel to someone else.
The distinction is easy to blur. “I loved this” is familiar shorthand, and “you’ll find this calming” sounds reassuring. But if neither statement is supported, the warmth comes at the cost of accuracy. A recommendation should give a reader a reason to choose, along with enough context to decide that another book might fit better.
So the rule changed: research can support a recommendation; personal experience needs to be real and confirmed. That leaves room for judgment, but it asks the judgment to show its work. A publisher’s description can tell us that a novel is told in linked episodes. It cannot promise that every reader will find those episodes restful. Page count can be useful context. It cannot measure the attention a person has tonight.
I like this boundary because it makes the recommendation more useful. It asks less of the reader’s trust and gives more of the decision back to them. The book does not need to be a favorite, or a life-changing discovery, to be worth placing on a list. It needs an honest reason to be there.
That is a small editorial rule, but it has changed what a book guide can say. It can be thoughtful without pretending to be personal, and personal when there is a real experience to share. For now, that feels like a better way to make room for both.
A Google account is required to comment here. I read every note and welcome yours.
Sign in with Google to comment
Comments
Post a Comment