Read about 70% of dreaming in code.  Kind of dry if you ask me.  You get all of these stories about the history of software but rarely get a glimpse of talk about Chandler.  And even when you get to talk about Chandler, it really isnt that interesting.

Software isn't the interesting.

It's a pretty decent book... as long as you like abrupt endings.

"Gee, these guys are going nowhere fast, and my publisher is asking when my book will be done..."

But it is a good commentary on the state of the industry, and how it's really really really hard to deliver a product on time and on budget.  I lent my copy to one of the managers at work.

What about the history about everything in software?  And the way we are suddenly given a history lesson.

It's written for a general audience, so not everyone has had the experiences that we've had with the industry.

Actually, reading it was sort of depressing.
How *can* we do something different that will help us succeed if all these really smart people who GTD aren't able to do it, even with schedule pressures removed?

> these really smart people

Because it's not just about being really smart. So if you get that, you can still succeed. It's the arrogance of IQ that stops people from seeing they aren't a force of nature that can create from will alone.