Being The 12th Man

I grew up in New York and lived in various parts of the state until a few years ago. I loved being a fan of NY teams since they were perennial contenders. Their owners had wads of cash and were willing to spend it to make a run every year. Being a fan of a winning team is one of the most exciting things I knew growing up and, honestly, I grew to take it for granted.

The first sport I followed closely was baseball. Born in Flushing, Queens, the Mets were the obvious choice. The first full season I watched was in 1986 when I was glued to our TV. The Mets went all the way that year and I felt like I was a part of it by watching every game I could (sometimes sneaking out of my room after bedtime to watch them on west coast trips).

As high school approached, I began to find baseball boring and made the move to hockey. We had moved to Putnam County (around an hour north of Manhattan) and had a solid 10-12 weeks of "frozen lake" weather to really get the most out of hockey. However, when it came to the NHL I had a tough decision to make.

That year, the Rangers were a huge disappointment and didn't make the playoffs. The Islanders, on the other hand, did make the playoffs and went pretty far. Buffalo had a team, but they were hundreds of miles away, and the team in Hartford was, well, in Hartford. However, Putnam was technically Ranger country (in my mind) so I made the hard decision and picked them. Sure enough, they went all the way that year, winning their first Stanley Cup in 54 years. I watched almost every regular season game. I bought the newspaper with Messier's "We Will Win Tonight" guarantee and watched the entire game on my feet in the living room. I watched Matteau eliminate the Devils in double overtime on a scrambled TV (I was at my grandparents' house and they only got the Ultra-Super-Basic cable package). I watched the Rangers almost squander a huge series lead to the Canucks, only to cap off the Finals at home. I really felt like I was a part of that championship.

Although NY football teams had some great success while I lived there, I never really got into the game. Even though I played in high school, it always seemed like an "old man" sport and there weren't enough games in the year to make it interesting. However, last year it occurred to me that I am effectively an "old man" now. With a wife and kid[s] (note the "forward compatibility"), I'm about three pairs of plaid pants away from a Golf Magazine subscription. Finally, I made the plunge and bought Seahawks season tickets.

It's been an amazing year as a Seahawks fan. Sure, I could go on and on about the great things that have happened. I could talk about the NFC championship we won yesterday. I could talk about the 10-0 home record. I could talk about watching the league MVP every week. I could talk about the amazing last minute win over the Cowboys. I could talk about the supernatural powers that protected our perfect season against three game winning field goals by the Giants. Instead, I'm going to talk about the same thing Paul Allen and the rest of his organization talk about—the 12th man.

This year I really felt like I was a part of the Seahawks championship. I felt like I deserve 1/68,000th of the credit that went into making Qwest Field the single hardest place for NFL teams to play this year. More than any other team I've been a fan of, the entire Seahawks organization makes me feel like they really care. Sure, we might be their main source of revenue, but their appreciation seems sincere. After all, they've even retired #12 in dedication to their 12th Man—the fan. If there's one thing I've learned about business, it's to make sure your customer feels like they're as important to you as possible.

For the record, this is also my first year following an NBA team closely (the Sonics). This should disprove any "closet fan" theories

PS: This guy can suck it for all I care. If I was as bad at my job as he is at his, there's no way I'd still have one. I am *praying* he picks the Steelers to win in the Super Bowl since that seems to be the only way to lock up a victory for us.

1/23/2006 1:19:39 AM (Pacific Standard Time, UTC-08:00)      Comments [0]  

Indigo & Workflow Foundation Hit Go-Live

Microsoft just announced Go-Live licensing for Windows Communication Foundation and Windows Workflow Foundation. This occurs when a quorum of program and product managers get in a room with a senior exec who says "You’re waiting for what/who to ship?!? They’ll take forever. Ship it with out them!"

It’s actually a huge milestone. Now I have to go brush up on what's changed over the past 18 months

1/18/2006 10:02:14 AM (Pacific Standard Time, UTC-08:00)      Comments [0]  

YAWS (Yet Another Whiteboard Screenshot)
Rohan reveals the truth behind Virtual PC.
1/7/2006 6:26:10 PM (Pacific Standard Time, UTC-08:00)      Comments [0]  

RPC In VPC

I spent some time earlier this week working with BizTalk 2004 in a Virtual PC 2004 environment. The VPC OS was Windows Server 2003 Standard and it was running separate from a domain. When I was at work I would used Shared Networking, whereas at home it would share my tablet's wireless card. I had problems from the beginning getting BizTalk installed, and then regular problems along the way related to operating when BizTalk would attempt to integrate with SQL, SSO, or other system services. The errors would vary, but they would invariably be complaining about the RPC server. For example, errors such as "Failed to generate the master secret (error code 0X80070005)" would come up.

The problem was the result of failed RPC endpoint resolution. BizTalk was configured to connect to other services via machine name, in this case "VPC-WIN2K3STD", since "localhost" is not allowed as an endpoint. Unfortunately, given the configuration of the server with the VPC in my mixed environments resulted in the OS not being able to resolve the name "VPC-WIN2K3STD" to an IP address. If a step in the process of installing or running an app fails, do the following:

1. From the VPC OS' command line, run "ipconfig /all". This will tell you what its host name and IP address are. If you're using Shared Networking, expect 192.168.131.### where ### is between 2 and 251. If you're sharing the NIC of your host machine, expect it to be the same (I haven't verified that this is actually a problem when sharing a NIC).
2. Edit the "hosts" file in "<system path>\drivers\etc" (probably "C:\WINDOWS\system32\drivers\etc") to include an entry for your local machine's name and its IP. Just follow the example used by "localhost" to see how this is done. This file is the first place the system looks to resolve a host name as an IP address before going to the DNS server.
3. Retry the step that failed. It should work almost immediately, but I've found that sometimes it seems to take a few seconds to kick in (maybe the IP is cached somewhere?).

Keep in mind that if your IP address changes, you'll need to update this file. If you don't, things will likely stop working since your OS will be looking for a non-existent IP. This could happen when your VPC reboots, is rehydrated, or has its network connection changed.

12/28/2005 10:33:49 AM (Pacific Standard Time, UTC-08:00)      Comments [0]  

Voluntary White Elepha--what?!?

When I first started using email years ago, I would often receive emails that were clearly not intended for me. As a nice Internet citizen, I would respond to these mails indicating that they had sent to the wrong address. However, I quickly learned that this was a great way to validate your email address on a spammer's hit list. Since then I've learned (along with the rest of the world) to just ignore email that wasn't for me, unless I had a really good reason to believe it was legitimately mis-sent.

Nowadays, I'll get a random SMS message every few weeks that looks legitimate, but intended for someone else. I ignored the first few, but I started noticing a pattern that makes me think that someone just miskeyed a phone number, resulting in all these messages being sent to me. As I've paid closer attention to this sender recently, it's clear that the last few have been business-related messages for another company. However, yesterday I received the following message (which I have edited with *s to remove identifiable info) that may clinch the validity:

***** is having a company Christmas party Friday Dec. 16th at 4:00 PM at the office. There is going to be appetizers and a voluntary white elepha

I've used the domain info from the source email to track down the company and am pretty sure at this point they're not spamming me (or verifying my number as a spam socket). I'm tempted to contact them directly and let the person who's been sending these to me that they have the wrong number. At the same time, I'm also tempted to just drop by this party and find out what a "Voluntary White Elephant" (I assume that's how the message would have ended) is. I'm also concerned that they may end up being pissed off that I didn't tell them sooner. After all, the poor dude who they thought they were texting may have been fired for saying he never received any of their messages.

