Showing posts with label DNF. Show all posts
Showing posts with label DNF. Show all posts

DNF: Quest for the Cure by Brent R. Stockwell

Saturday, June 11, 2011

Apparently, I'm making a pattern of "do not finish" books. (According to my clinical instructor, once is a mistake, twice is a pattern). I don't think I am going to have a DNF post every week. However, I do think I am more likely to leave a book unfinished these days, because as I'm becoming immersed in nursing school, I have less time to read. I want to spend the time I have reading something I enjoy, not forcing myself to read something I don't enjoy. I'm not going to give up on every book I struggle with, but I don't have many regrets about this one. Here's the breakdown:

Why I quit:
* The book was dry as can be, with long stretches reading like a textbook. Textbooks have their place, and there have been many textbooks that I loved. However, in a mainstream nonfiction book, I am looking for something a little more readable.
* The book was extremely technical but also dumbed down, if that makes sense. Many of the processes being described in extreme, simple detail were processes I already knew from my first degree. This isn't an intrinsic fault of the book and is probably very helpful for those who are starting from scratch in their learning about drug development, but for me, it was very painful.
* The book had some propaganda elements that bothered me. In the first few pages, the author made a statement stating that because drug development is slowing down due to the lack of proteins able to interact with drugs, we are all essentially doomed to die long painful deaths of terminal illnesses. Yes, there is no cure for cancer, and yes, it is a terrible thing. However, just because some illnesses are not yet cured does not mean that as a race we are going to die out in misery. A lot of progress has been made, and there is room for more.
* The author also made statements about many of the scientists he worked with that did not quite flow with the book. He would be describing an experiment and then make some statements about the scientist along the lines of, "He's a great guy. He called me once, and we did an experiment together. Then he died of cancer." I think the author was trying to make the book less dense, but when there wasn't a direct point to his comments on the scientists, they seemed a bit random.

Why it was hard to stop:
* This is a review book that I requested from NetGalley. I've never outright decided not to read a book I have from NetGalley, and the guilt is consuming *ashamed face*.
* I really am interested in drug development. My father has worked for drug companies for most of my life, and I almost went into pharmacy instead of nursing. I was sad that this book and I didn't mesh.
* There were some very interesting facts presented in this book - interesting enough that I think I may pick it up again some day in the future. I just didn't enjoy wading through the explanations of how proteins were made.

Who this book might work for:
I have a feeling that heading is awkward. However, I lack the energy to grammatically save it.
* If you are curious about drug development and haven't studied molecular processes in great detail, these explanations should really help you. They are written in layman's terms and explained very slowly and carefully. I do think it would be very clear in helping someone unfamiliar with the Central Dogma to understand the basics of molecular biology and how they relate to drug development.

Hopefully this is my last DNF in a while. And I'm curious, do you ever DNF review books? Do you feel consumed by guilt like me?

DNF: Water for Elephants by Sarah Gruen

Saturday, June 04, 2011

I read somewhere, on some blog (sorry that I can't remember who you are) that there are, in general, two types of readers - those who will put down a book relatively quickly if they are not enjoying it and those who stubbornly make it through every book because they will finish it. I am definitely, definitely, the second type. Once I start a book, I find it unbearable to not know what happens in the end to the characters. It nags at me to leave a book unfinished.

However, there are too many good books in the world to read the ones I don't like, so I am trying to do better with my little "problem." I don't think I could write a fair review of a book I did not finish, but I do like to process a bit, so from now on this will be a feature that pops up every so often. So here we go...

Why I didn't finish:
* More than anything, the sex. I am not a reader that will set a book down at the first allusion to sex, but I do prefer things to be on the cleaner side - rated PG-13, at most. This book had vivid descriptions of what went on in a stripper's tent and what was hidden under one pervy little character's pillow, if you know what I mean. I didn't even get to anything between characters before I felt too disturbed to continue.
* While this alone wouldn't have kept me from finishing the book, the present tense first person does get old.
* I wasn't dying to know what happened to the characters, because I already knew. So much was revealed in the first few chapters that I didn't feel a drive to find out more about the characters. I am sure there were significant events I didn't get to, but it seemed as if the climax had already been given away.

Why it was hard to stop:
* Mainly, the hype. I'd heard so much about how this book was epically romantic and such a compelling story. Nobody wants to stop reading a book they pick it up - the reason we pick up books is because we want to be delighted and swept away in a new story. I hoped for this with this book, but it didn't happen for me.
* I bought it for my Kindle, meaning that there is no way I can send it back or swap it. To me, this is the one drawback of an e-reader.

I've heard the movie is better than the book. Does anyone recommend it (with the knowledge that I didn't care for the book)?
Related Posts Plugin for WordPress, Blogger...