Review: Wait....what?!?!
Rating: 2 out of 5
Date: 09 25, 2013
I feel like I just read two separate books....The first half was incredible. I started Addicted to Him at 9pm a few nights ago and quickly got sucked in by the author's gripping story of a scared, unloved teenage girl who had to diminish her physical beauty just to keep her lecherous stepfather at bay.  The story was so enthralling that I could not put it down. I wound up staying awake until after midnight, until I was reading with one eye open and actually falling asleep, because I kept turning page after page. I finally gave in to exhaustion at 50%.The next day all I could think about was picking my Kindle back up after my two children went to sleep, but when I finally got to continue the story, I felt like I picked up an entirely different book. It happened that quickly, at exactly 50% into the book. The turmoil over Cassidy's mother and stepfather was almost all but forgotten and it was replaced by insta-love with a guy that quite frankly did not sound appealing, and a ton of insta-sex. I like a steamy romance as much as the next person, but the amount of sex in this book was completely unnecessary. And it just got worse from there when the author introduced a bunch of subplots that had nothing to do with the original premise, and our brave, tough-as-steel heroine turned into a spineless doormat. I HATED the second half of this book. There were a ton of inconsistencies in ages and details, and I just could not get over how the author let her lead character pine away for such an a**hole!!***POSSIBLE SPOILERS***Is it okay to let a guy hit you and verbally berate you, then chalk it up to the fact that you are addicted to having sex with him? Really, in the year 2013, why would anyone write a story that sets girls back 20 years?!? How about the part where she has sex with him right after finding out he just had sex with someone else five minutes beforehand? Was that a joke?I give Addicted to Him a generous 2.5 stars only because the first half was so good!