|
|
Therapist Directory: Find a Psychologist, Find a Therapist, Find a Marriage Counselor
PSYCHOLOGY TOPICS
Selected topics in psychology
and mental health.
|
|
|
|
|
THE THERAPIST PSYCHOLOGIST BOOK STORE
 | |
 View Larger |
How to Read a Novel: A User's Guide By John Sutherland ( St. Martin's Griffin )
Release Date: 2007-09-18
Average Customer Rating:
List Price: $12.95
Price: $11.01
Eligible for FREE Super Saver Shipping on orders over $25.
Availability: Usually ships in 24 hours
|  Add to Cart |
|
|
Product Description
“Do we still know how to read a novel?” John Sutherland, Chairman of the 2005 Booker Prize Committee, asks. His answer is an unequivocal, “No.” But Sutherland has not given up hope. With acerbic wit and intellect, he traces the history of what it used to mean to be well-read and tells readers what it still means today while reminding readers how the delicate charms of fiction can be at once wonderful and inspired and infuriating. On one level this is a book about novels but at a deeper level, this is a book in which one of the most intimate tête-à-têtes is described—one in which a reader meets a novel. However, in order for the relationship to take its proper course, a reader must know how to read it! Sutherland helps readers:
--Pick the right book for them among the cattle call of pre-packaged blurbs and enticing cover art--Recognize a misleading title at first glance--Look beyond the politics of book reviewers--Learn to read the extras—epigraphs, forewords, afterwords—to understand themes only hinted at in the main text--Find real aspects of the author cleverly hidden in the narrative structure--And much more
In a book that is as wry and humorous as it is learned and opinionated, John Sutherland tells you everything you always wanted to know about how to read fiction better than you do now (but, were afraid to ask).
|
|
 A waste of time ( cully )
This book is absolutely useless. I purchased it with the understanding that the author would enlighten me on how to better read fiction. The problem is that Sutherland never actually does that. He talks A LOT about how many books there are these days and how daunting a task it is to wade through them all. He discusses how choose a book, book titles, book covers, methods of finding books. But, he never writes a bit about how to READ a novel. Well, he may have written a bit about it, but only incidentally--seemingly as a mistake.
|
 Misleading Title; Tedious; Spoilers Throughout ( bluecombtiller )
I purchased "How to Read a Novel" believing that it was about how to read a novel. Rather, it's a tedious overview of "the novel's" history. Granted, I'm only 2/3 through, at page 163. But a glance at the upcoming chapter titles enlivens no new anticipation for me. Basically, every chapter can be outlined thus:
- Mention the subject (ex. "Should I write in my book?")
- Talk a little about the history (ex. Marginalia in publishing) - focus on impressing reader by throwing out ever name of every book possible, and insert horrible attempts at parenthetical wit that ruin the endings of so many "must reads."
- Conclude with obvious, no-brainer advice. (ex. "If you want to.")
This book has spoiled the endings of no less than three books that I have sitting on my reading queue shelf, and two that I was planning on buying, but now want to wait on in the hopes that I'll forget the endings he revealed.
Sutherland's writing is often awkward; he is no talent. This book is more like a reader's self indulgent "look what I've read" than an illuminating manual that will enrich your reading life.
That being said, if you are interested in the history of the novel (the physical bound form, reviews, author's choices of titles and pseudonyms, typography, etc) this is a hearty recommendation, if you are willing to cringe your way through a few spoilers that you'll regret. If you are interested in How to Read a Novel - how to enrich your experience and interact with a book - find something else.
The only two things I'm learning from this book are that I should REALLY learn how to STOP reading a bad book halfway and save myself the struggle and, if a book's blurb is written BY THE AUTHOR and says "This is a truly important book," know that it is a self-indulgent, ill-writ, mislabeled atrocity that couldn't get an adequate blurb from anyone else.
If you happen across the book, above the blurb, read the back cover's text, "How to Read an Endorsement," and tell me you don't crack up at the irony of the page. If you happen across the book, walk away.
|
 Devoted non-fiction reader is now fired up to read novels ( meritman )
When I head to the book store or library, I have always zipped right by the racks of new novels for the non-fiction section (where I picked up this book) -- but John Sutherland has so charmed me with his observations about the history and uses of fiction, that I will now be plunging into novels for the first time since college. He references no fewer than 400 notable works spanning hundreds of years in a mere 240 pages and includes illustrations of title pages and covers from many notable novels dating back to the 1719 edition of Robinson Crusoe. His passion for and intimate familiarity with so much great fiction is infectious.
|
"So many novels, so little time." ( booklover10 )
John Sutherland's splendid "How to Read a Novel" is a comprehensive guidebook to an art form that is very dear to my librarian's heart. Sutherland's credentials are impressive: he has taught Modern English Literature at University College London, served as the committee chairman for the 2005 Man Booker Prize, and writes for such prestigious publications as The Guardian and The London Review of Books. Sutherland's professed goal is to help overwhelmed book borrowers and purchasers make more informed choices than they would by merely browsing through their local library or bookstore.
The author is nothing if not thorough, covering everything from the history of the novel (its format has changed surprisingly little over time) to its many distinct parts, including the dust jacket, copyright page, title, epigraph, foreword, afterword, opening, conclusion, and even the font. How much stock should we put in blurbs that gushingly declare a suspense novel to be "taut and riveting"? Would we better off slavishly following the advice of some curmudgeonly critic who urges us to avoid the very same novel, since it is hackneyed and melodramatic tripe? Is an intimate knowledge of the cultural background and setting of a book indispensable to its appreciation? What role does genre play in a reader's enjoyment of a particular work of fiction? What factors go into making one book a bestseller and/or a literary prize winner while another is quickly forgotten and dumped into a store's remainder bin? Can movies and novels coexist comfortably or do cinematic adaptations inevitably destroy our enjoyment of the printed work on which the movie is based? Do novels have any lasting value beyond their ability to entertain us for a few hours?
The well-read, highly literate, and somewhat opinionated Sutherland brilliantly and amusingly answers these and other lively questions. Although I am a presumably knowledgeable librarian, the author's occasionally arcane prose had me checking the meaning of quite a few unfamiliar words and allusions (costive, belletristic, Zoilism, to name a few) that permeate this book. In addition, "How to Read a Novel" is geared more to a British than an American audience; the British cultural references may have some readers on my side of the Atlantic scratching their heads in bewilderment. I was none too pleased with Sutherland's derisive (although obviously tongue-in-cheek) attitude towards librarians. He tars us all with one brush as being narrow-minded fussbudgets. Shame on you, Mr. Sutherland!
However, these quibbles are offset by the author's exuberant love of reading and his understanding of what makes a novel addict come back time and time again for another fix. In "How to Read a Novel," John Sutherland takes us on a delightful and entertaining journey, citing numerous passages from such works as Zadie Smith's "On Beauty," Ian McEwen's "Saturday," Michael Cunningham's "The Hours," Salman Rushdie's "Shalimar the Clown," and J. M. Coetzee's "Disgrace" to illustrate his witty and thought-provoking comments. I suspect that many readers will be unable to resist looking at "How to Read a Novel" more than once, the better to absorb its nuances and appreciate its lively analysis of what makes novels so eternally beloved.
|
|
|
|
|
|
Addiction