A cursory search of this here InterWeb^tm indicates that "Voluntary White Elephant" is a "Secret Santa" game similar to "Yankee Swap" (which I had first heard of on last week's "The Office"). However, there's no way to be sure that's how the message would have ended without showing up at the party...maybe they'll really have an easygoing elephant that happens to be white. I just can't take that kind of risk.

12/15/2005 11:23:13 AM (Pacific Standard Time, UTC-08:00)      Comments [1]  

DirecTV Fined For Do-Not-Call Violations
MSNBC reports that DirecTV is being fined for hiring telemarketing firms that violated the DNC listings on their behalf. It's unclear as to whether any of these violations were directly performed by DirecTV employees, or whether it was just a case of their vendors breaking the rules and them being held responsible. Regadless, it'll be interesting to see if this has any implications for companies that hire spammers.
12/13/2005 10:31:11 AM (Pacific Standard Time, UTC-08:00)      Comments [0]  

The Mnemonics Are Gonna Get Ya!

I recently had the Pocket PC version of a Windows Mobile game rejected by VeriTest during the certification process. It was rejected because the app's menus had mnemonics (underlined letters to be used as keyboard shortcuts). Not having these has been a requirement for as far back as I can remember, so I was surprised they showed up--the .NET Compact Framework won't even let you turn them on. After doing some debugging I noticed something very odd--the mnemonics were showing up in the WM 2003 SE emulator, but not in the WM 5.0 emulator or on my WM 2003 device.

(Same bits on WM 2003, WM 2003 SE, & WM 5.0)

It turns out that Windows Mobile--for some time--has been smart about detecting attached keyboards and auto-injecting mnemonics into menu items, which is why the configuration I have across the emulators and devices showed up the way they did. I think this is pretty cool and another example of the little reasons why WM devices are such a pleasure to develop for (flame away ). Another nifty feature in WM 5.0 (as you can see from the screenshot) is how a two item menu on PPC will turn itself into a pair of softkeys to match the look & feel of Smartphone. Since this app was originally written for Smartphone and ported over (under 15 minutes of dev work!), it made things that much nicer.

Anyway, I raised the issue with Microsoft and VeriTest and it looks like this requirement may be changed so that you're allowed to have mnemonics when there's a keyboard present. After all, it would be a pain to stop the OS from putting them in, so why fight it?

By the way, you can buy this app for Smartphone or Pocket PC (they're actually the same CAB, but I can't figure out how to get Handango to let you have two different platforms for the same product). It's a .NET CF 1.0 app that runs on all Pocket PCs and Smartphones (except SP02 devices since those don't have .NET CF). Our 60% cut of every $4.99 purchase goes towards our mounting certification bills

