Mr & Mrs Smith

You done laughing?

Let me tell you how I choose to see a movie, before you start laughing again.

First, I have to be generally interested – that’s changing and getting harder to do as I get older. Second, when the movie comes out, I’ll read Roger Ebert’s review. He’s a candy man: he likes a lot of movies and rates them high. Then, I’ll read what the reviewers at the Globe And Mail write about it: they hate everything just to spite you. They’re the snotty type that criticize everything because their own lives have no happiness.

Based on their reviews and these rules, I’ll then deem the movie worthy of viewing:

  1. Ebert gives it ** or lower: don’t see it.
  2. Ebert gives it *** and Globe And Mail gives it **: worth seeing.
  3. Ebert gives it *** or higher and Globe And Mail gives it ***: go see it.
  4. Ebert gives it **** and Globe And Mail gives it ****: ha ha, that’s a trick – Globe And Mail doesn’t give anything worth seeing ****. Anything with **** from the Globe And Mail may be truly brilliant, but watching them is usually is super depressing and you would never, ever want to see the movie again. (Some examples: Monster’s Ball, Monster). I’ve stopped doing it.

Where was I?

Oh yeah, Mr & Mrs Smith. It passed rule 3. The Globe And Mail was right, it was a good movie for the first two acts, but then devolved to an action movie in the third. But the first two acts are totally worth it. And hey, it broke up a real marriage, right?

Recommended.

On A Reading Tear

I’ve been reading and reviewing a ton lately. I’ve got a few more books in the pipe as well. Stay Tuned.

Joel recently posted a pointer to his list of indispensable books. I was pleased to note a few that I own, although I wouldn’t have considered some to be programming books. My employer has an excellent policy of paying for any book that we buy related to our profession. There are number on Joel’s list that we own in the office. I’ll have to take a look at them.

Fun. Fun. Fun.

Pragmatic Unit Testing – A Review

Pragmatic Unit Testing, by Andrew Hunt and David Thomas (The Pragmatic Programmers), is just the kind of software book I like: short, concise, laser-focussed on one topic. That topic, apparently, is unit testing with a pragmatic bent. There are two versions of the book: 1) In C# with NUnit; and 2) In Java with JUnit. I read the C# version, natch.

Ever since reading Coder To Developer and Test-Driven Development in Microsoft.NET, I’ve been a huge proponent of TDD to anyone who will listen. I’ve found my code to be easier to use, easier to debug, and hella solid, as the kids say, since starting TDD. So I didn’t think Pragmatic Unit Testing would provide anything new for me. In large part, I was right: nothing new. Whatever wasn’t covered by the above two books, I had already learned through experience. However, the book articulates the power of Unit Testing and TDD very well; better than I ever could at any rate. It reinforced what I already knew.

At around 150 pages, it’s a very quick read. The book is written in a conversational tone; written as though you had the brilliant idea to hire the Pragmatic Programmers for an afternoon to explain the power of Unit Testing and this was what they presented to you. I’d recommend this book be mandatory for all new hires at your company if you practice unit testing. Consequently, it should be mandatory reading for you if you don’t. I have a suspicion that I’ll be refering to this book every year or so to confirm I haven’t strayed to far from pragmatic unit testing.

Recommended.

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.

An announcement about MovieTickets.com

In Canada, before every movie, we’re subjected to really, really lame ads about movietickets.com. Go there if you have to know what they’re about. Their stupid, STUPID ads repulse me from ever using the damn service.

If MovieTickets.com was a person, I’d kick it in the balls.