January 9, 2004

New Home for Many MS Bloggers

Don't have enough bloggers to listen to? Can't find your favorite MS blogger? Chances are that you'll find a bunch of interesting tidbits at the new MSDN blogger site.
January 9, 2004 .NET

Developers Shrug Off Longhorn Delay Rumors

January 9, 2004 Spout

Surprised by Microsoft’s Openness

Friday, January 9th, 2004

I get a lot of emails from folks surprised about how open Microsoft is being lately, mostly due to all of the blogging we’ve been doing lately (some of us started long before we ever became employees). However, even I was surprised in an internal blogging meeting today filled with a bunch of MS bloggers. During the meeting, we talked about a bunch of the benefits to MS and to our customers. Sara talked about how blogs are driving more traffic to MSDN than our own headlines. Robert described his “green, yellow, red” scale for determining whether to blog about something (believe it or not, he does decide not to sometimes : ).

And then Adam Sohn from marketing talked about the need to police ourselves, describing some of the downsides in regards to blowing some group’s launch plans or unconstructively criticizing another group. He preached caution when approaching the line between what was good for the customer and what was good for Microsoft. After listening to what I began to interpret as a message of self-censorship, I asked Adam a warm up, “Isn’t it true that a lot of the stuff close to the ‘line’ is what our customers find most valuable?” He agreed that it was. And then I asked Adam my real question, “So, when we get close to that line, do we err on the side of our customer or ourselves?”

Now, you have to remember that I’ve been a contributing member of the Windows development community for a lot of years. I’ve seen how aggressive Microsoft is in everything it does to always be on top. So when I asked on what side of the line I should come down, I fully expected to be told to keep the shareholders in mind.

Of course, you know what his answer was or this story wouldn’t have made it into my blog until after my tenure at MS was complete (or just before : ). He said, without hesitation, “Err on the side of the customer.”

That blew me away. Of course, I’ve been doing just that since before I became an MS employee and Robert rides the ragged edge all day long, but it was *very* nice to hear that guy with the PR and legal battle scars tell me to keep the customer first and foremost in my mind.

Thanks, Adam. You’ve confirmed my decision to work at Microsoft.

January 7, 2004 .NET

Vector Graphics & Declarative Animation w/ Avalon

Don "XML" shows how to use graphic primitives and animation declaratively in Avalon, building an analog clock in the process. Cool!
January 7, 2004

Stereolize Pumps Up Presentations

Not only does Longhorn intimidate me by removing my safe, comfortable barriers to building difficult applications, Stereolize does the same for presentations, but seems to require a music composer as well as a graphic designer. Yikes!
January 6, 2004 .NET

Breaking the Mental Logjam

As I’ve mentioned, one of the biggest problems I see with Longhorn is deciding exactly what to do with all of the new capabilities. So, when Carter Maslan showed me some internal training videos showing off some uses of Longhorn in potential real-world applications, I just knew we had to get them out to the world.

The first such “concept video” is centered around commercial real estate (available at 320x240 and 640x480) and Carter’s got more planned in other industries, including manufacturing, telecom, financial services and more. The goal is to help break the mental logjam around how we build Windows and web applications today to get folks thinking about the possibilities that Longhorn provides. Enjoy.

January 5, 2004 .NET

Don Box on .NET Rocks!

I haven't heard this yet, but I just know it'll be fun. Once you get Don started talking, it's hard for me to stop and interesting things almost always pop out. : )
January 3, 2004 .NET

WinFS: Stamping out the Roach Motel

For those of you unfamiliar with Don’s reference, a “roach motel” lets roaches in, but never lets them out. That’s exactly what most apps do today, i.e. take data in from users or import routines, but never let it out again. As Don states, one of the chief benefits of WinFS is that data that apps store in it will be available to other apps, thereby letting the roaches out of the hotel. Where Don’s analogy breaks down is that in the case of application data, letting the roaches back out of the hotel is actually a good thing. : )


← Newer Entries Older Entries →