Skip to main content

When is a book worth reading from start to finish?

I decided to rework this old essay from my original 52 books blog and re-post it, because this subject seems to be on people’s minds right now, at least considering how many of the book bloggers whose blogs I regularly visit have written about it in the last couple of months.

Everyone has different criteria for deciding if a book is worth finishing.
Some will read any book to the end, slogging through piles of tripe or suffering endless boredom just so they can say they have read it. Several people I know of did this with The DaVinci Code and/or The Name of the Rose. (Please note that I am not belittling either book. It just so happens that many people think the former is tripe and the latter is boring).
Others will give it a couple of chapters (or 50 pages or so in the case of “chapterless” books like those of Terry Pratchett) before deciding.
Still others will read the reviews, read the blurb, skim the book and read the ending, and then decide they’re not interested.
Each method has its merits.

As for myself, I have occasionally finished badly written books because the story or concept was interesting in spite of the bad writing, or there was something I just had to find out (usually the resolution, but sometimes some small detail). More often, I will just stop reading.

If a writer's style annoys me, I stop reading if it continues to annoy after I have read about 20-25% of the pages. This means about 50 pages of an average length novel. One example is Elizabeth Peters. I started reading one of her Amelia Peabody mysteries and found the style very annoying, so I stopped reading. However, I tried again and loved both of the books in the series that I have read so far.

If a book is dull but well written, I give it about 100 pages, because some stories start very slowly, especially long novels that need to explain a lot of background before the actual story starts. If it has not picked up by then, I stop reading (unless the book was recommended by a reliable reader, in which case I may read another 100 pages). This happens mostly with long novels and non-fiction, especially travel books.

Sometimes I come across books that tell a good story and are, for the most part, well written, but there is something missing, some spark or soul that would make an average book into a good one and a great one into a masterpiece. Those I usually finish. The Secret Life of Bees by Sue Monk Kidd and The Eyre Affair by Jasper Fforde are good examples.

Sometimes books are spoiled for me by other books. Those I put aside to read at a later time when I have forgotten the book that did the spoiling. I stopped reading Gail Anderson-Dargatz's book The Cure for Death by Lightning because I had recently read The Secret Life of Bees, had not liked it much, and found too many similarities in the first chapter of Cure (both are about girls from dysfunctional families). I am assured by people who have read both that Cure... is far superior to Bees..., but I need to distance myself before I can enjoy it.

I am always ready to give authors whose books I have not liked in the past a second chance, and have usually not regretted it. Even the best of writers sometimes write bad books.

Comments

George said…
I'm in the "read 50 pages and decide" camp. If a book can't engage me in 50 pages, then it's time to move on to another book. That being said, I've tried to read Proust's IN SEARCH OF LOST TIME three times. I know it's a classic, but maybe the translation is turning me off. I have the Lydia Davis translation of SWANN'S WAY so that might make the difference on my next attempt.
I just have to ask. Surely you are a librarian? If not "officially", then you are certainly one at heart. Or, if not, would you be one in another life?
Your pal, a librarian.
Bibliophile said…
Rose, I am not a librarian, but it is a career I seriously considered when I was choosing a subject at university. I have sometimes wondered what would have happened if I had.

Popular posts from this blog

How to make a simple origami bookmark

Here are some instructions on how to make a simple origami (paper folding) bookmark: Take a square of paper. It can be patterned origami paper, gift paper or even office paper, just as long as it’s easy to fold. The square should not be much bigger than 10 cm/4 inches across, unless you intend to use the mark for a big book. The images show what the paper should look like after you follow each step of the instructions. The two sides of the paper are shown in different colours to make things easier, and the edges and fold lines are shown as black lines. Fold the paper in half diagonally (corner to corner), and then unfold. Repeat with the other two corners. This is to find the middle and to make the rest of the folding easier. If the paper is thick or stiff it can help to reverse the folds. Fold three of the corners in so that they meet in the middle. You now have a piece of paper resembling an open envelope. For the next two steps, ignore the flap. Fold the square diagonally in two. Yo...

Book 40: The Martian by Andy Weir, audiobook read by Wil Wheaton

Note : This will be a general scattershot discussion about my thoughts on the book and the movie, and not a cohesive review. When movies are based on books I am interested in reading but haven't yet read, I generally wait to read the book until I have seen the movie, but when a movie is made based on a book I have already read, I try to abstain from rereading the book until I have seen the movie. The reason is simple: I am one of those people who can be reduced to near-incoherent rage when a movie severely alters the perfectly good story line of a beloved book, changes the ending beyond recognition or adds unnecessarily to the story ( The Hobbit , anyone?) without any apparent reason. I don't mind omissions of unnecessary parts so much (I did not, for example, become enraged to find Tom Bombadil missing from The Lord of the Rings ), because one expects that - movies based on books would be TV-series long if they tried to include everything, so the material must be pared down ...

Bibliophile discusses Van Dine’s rules for writing detective stories

Writers have been putting down advice for wannabe writers for centuries, about everything from how to captivate readers to how to build a story and write believable characters to getting published. The mystery genre has had its fair share, and one of the best known advisory essays is mystery writer’s S.S. Van Dine’s 1928 piece “Twenty rules for writing detective stories.” I mentioned in one of my reviews that I might write about these rules. Well, I finally gave myself the time to do it. First comes the rule (condensed), then what I think about it. Here are the Rules as Van Dine wrote them . (Incidentally, check out the rest of this excellent mystery reader’s resource: Gaslight ) The rules are meant to apply to whodunnit amateur detective fiction, but the main ones can be applied to police and P.I. fiction as well. I will discuss them mostly in this context, but will also mention genres where the rules don’t apply and authors who have successfully and unsuccessfully broken the rules. 1...