She's Not Sorry
Ratings6
Average rating3.8
15
Ratings6
Average rating3.8
An ICU nurse accidentally uncovers a patient’s frightening past in this chilling thriller from theNew York Timesbestselling author of Local Woman Missingand Just the Nicest Couple.
Meghan Michaels is trying to find balance between being a single mom to a teenage daughter and working as a full time nurse. While on duty at the hospital one day, a patient named Caitlin arrives in a coma with a traumatic brain injury, having jumped from a bridge and plunging over twenty feet to the train tracks below.
But when a witness comes forward with shocking details about the fall, it calls everything they know into question. Was Caitlin pushed and if so, by whom and why?
Meghan has always tried to stay emotionally detached from her patients, but this time, she mistakenly lets herself get too close until she’s deeply entangled in Caitlin’s and her family’s lives. Only when it’s too late, does she realize that she and her daughter could be the next victims.
Reviews with the most likes.
This book had too many side storylines going on, but yet was so boring at the same time. I looked up the ending and figured out one storyline Luke kidnapped Sienna and was on track to others Nat had more of a connection to Meghan than we thought. The twist of Caitlyn and Nat being the same person may have surprised me, but this was not compelling enough to keep reading
Slow, Problematic (Some Say Offensive) Main Character, Largely Forgettable. Yet Good Enough. This is a book where from an objective (ish) standpoint, there really isn't much if anything actually *wrong* about it. Yes, it is absolutely a slow burn - and yes, some people may prefer faster pacing, particularly in a "thriller". But that is taste, and the artist is allowed to do as they will there. The MC could be argued to be quite stupid or even downright evil by some, but there again - artistic license. Writing this review even 5 days after finishing the book (while having read 5 other books since, and with quite a bit going on in my own life at the moment, admittedly), I must confess that I barely remembered the book at all and only really picked up what it was when reading other reviews.
And yet, despite all of that... I *do* remember the book as enjoyable enough while I was reading it, and a good enough tale to be a worthy read for those looking for a solid enough mystery/ thriller. It won't be going on my personal "best of" lists any time soon, but it was also solid enough that I don't in any way feel I was cheated out the time I spent with the book. Obviously, other reviewers have had stronger reactions both directions and will continue to have so long as this book exists. But for *me*, it was ok and with nothing objectively (ish) wrong, therefore it gets a 5* rating, a decent enough review, and an encouragement from me to you, the reader of my review, to check out the blurb, maybe check out some reviews from other reviewers you trust not to spoil anything who may highly praise it - and others who highly despise it - and make your own call.
For me, I'm comfortable enough saying: Recommended.
Originally posted at bookanon.com.
