Breaking Dawn

Categories: Book Reviews
Tags:
Comments: 1 Comment
Published on: April 2, 2010

Finally I have made it through the agony of this series of books.  This one took longer to finally get around to due to the foul taste left by Book 3.  I do have to say that I am mildly surprised by the book and found it considerably more entertaining and worthwhile than the rest of the series combined.

The book ended on a completely happy ending with some sappiness – but that is expected from knowing the rest of the books and story.  This book had a lot less predictability than the prior novels which tells me that the author has learned a thing or two about writing since starting her career.  The end result though was completely predictable and the imprinting was also a no-brainer without any twist.

The story was a lot less sappy – once you got past the honeymoon.  I do wish that a whole lot more was divulged to Charlie about the situation but can conceded the author point of view on it.

I enjoyed this book and find it to be on a much higher par level.  This one was written more for the general public and not just your teeny bopper girl cross-section.

Overall Grade B – worth reading.

1 Comment - Leave a comment
  1. […] This post was mentioned on Twitter by Jason Brimhall. Jason Brimhall said: New post: Breaking Dawn (http://bit.ly/9RXi7s) […]

Leave a comment

Your email address will not be published. Required fields are marked *










Calendar
April 2010
M T W T F S S
« Mar   May »
 1234
567891011
12131415161718
19202122232425
2627282930  
Content
SQLHelp

SQLHelp

  • @Ko_Ver: @NickyvV no, no special tricks in the package :) #sqlhelp
  • @NickyvV: @Ko_Ver I've seen that last week that the Job (step) succeeded, but it actually failed with an error #sqlhelp
  • @NickyvV: @Ko_Ver Is FailParentOnFailure set to false on a task/container maybe? #sqlhelp
  • @Ko_Ver: When I start an Agent job, the "job running" pop-up says there's an error. But SSIS catalog and Agent history says jobs succeed. #sqlhelp
  • @DbaMayor: #sqlhelp I'm seeing LCK_M_U and LCK_M_RS_U waits on sec readonly replica with only reporting queries...anyone faced similar issue?..thnks
  • @TrustMeImADBA: Prob not a good question for #sqlhelp but what is the chances time-service changing the time 23 sec forward made my sql cluster failover?
  • @zippy1981: Seem to be that I need to install SSMS vNext Verifying now #sqlhelp
  • @ChrisAdkin8: @YaHoznaDBA you should also compare avg writelog waits to avg tran log write stall,the two are not necessarily foced to be the same #sqlhelp
  • @toddkleinhans: #sqlhelp Will try using lock priority. Totally forgot about that. Thanks!
  • @DBArgenis: @toddkleinhans Compatibility mode is for T-SQL constructs and Query Optimization, nothing else. #sqlhelp

Welcome , today is Tuesday, February 21, 2017