I got my Qtek 8500 today. The bad news was that I got the French version of the manual, but that wasn’t so bad, since I wasn’t going to read the manual anyway. However, the worse news was that all of the phone menus where in French, too. The nice folks at expansys.com were quick to send me the set of menus to turn English back on, but the instructions they sent where themselves in English, which required me to do a little babelfish work to translate into French menu text, but I managed.

Things I like about my new phone:

• It’s a flip phone that looks almost exactly like the famous RAZR, but runs Windows Mobile 5, allowing me to sync my email, contacts and appointments, play my music, load my own apps, etc. Physically, it feels very nice — thin, but solid. Even the flat keypad feels nice.
• I really like the higher res screen (when compared to my Audiovox 5600) and the larger keyboard (handy when you’ve got sausage fingers like mine).
• I like the external screen with the clock (a nice round analog one, too), the battery, the email count and three buttons for controlling the audio.
• The reception is better than my Audiovox.
• The volume on both my existing bluetooth headset and the included headphones is louder than my Audiovox (which is good for an aging Def Leppard fan…).
• I love not having to lock the keys on my phone — just flip it!

Things I don’t like about my new phone:

• The single, proprietary USB port (they call it an “extUSB,” whatever the hell that is). It’s for power, data and audio, which is handy, but I’ve got a bunch of mini-USD cables that no longer work, as well no way to connect my fully music-capable phone to the mini-jack in my car. I can get a conversion from extUSB to mini-USB on expansys.com, but so far, I’ve found no way of connecting the phone to my car.
• The camera’s high-res (1.3M), but doesn’t seem to focus very well.
• I haven’t yet found the button or option that allows me to set flight mode. Given the amount of air travel I do, that’s kind of a problem. Hopefully the pictures in my French manual will provide a clue…
• My $19 1GB mini-SD card doesn’t fit — I need *micro*-SD (who knew?!?). Luckily, micro-SD cards are pretty cheap, but it’d be nice to use my existing mini-SD cards, especially since the included storage was just enough to hold a single MP3 file…
• I don’t like the Start menu laid out in a 3x3 grid — I prefer to have things in a list with numbers by ’em, like in WM 2003SE. As it turns out, the numbers still work, but they’re not shown.

It’s true that I’ve listed more things I don’t like than that I do, but most of the stuff I don’t like is nuisance and the stuff I do like is very, very cool. I don’t know about battery life yet or what I’m going to think over time, but right now, I really like this phone. Recommended.

I’ve just registered for the Portland Code Camp 2.0, July 22-23. It’s a free conference that includes 26 developer sessions (so far), food, a party and the potential to win an XBox 360. And did I mention it was free? I’m not sure about the name (it’s being held at the Washington State University in Vancouver, WA), but other than that, what’s not to love about a local, free, developer conference?!?

And if you’re coming from out of town and need a place to crash, I’ve got a spare room. Come one, come all! Tell a friend! Register today! It’s free!

The reviews have been largely positive (but not completely), and I’m very much looking forward to my new QTEK 8500 (aka the Star Trek [STRTrk?]). Apparently I’ll be one of the first folks on the west coast to have it, which will probably destroy my book-writing productively over the weekend (I’m supposed to be working on the Avalon RTM book).

Being first with hardware is not generally something I like to do. In general, I purchase laptops and cell phones and not many of either (usually one every 18 months of either). Frankly, I’m a late adopter on hardware ’cuz I like to handle someone else’s first (no snide comments, please… : ). However, the experience with my Audiovox 5600 has been so positive and the features of the QTEK 8500 are so overwhelming (on paper) that I just had to get it ASAP. It’s really the first Windows Mobile 5 phone I’ve found compelling.

Stay tuned for a review.

I’ve been doing some design work with a small part of my new team for a few months now and we’ve gotten largely on the same page with each other. However, there were 20-some odd folks that we hadn’t done a good job keeping on the same page, so ChrisAn proposed an off-site. I proposed the format:

• 45-minute slots for each “bucket” of design functionality with the owner of the bucket leading the discussion (my boss, Adam, wanted to make sure that at least half of each talk was *not* lecture from the speaker). Each session was followed with a 15-minute break.
• 90-minute break-out sessions where each person had to pick their technology bucket and work with the owner to produce a 2-page functional spec and a 2-page technical spec.

If this format sounds like a tweaked DevCon to you, then you know where I got the format.

We started at 8am (1-2 hours before most folks start their day @ MS), so that gave us a little shared adversity to help build the team.

The 45 minute sessions made sure that the presenter had to get to the meat quickly, while the 15 minute breaks allowed folks some downtime to catch their breaths, check their email and chat with their brethren (this was a new team, so “bonding” time was an important element).

The 90 minute break-outs allowed folks to self-select into the bucket that most interested them, validated that we had the right buckets (any bucket w/ too few people would be cut, whereas any bucket w/ too many people would be split), helped establish the base-line for each bucket’s future (we used the off-site to kick-start the buckets) and gave the team a seemingly impossible task given the amount of time they had (shared impossible task == more team building).

Like your average DevCon, the “DesignCon” worked pretty well. We generated a ton of issues in each bucket that the owner hadn’t yet thought of and gave the entire team a kick-start down the road to shared pov. Also, since we had some folks from other, related teams and from upper management, we made sure we were communicating up and out as well as internally.

Of course, just as no DevCon is perfect, neither was the DesignCon, but if you’re looking for a way to get your team pointed in the same direction, I find the DesCon format a good one.

I’m thinking about doing a DevCon before the end of the year (likely October) in a pleasant environment (likely the Skamania Lodge) on a topic that’s *not* XML or Web Services based (we’ve done that topic to death). The soul of the DevCon will remain the same, i.e. to cut away all the unessential conference baggage and concentrate on why we’re spending time at a conference in the first place — the talks by industry experts and experienced practitioners.

If I organized such an event, would anyone come?

If you like man, you’ll love MSDN man. Enjoy.

The WinFX name is no more. Instead, WinFX (.NET 2.0 + W*F)is .NET 3.0.

For a long time, my favorite place to put up code snippets that I could get back to later has been pinvoke.net (like GetTempFileName). However, that was only good for managed/native interop, whereas the MSDN Wiki is for anything in the docs. I don’t know what their commitment is to keeping content over time or between versions, but I’ve got my fingers crossed. Enjoy!