Here. Tentatively schedule for July 10-11 in greater Portland, OR, the Applied XML DevCon needs your talks. If you want to speak on XML applied in novel forms, e.g. web services, interop, extensibility, Google hacks, replacement for more traditional data formats, RSS, hardware integration, blogging, or in any other fun, cool, fast or amazing way, let me know! I'm looking for sessions on things that you're actually doing or planning on doing with XML. Strict theoreticians need not apply. Send abstracts before 5/7 to csells@microsoft.com If you can think of another place, e.g. mailing list or blog, that would be appropriate for this announcement, please send it along.

Here. From Carlos Aquino: Things goes wrong all the time, but a good administrator is always alert. On this site they have some documentations about how to avoid (and how to recover from) a disaster on your systems.

Here. Tim O'Reilly pulls out four trends worth watching: Amazon.com web services, ubiquitous 802.11, h/w hacking and online gaming. I'm not sure how far h/w hacking will get us, but the other three I see being big deals. [slashdot.org]

Here. From Spencer Harbar: a nice site featuring the usual suspects! - but wasn't it don who did the bathtub SOAP talk? :)

Here. William Poundstone interviewed me for this book. I'm still waiting for my free copy...

Here. The one where I list what I learned my first week at the source of all software.

Here. From Jan Tielens: Hippo.NET is a tool for streamlining the build process of .NET projects in a team envirionment. It provides continuous integration by monitoring the shared Visual SourceSafe database and starting the build process when changes are detected. An important design goal is to provide a nice and easy-to-use user interface, to monitor builds and trigger the build process when needed. Now you can download a stable version of this tool, with full source code. Current features are: - Client/server model - Trigger build from remote clients - Implements the build process proposed by Microsoft - Automatic build number updates in AssemblyInfo files - Build history information - Current activity information - Fully configurable - Rich Windows Forms UI

Friday, April 25, 2003

After my first week at Microsoft *everyone* wanted to know how it went, both internally and externally. I learned some things:

• I learned that folks at MS will call a meeting for lots and lots of reasons, including at the slightest sign of confrontation or hurt feelings. For a guy that hasn’t really attended a meeting in the last decade, this is quite a switch : )
• I learned how to schedule a meeting w/ multiple people and a conference room (listed as “conf room <bld>” in the address book), all with conflicting schedules and all remotely using Outlook Web Access and without a SmartCard (I was pretty proud of that one, actually : )
• I learned that no one uses the phone for anything — instead, they schedule meetings
• I learned that it’s the person that wants something that does the actually scheduling of the meeting
• I learned that it’s OK to open your laptop in a meeting, otherwise when would you get any work done?
• I learned that it causes quite a stir when you disagree with the technical lead of one of the major pieces of technology that you’re supposed to be taking to the world
• I learned that it’s darn hard to find out who to talk to your first week, and that you should take your boss to most of your initial meetings so that s/he can make sure you’re getting what you need to get from them
• I learned that you can mix Exchange and POP3/SMTP to keep your new and your old email addresses going, if you use Office 11 and if you are willing to give up calendar and follow up notifications on your POP3/SMTP account (have I missed something?). I also learned that internal MS support doesn’t help w/ such things.
• I learned that internal MS support is the greatest support in the whole darn world. These people don’t let you off the phone ’til everything works. They’re amazing
• I learned that you can volunteer for absolutely anything you think is cool or important so long as you get everything else done, too
• I learned that it’s not good to ask for NDA access to super-secret bits for your friends the week before you start working there (OK, I’m pretty sure I knew that before, but I had to try… : )
• I learned that the right folks hanging out at lunch can make all kinds of interesting things happen
• I learned that MS and it’s employees is the most charitable company in the country (world?)
• I learned that the internal resources for MS employees are unbelievable. I could work their my whole life and never take advantage of all of them
• I learned that it’s important to sign up for your benefits immediately if you’re going to be remote w/o a SmartCard for a while, otherwise your son may wake you up in the middle of the night with a hard toothache and when you take him to the dentist the next day, the dentist won’t be able to confirm your dental insurance (as one example : )
• I learned that most everyone at MS is very nice (even when they’re telling you to f-off)
• I learned that everyone (and I’m no exception) has a hard time fitting in at first. One interviewer told me that his first 6 months at MS were the worst of his life. I pray that it doesn’t last that long for me
• I learned that after the initial period that few that survive it would ever think of leaving. I absolutely see how that could be