I have no affiliation to the book or the company, I just really enjoyed reading it :]
It seems like something I've seen before; but then again, I'm not completely sure. I looked at a few bits and pieces of the book; certainly seems interesting. As a software developer who's been in the profession for almost 20 years now, some of the suggestions and attitude in it feel "wrong" to me. A lot of that, though, has to do with the fact that when I started professional software development, the concept of "open source" was in its infancy for the most part. Concepts like "agile development" was simply doing things "quick and dirty" and "damn future maintenance needs". I guess in a way, I'm a little set in my ways, but I am always willing to try something new!
Part of the description that leads off my resume says
I know how to "hack", and how to "engineer", and when to do each.
They don't.
Their basic attitude is one of the biggest reasons that there's so much junk software around today. In fact, it exemplifies much of what's wrong with the U.S. in a lot of areas.
I think it's telling that, when I browsed the introductory "What is Getting Real?", my browser got stuck in an endless download, fetching $DEITY-knows-what from google-analytics.com, and had to be manually interrupted.