The Seattle Code Camp 2010 virtual event is live at http://events.boostweb20.com/events/SeattleCodeCamp2010. You can watch most of the sessions live and/or on-demand. This virtual event is powered by SharpLogic's Boost Virtual Events with great support from Tri-Digital for all the video encoding and production.

I am very proud to announce that Layla Ruiqiu Kaim was born at 5:16AM on March 15, 2008. She checked in at 8lbs, 21 inches. Both mother and baby are doing very well.

(Ruiqiu is a Chinese name pronounced like "Rachael" without the "l".)

We launched the Boost Online Media Service earlier this week. It's a service designed to simplify the integration of user-generated content, such as video, music, files, etc, into other sites.

For more details, please check out the site at http://www.boostonlinemedia.com.

I co-hosted This Week on Channel 9 with Brian Keller. Check it out at http://channel9.msdn.com/showpost.aspx?postid=385240.

It's been three years now and we're still going strong. Every day I'm amazed at how much I've learned, and yet somewhat apprehensive about the lessons I haven’t gotten to yet. Some of the times have been rough. Really rough. Yet somehow, everything always seems to work out and things get better and better. Year four looks to start out strong, and I’m excited to wake up tomorrow and get it started.

We recently launched PuckLink, a social network designed for recreational hockey players. After playing for a few years in the northwest, it seemed clear that people needed a better way to manage and coordinate teams, games, and practices.

You can check it out at http://www.pucklink.com. If you know anyone who plays hockey, please let them know!

For those who don't get why this is funny, you should know that AdCenter is Microsoft's competitor to Google's AdSense.

I find that most upstream project errors occur due to simple misunderstandings. Although I always try to ask all the relevant questions early on, there are almost always gaps in what I’m really trying to learn, and sometimes there are subtleties in terminology that mean very different things when being translated from business requirements into technical specifications.

Last week, we had a project extended slightly to support an additional locale. The engineer responsible for the project gave me two options: one simple (but inelegant) and the other sophisticated (but time consuming). I asked the client if they had a preference between the two, but rather than explaining how this impacted the business aspects, I pretty much laid it out as “hack vs elegant”. The client opted for the more elegant approach, which we began.

I took a walk to ship something from the UPS store. On my way back to the office, a car pulled up next to me and a woman asked “How can I get out of Redmond?”

Being the helpful citizen, I replied, “Pick a road and don’t make any turns.”

She smiled—patiently—and asked me how to get to SR-520, the nearest highway. After all, this was the question she really wanted answered. She was two blocks away, so I obliged and gave her the info she really wanted. I’m pretty sure that worked out fine.

Anyway, I rushed back to the office and called the client again. This time, rather than asking the “hack vs elegant” solution, I explained how the decision we were making now would impact the way we would extend the project in the future, and asked the client where they saw the project evolving to. As it turned out, the client had upcoming features I hadn’t accounted for, and the “hack” approach was actually the more elegant option because of the feature requests we would receive once we finished off the current round.

The moral is simple: ask the question you really want answered. It makes life a lot easier down the road.