I really like Outlook 2007. I just LOVE the ToDo bar, and the searching, and the flagging for followup and marking done, and the way the calendar looks now, and well pretty much everything. Except one thing. I hate that Outlook Today view and I hated it before too. Well... I just made it go away.

Tools, Options, Other tab, Advanced button, click the Browse next to "Startup in this folder" ... and no more Outlook Today when Outlook first starts up. Simple, but so satisfying!

Kate

So you were thinking about entering the Gadget contest, but then you didn't get around to it? Well lucky you, you get another chance. Here's what I heard today: the deadline has been extended a month. You have to get your gadget into the Gallery to enter, and it's a process with a few steps to it:

Process to Enter Competition

 

Developers will need to perform the following actions:

 

1.       Post their Gadget on the Windows Live Gallery (approval process can take a few days)

2.       Return to the Gadget Vs. Gadget site and select ‘Enter Contest’ tab and use their Live ID to login

3.       Complete the entry form to submit their Windows Vista gadget for review

 

Winners will be announced September 4, 2007.

Same cool prizes, same great exposure, so go for it! http://www.microsoft.com/canada/msdn/gadgetvsgadget/default.aspx . Remember, Canadians only!

Kate

Steve Clayton reports on a British university that offers a B.Sc. in .NET ... well in Computer Science but with a deliberate emphasis on .NET technologies. Interesting approach since here in Canada universities like to distinguish themselves from colleges and trade schools by teaching theory and concepts and not worrying too much about what tools the students learn how to use along the way. The belief is that learning to use tools in general and learning the commonalities behind them (what is a compiler, what is a renderer, what are the aspects of identity management) has greater long term value than learning one particular tool or toolset. In general, I agree with that belief, and I've hired people from a wide variety of backgrounds over the two decades we've been in business. But on the other hand, if you're going to teach all that general stuff, why not teach it in the context of some tools that happen to be immediately useful in the work world?

Kate

Roy Osherove is looking for a Test Driven C++ trainer who lives in Israel already. He can make you a better trainer, he can get you the TDD background you need, but you need to have the C++ chops already and to be in the area. If you're interested, read his blog entry and make yourself known to Roy directly.

Kate

This is actually something that got settled during Tech Ed USA but my June schedule meant a lot of things I intended to blog didn't get blogged. Now I see myself listed on the Featured Speakers page (I told them, "flattery will get you everywhere" and they're going for it) so it's official.

My talks? The C++/Vista talk I did in the USA, plus a managed-code Vista one. We're still working on an abstract for that.

This will be my third trip to Barcelona. Will this be the year I do the Gaudi-tourist thing? Sure hope so!

Kate

Speaker Idol is happening again at Tech Ed Developers in Barcelona this fall. You have months to sign up, but only the first 30 are accepted, so if you already know you're headed to Barcelona (and not speaking, live in EMEA, don't work for Microsoft, etc ... full eligibility rules on the contest site) then you want to give this some serious consideration. Speaking as a judge at this year's US event, I can tell you that the experience of trying to do 5 minutes on a topic you know well can only be good. In order of the worst-possible-thing to best, here's what can happen:

• You can do your talk, do OK, not win, and learn nothing from the judges while still failing to impress anyone with your speaking skills. I think this is pretty unlikely, but anyway it would leave you where you were before you tried - no loss
• You can learn some very specific tips on being a better speaker, both from observing other speakers whose content you don't understand, and from the judges giving you ideas
• You can show your skills in front of people who choose speakers - and not just for Tech Ed either
• you get some publicity and bragging rights just by being selected
• You can win a speaking slot at Tech Ed

To enter, you need to make a 3 minute video of yourself presenting on a technical topic, so don't dawdle!

If you are sure you don't want to enter, either because you're already a Tech Ed speaker or because you'd rather die than speak in public, be sure to at least plan to watch. I found it highly entertaining.

Kate

Why, you call 911 of course. I imagine it would be a challenge for the 911 operator not to laugh out loud, but it was true...

http://www.theglobeandmail.com/servlet/story/RTGAM.20070712.welephants0712/BNStory/National/home

http://www.cbc.ca/canada/toronto/story/2007/07/12/elephant-stroll.html

http://www.thestar.com/News/GTA/article/235173

My favourite part is the elephant who didn't particularly notice they'd escaped and went to sleep just outside the pen. She's the one at the far left not being sprayed with the hose.

Update: The National Post provides this delightful picture, and links to the 911 call and dispatcher conversation. "Outstanding elephant" indeed. And what a nice police department to host the mp3s - not all would.

http://www.police.york.on.ca/Press/07-160928%20Comm.mp3

http://www.police.york.on.ca/Press/07-160928%20Dispatch.mp3

Kate

In a talk on IDE tips and tricks for Visual Studio, I asserted that good programmers are ten times as productive as ordinary ones. I didn't remember where I'd read that, but I knew it was true. I've just worked with so many folks who need a week to do what some superstars can do in a morning. The ordinary guy needs half a day to find some samples that are similar, half a day to tweak them so they fit into the current situation, a day to test and realize they aren't quite right, a day to adjust them and then fix the things that broke while adjusting them, half a day to get distracted and lured into scope creep by some comments during user testing, then another day to fix up what they did that they shouldn't have, and finally a half a day to clean things up and make documentation. The terrific guy only spends an hour finding samples, stays focused, documents and tests along the way, and makes short work of a specific small task. And I find this holds over months and years as well as over the course of a week.

Now I bumped across a proper cite of that, and not surprisingly it's from the Mythical Man Month. The quote and some related musings is over on Phil Haack's blog. Worth reading and worth thinking about. There are many ways to be productive ... write code that solves the real problem, don't write buggy code, don't write brittle code, and so on.

Kate