12/12/2005 8:17:29 PM (Pacific Standard Time, UTC-08:00)      Comments [1]  

The Forgetful Mouse

Most laptops have touchpads that ship with the most annoying consumer feature ever on by default: the "tap to click". As an aggressive keyboard user, I always seem to have my palm smack the touchpad, resulting in "clicks" at the most inopportune times, causing key commands being set to windows I thought to be out of focus, etc. I always disable this feature every time I get a new machine (which usually requires installation of stupid OEM apps as part of the driver process). However, my tablet's Synaptic TouchPad seems to be forgetful, turning it back on every once in a while. As first I assumed this was due to something crashing & reverting to the anti-user default. However, tonight I noticed for the first time that all the Taskbar Notification Area(TM) screenshots in Synaptics' Device Settings tab have the clock time set at 4:20. I suppose I should just be glad they don't replace my screensaver with a lava lamp and search my drive for twinkies every few hours.

PS: If you don't get the 4:20 reference, ask your kids. Then again, you probably don't want to know.

12/5/2005 3:12:12 AM (Pacific Standard Time, UTC-08:00)      Comments [2]  

The Sky Is Falling!

It started snowing this morning, so I went to weather.com to see if it was even below freezing outside. I got a kick out of the "Severe Weather Alerts" blinking text on the page.

If you scroll to the bottom of the page, it says "About one inch of snow expected." Posers.

12/1/2005 11:43:52 AM (Pacific Standard Time, UTC-08:00)      Comments [0]  

Great Article On Using The VS05 Emulator To Connect To The Internet

http://blogs.msdn.com/akhune/archive/2005/11/16/493329.aspx

I don't know if I could have ever figured this out!

12/1/2005 2:01:31 AM (Pacific Standard Time, UTC-08:00)      Comments [0]