Mr. Hockey’s Final Shift?

My son Nate started hockey at four years old. He was such a talented player by the time he reached high school he had already been to the junior olympics three times and has 2 gold a silver and bronze medals. But there was alot of politics and some real ugly calls by the officials one year that sent him to the bench for a season, and after all the meetings the controversy and arguments he decided to give up his goal and dream. He switched to high school football, which really makes me sad. I know he is great at football and really enjoys playing on the varsity team, I just hope that he doesn’t completely give up on his dream as a professional hockey player.

If you asked me who I thought was the greatest hockey player of all time, I’d say, without even a second thought, Gordie Howe. Mr. Hockey had it all, size, speed, strength, smarts and more importantly that desire to win. It’s hard to believe that we will live in a world without one of the game’s greatest legends and ambassadors.

The 86 year old suffered a stroke over the weekend and fears maybe that the hockey great, as son Murray said, “I feel like this is his final lap around the rink.”

It’s hard to imagine Howe, whose daughter Cathy mentioned in an interview yesterday, that her father lost the use of his right arm and leg, can be weak. This was the same man who endured years in the punishing Original Six days of the NHL. The same man who played all 80 games, at the age of 51…

View original post 1,090 more words


The Case for Slow Programming

It would be great to find a way to quickly download information into the human memory banks. I would love to plug into a program that downloads information over night. How great it would be to wake up a qualified computer programmer, or a marketing guru.

Nature -> Brain -> Technology

My dad used to say, “Slow down, son. You’ll get the job done faster.”

I’ve worked in many high-tech startup companies in the San Francisco Bay area. I am now 52, and I program slowly and thoughtfully. I’m kind of like a designer who writes code; this may become apparent as you read on 🙂

Programming slowly was a problem for me when I recently worked on a project with some young coders who believe in making really fast, small iterative changes to the code. At the job, we were encouraged to work in the same codebase, as if it were a big cauldron of soup, and if we all just kept stirring it continuously and vigorously, a fully-formed thing of wonder would emerge.

It didn’t.

Many of these coders believed in thefallacy that all engineers are fungible, and that no one should be responsible for any particular…

View original post 887 more words