Instruct: Classify Amazon reviews into positive or negative sentiment
Query: Little new information...

Chances are, anyone who's reading this book is on or has been on the very "Death March" projects it describes; I know I have.As such, the book reads not so much like new information, but rather like a conversation around the watercooler. "Should have bailed on that project," "Try to get all the 'must have' functions complete," etc.The upshot: While this book is affirming of the ad hoc insights all developers make as we go along, nothing's particularly revolutionary here. If you've survived one "Death March", you have these lessons hardwired into your brain:1) Understand the politics of your organization2) Don't use risky, not-ready-for-primetime technologies3) Prioritize your function and drop fluff as necessary to meet your targets.4) If all else fails, quit. That'll teach 'em.Overall, there are some valuable insights, but I wouldn't waste my money.