I wanted this to be a better book than it was. The writing was fairly decent and the characters were likeable enough, but it was justBook #12 of 2011
I wanted this to be a better book than it was. The writing was fairly decent and the characters were likeable enough, but it was just rather obvious to me who the bad guy was. Right from the start. And, I suppose that I could believe that the characters wouldn't suspect this individual, and if it hadn't been so obvious as a reader who it was, it would have been a better book. I mean, these kind of suspense books work a certain way, right? At some point, the reader is introduced to the bad guy. It’s never someone completely random. Anyway, I don't know what else to say without giving it away...
Other things that annoyed me... Bryan and Dawn decide to play amateur sleuths. Well, he's a cop (not a detective, a cop), so I guess the argument could be made that he's not exactly an amateur, but she is. And he's on the run from the law, so he's not really a professional at that point anyway. In fact, one of the reasons that she even came back (she'd run away from him 5 years prior) was because they used to be really good at playing amateur detective. Why not leave it to the real detectives anyway?
And then there was the whole thing about her leaving. That was OK in and of itself, except the two of them brought it up or thought about it every. other. minute. UGH!
And she left because she could see ghosts. And she didn't want to, so she left to run away from the gift/curse. Again, OK as a story set up... but then she apparently can't see ghosts anymore anyway. So it’s this whole bit part of the story that in the end doesn't seem all that important.
I wasn't entirely sure how much I'd like this book. I thought it'd probably be decent, but I was surprised how much I did like it. ItBook # 24 of 2010
I wasn't entirely sure how much I'd like this book. I thought it'd probably be decent, but I was surprised how much I did like it. It was a little jarring to be reading a book set in the future. I kept feeling like I was in one of the "Back to the Future" movies. Plus, the cover is at such odds with the future world Robb has built. Two aging Crown Vicotria's sitting outside of a precinct that looks like it's the setting of a "Law and Order" rerun?
I really liked Roarke. I don't know what it was, but as soon as he was introduced into the story, I found myself smiling. I know this is more a suspense series than a romance, but I do like the romance elements between Roarke and Eve. I also liked how there was no angst about them being together. I mean, sure there was some hesitations, but none of the over top angst that kind of grates on my nerves.
I didn't intend to finish this as quickly as I did, but there ya go. Can't wait to move on to the next ones...
Loved this book the second time around too. I have a feeling I will probably read the entire series again at some point... but with 31 books (and counting, as far as I know), I'll probably be kept busy for awhile......more
I didn't actually like this book so much. It was an OK listen, but not my favorite. I think what I didn't like about it was thatAudio Book #5 of 2009
I didn't actually like this book so much. It was an OK listen, but not my favorite. I think what I didn't like about it was that the computer references seemed dated, which made the whole thing seem dated. ...more
This was an OK book. The beginning was a little slow and then it picked up about 1/4 of the way into it. My main problem with it was tBook #61 of 2009
This was an OK book. The beginning was a little slow and then it picked up about 1/4 of the way into it. My main problem with it was that the "explanations" such as they were came from long dialogues from one of the main characters. This was alright for some of the background information, but annoyed me when this device was used to explain the ending and the whole "secret" they'd been trying to recover/hide (depending on the character). I mean, three people had read this supposedly damning document and instead of describing the secret via the reading of the document, someone was brought in to describe the whole thing... and then, it just ended. Eh. It was alright....more
I'd say this was more thriller than romance as Kristi Bentz and her old boyfriend - now her professor - search for the reasons whAudio Book #4 of 2009
I'd say this was more thriller than romance as Kristi Bentz and her old boyfriend - now her professor - search for the reasons why four women went missing from Kristi's small college campus.
The main problem I had with this book is... where exactly does Kristi get off investigating the disappearance of these woman? She's in no way involved, not a member of any police agency (although her father/boyfriend Jay are), not a private eye, not a government agent. Do regular people really just go up to someone and say, "So, professor so and so, what do you know about the disappearance of your student?"
It was an okay listen, at times it felt a bit like it dragged on. But it did keep me engaged, wondering what would happen next.
Wow, it seems like it took me all of May to read this book. It was a decent book. Lots of buried family secrets and intrigue. I becamBook # 53 of 2009
Wow, it seems like it took me all of May to read this book. It was a decent book. Lots of buried family secrets and intrigue. I became interested in this book after listening to "Blue Smoke and Murder" which was the fourth in a line of St. Kilda Consulting series - this was supposed to be the first. Although St. Kilda was mentioned (especially in the last 1/4 of the book), it left me more confused about the whole St. Kilda series timeline. There's no description of how this organization started. And compared to the roll it played in "Blue Smoke and Murder", the organization might as well have been non-existent here. But despite those issues, which I wouldn't have even noticed if I hadn't started the series at the end, it was a decent book on its own. I had to reread through the ending just to make sure I understood where all the twists came out and I still think there's one I'm not following, but that's alright....more
I liked this much better than "Always Time to Die". I just followed it better I think, and there was more action and a whole lot moreBook #54 of 2009
I liked this much better than "Always Time to Die". I just followed it better I think, and there was more action and a whole lot more of St. Kilda Consulting. Finally, FINALLY, I get the backstory on Joe Faroe, Lane, and Judge Grace Silva! ...more
Whenever I drive to Mansfield, we pass this place called Salamanca in NY. It is usually late at night and maybe it is the perfect spotBook #9 of 2013
Whenever I drive to Mansfield, we pass this place called Salamanca in NY. It is usually late at night and maybe it is the perfect spot on the highway because we often stop to fill up the gas tank or to grab a road snack. It also happens to have a casino, always lit up just off the highway (and I think is owned by an Indian/Native American tribe?) Anyway, it might be the combination of the casino scenes in this book (where the casino seems to also be in the middle of nowhere) and the fact that I first listened to this book on the way to Mansfield, but whenever I go home and pass Salamanca, I think of this book. So, I finally decided to read it again. It was still a pretty good book. I have a feeling I might pick it up again in another few years.
Original 4/12/2009 Audio Book #2 of 2009
Listened to this on my way to Mansfield and back and I very much enjoyed it. It was more thriller than romance, and that's okay, good even since Ron was listening to it as well. As a matter of fact, we disagree on how exactly the book should be categorized, he doesn't think it's a romance, I say that although the romance may be secondary to the plot, it's still considered a romance.
While listening to the book, I got the feeling that there was more to the St. Kilda (the private security firm the MC hires) story than is let on within the book itself, and a glance at the author's website confirms this. There are a few other books in this series before this one, which I'm not interested in reading.
Ironically, while perusing the books at Wal Mart in Mansfield (because I clearly NEEDED more books with me in Mansfield...) I saw this on the shelf. I almost wish I would have actually read the book, I think that would have at least helped me figure out the timeline of the plot, each chapter began with a date and place and usually it didn't mean a whole lot to me because it's not like I could go back and check how much time had passed from the previous chapter, but that's only a minor complaint, one inherent to listening rather than reading.
Book #12 of 2009 That was surprisingly engaging, even if it took me forever to finish it. The book basically revolves around the main character tryingBook #12 of 2009 That was surprisingly engaging, even if it took me forever to finish it. The book basically revolves around the main character trying to figure out what really happened eight years ago when he was grazed by a stray bullet, disfiguring him for life. There was enough action and twists to keep me engaged, but some of the pieces seem like loose ends. For example, one of the characters goes to a former collegue for help figuring a code out. Although this former collegue cracks the code, and we read about it because the narration is focused on him briefly, NO OTHER CHARACTERS EVER FIND OUT. Why not just introduce the information a different way? Which brings me to my biggest complaint, there was too much switching back and forth between characters. Chapters were often only two pages long. I felt like I was reading the equivalent of a cliffhanger at the beginning of a commercial break, complete with suspensful music, at the end of EVERY chapter. It got old after awhile. I'm also not sure that I was a huge fan of the ending, vague though it was, although on the other hand, the ending was fitting.