In Search Of Stupidity – A Review

In Search Of Stupidy, written by Rick Chapman, covers the mighty stupid blunders of high-tech companies from the early 80s right up to 2003, when the book was published.

To be worthy of mention in this book, it took the combined efforts of personnel in upper management, development, sales, and marketing, all fiercely dedicated to ignoring common sense, the blatantly obvious, and the lessons of the past. Major failure doesn’t just happen: To achieve it, everyone must pull together as a team. [Afterword, p223]

It covers a time in computer industry of which I am only dimly aware. I didn’t really get into computers until Windows 98 Second Edtion. There were no other spreadsheets but Excel; no word processors but Word. Microsoft was so firmly entrenched that it was  cool to disparage them.

So reading this book was a delight. It showed that Microsoft had some help from others’ stupidity to get where they are now. It also covers Microsoft’s stupid arrogance that sparked the antitrust suit. The stories are told in a light, conversational tone; Chapman isn’t afraid to call a spade a spade, either. Major idiocy is pointed out on a regular basis in the book.

I also learned a lot about some marketing concepts that I always sneered at such as branding. Chapman explains the power of branding and shows no one really understands how to go about “building a brand.”

Recommended.

The Automatic Millionaire

At the recommendation of the Wealthy Blogger, I bought the Automatic Millionaire by David Bach (US, Canada), and read it off and on for the past few weekends. It’s not very long but I just didn’t have attention span to finish it all at once. I blame TV.

Seriously, that usually means that the writing isn’t very interesting. That isn’t really true for this book, though. Even though the advice seems simple, I learned a lot about managing money from the book. My parents weren’t very good teachers when it came to money, so a lot of it was new to me. Essentially, Bach says Pay Yourself First and Make It Automatic! I might owe him a few bucks mentioning that, since he repeats those phrases so often I suspect they’re trademarked. He has a few other pointers, but it’s mostly centered around making it all automatic so even those who suck at saving can do it.

So what was the problem? I think it was the repetition. Pay Yourself First! Make It Automatic! Every chapter. Gawd! If he was on TV, it would have be very informercially (that’s the technical term). Now that I consider it, the text is very conversational, almost as if he transcribed one of his seminars. The repetitive catch phrases would probably work if I saw him live, but as book, it doesn’t really work. Granted, a literary masterpiece should not be sought in personal finance; the advice, the important part, is very good and essential if you suck at saving or charge everything on the plastic. Recommended.

P.S. Yay! 100th post. A significant milestone since I suck at posting frequently. More significant than a year blogging, which passed last week.

Computer Books Every .NET Programmer Should Own

Given my natural distaste for Computer Books, and my penchant for lists, here are my picks for Computer Books That Don’t Suck (.NET Version):

You may notice that almost all of these books are written by authors who blog. (Whether the blog or book came first is another, irrelevant discussion.)

The two books that get my absolute, trapped-on-a-desert-island recommendation are Joel On Software and Coder To Developer. I was unable to put down either of those books until they were finished. And then I wanted more of that. Interestingly, the last two books on the list are the least coupled with .NET.

This list will expand. Do you have any books you simply cannot do without?

Computer Books Mostly Suck

Chris Sells is asking his Windows Forms Programming Readership what he should do about the 2nd edition.

It got me thinking about what I like and dislike about technology books. I remember, when I first started out in Computer Science (~2001), walking into the computer section at my local giant bookstore, looking for books about how to design applications, design classes, how to program effectively, how should technology X be used effectively. I wanted to know what was important and what wasn’t. What did the pros do?

Well, I was disappointed with what I had to choose from. My choices were thick, heavy books at an outrageous price (damn the exchange rate!) that covered everything about technology X. There weren’t many on the topics that I thought I wanted. Professional C# Programming. Programming Robots with JINI. Essential ASP.NET. How to run a Linux Web Server Farm. Python explained. Now with 1300 pages of real-world sample application code! (I should not have to bother mentioning those Learn-everything-about-programming-in-five-minutes books. Those are beneath my contempt. I’m not talking about those. This guy does though.) Being rather green, I concluded that those books must contain what I want as well as a lot of other stuff that can’t really hurt anyway. So I bought some. I’d maybe look at a few chapters focussed on a particular topic. Then it would go on the bookshelf and stay there to be moved to my next apartment, another reason for detesting the grotesquely huge publications.

Now I’m more experienced with programming and buying computer books. I’ve learned my lesson. I’m wary of anything bigger than a few hundred pages. Those big fatties didn’t contain what I wanted to learn about. Or, if they did, they didn’t cover the topic deep enough, so I was forced to do it myself anyway. They focussed on a lot of how to do something, and not very much on when and why.

One idea Wrox had that I really liked was the Handbook. They were focussed, little books on a particular topic. And I mean particular. I managed to get a few on .NET topics from Code Access Security to Serialization to Scalability. I thought those were great. And that’s what I look for now in a book. Short, sweet and only covers one thing.

Those books are very rare, though, probably not profitable.

The System Of The World – A Review

Well I finally finished The System Of The World by Neal Stephenson. The System Of The World is the third and final book in The Baroque Cycle. I finished on the plane on the way to Australia. I say finally because I started it in October when it came out. Since I bought it I read a couple technical books and maybe one novel while TSOTW sat on my bedside table feeling sorry for itself.  By the time Christmas came around I was about half way through the book and determined to finish it before I left. Well I almost did it. Had about 80 pages to go when I had to leave for the airport. I couldn’t wait three weeks for that last little bit.

The latter half is far more entertaining. I think it was about half way through before a certain Shaftoe finally made an appearance. When I read Cryptonomicon the first time (I’ve read it twice, I’ve only read a handful of books more than once), I was in Physics and Math, so I loved Lawrence Waterhouse and couldn’t wait for his “turn“ in the narrative. The second time I was in Computer Science so I could appreciate Daniel Waterhouse more, though he still wasn’t my favourite (Bobby Shaftoe, this time), because I understood the lingo better. The Baroque Cycle has a few characters like that, but only Jack Shaftoe truly shines. So I enjoyed the second of the three books, The Confusion, the most. However, I like how all the characters aged in the third book: Daniel Waterhouse was WAY more interesting the third time around.

The first I’d heard about the Baroque Cycle was that it was about the feud between Newton and Liebniz. There is a conversation between the two that takes place in TSOTW that I speculate Stephenson made up that could well have been the first thing written. I’m glad, though, that that wasn’t the topic of the books. That would have been boring. Instead the Baroque Cycle is a mixture of genres: swashbuckler, cyberpunk, historical fiction. While I can’t say it entirely worked, I’m glad I read them all. I rate historical fiction on the interest I take in the period generated by the novel. For instance, The Masters of Rome Series by Colleen McCullough, an epic, and accurate, account of the fall of The Roman Republic inspired me to read at least three non-fiction books and countless other fiction about the period (She’s the best, don’t bother reading others about the Romans). So if I rate The Baroque Cycle on strictly that, then I have to recommend it. I enjoyed it enough that I want to read more about Marlborough, Newton, Louis XIV and I want to at least try to sort out the royals of that period.

But as a Stephenson novel? I don’t know if I’d recommend the Baroque Cycle if someone were interested in starting his work. As you can probably tell, I agree with the rest of the world: Cryptonomicon was a masterpiece and his best work. He would have been hard-pressed to repeat it, and none of The Baroque Cycle does it. But you won’t be bored. And you may learn a thing or two.

Recommended if you like Stephenson; like the Scientific Revolution; want three big, pretty books with which to impress people on your book shelf.