|
Summer Reading
Browse the best books of summer including blockbusters, beach reads, and editors' picks in our Summer Reading Store. |
Product Details
Would you like to update product info or give feedback on images? |
At exactly page 146, I felt like I was reading a different book. Unfortunately, it was a book that I did not enjoy nearly as much as the first 145 pages. From this point onward, Mr. Barr felt the need to write a long drawn out essay about the history of the computer industry peppered with comments about how it affected Microsoft.
I have read this history countless other times in books much more entertaining and comprehensive (i.e. Fire in the Valley) than this book.
The author supposedly worked on two different versions of Windows NT and Windows 2000, but there was no talk whatsoever of what it was like to work on those teams. I definitely expected more information about what specifically went on inside Microsoft (from an insider's point of view) rather than Microsoft's relation to the industry which is public knowledge.
The book is in four parts. The first is a look at MSFT hiring and interview processes, which is followed by a description of his time at Softimage (which includes a brilliant dissection of type-1 through type-4 demos), then a long and meandering recounting of his early involvement with computers and then an equally meandering final part which is a compilation of his observations about MSFT and the industry in general. I found the first two interesting enough to read, but found the final two not as compelling. He completely mis-understands the point about middleware and Java (see Lou Gerstner's book "Who said elephants can't dance?" for a different definition of middleware and business strategy). Perhaps his narrow, unappealing and unfocussed second half meanders so much because he didn't take his chances to widen his own career within MSFT as a manager or PM.
Like Adam with his interviewees, I agonized over whether or not I should give this book a "four" or a "three" star rating :). Ultimately, I had to go with the lower rating because as a developer, I was hoping to read about what "he" had actually "learnt as a developer" when I picked up the book. Unfortunately, while he talks about a whole lot of things (such as the importance of testing for product quality, and the importance of programmers getting a 'life' as they mature, the contributions of MSFT to the open source movement, etc. etc.) he doesn't at all talk about what he worked on, what was exciting and new about NT code he may have contributed to, or how methodologies and practices changed while he was there. Maybe MSFT prevents people from talking about such stuff, but by cutting out such professionally interesting bits, the book becomes a "missed opportunity" (esp. since Adam is a self described "systems guy"). Perhaps he really was writing only for the non-programmer crowd (but I doubt it).
For me, it was a bummer, too much ado about hiring practices, and the author does not escape his bias after having worked for Microsoft 10... Read more
First hand accounts of intereviewing and recruiting. Read more