Set Godin made an excellent point about the difference between urgent and important in his blog post today. My takeaway was this gem:  You will succeed in the face of change when you make the difficult decisions first.

Quite insightful. Made me think of the Microsoft Solutions Framework which advocates completing the highest risk elements of a project first to increase the chance of success. Although I do not follow the process, it has become almost second-nature for me to start with the most difficult and challenging aspects of a task first. Then, come crunch-time, the going is a lot less difficult than it would otherwise have been and quality is not compromised.

I am going to PDC05 in Los Angeles. Will you be there?

ASP.Net supports dynamic code generation and compilation. Sometimes, you just need a quick and dirty solution. This is one such solution. It writes out a control script, loads it and then deletes the file.

string dynamicControlUrl = "~/" + System.Guid.NewGuid().ToString() + ".ascx";
string dynamicControlPath = Server.MapPath(dynamicControlUrl);
TextWriter tw = new StreamWriter(dynamicControlPath);
tw.WriteLine("<%@ Control language=\"c#\" %>");
tw.WriteLine("<script runat=\"server\">");
tw.WriteLine(" protected void Page_Load(object s, EventArgs e)");
tw.WriteLine(" {");
tw.WriteLine(" Response.Write(\"Hello World!\");");
tw.WriteLine(" }");
tw.WriteLine("</script>");
tw.Flush();
tw.Close();
Control dynamicControl = Page.LoadControl(dynamicControlUrl);
Page.Controls.AddAt(0, dynamicControl);
dynamicControl = null;
File.Delete(dynamicControlPath);

Finally decided to download the IE7 beta from MSDN. I am running it side-by-side with IE6 and I see some occasional error dialogs, but not sure if they are related to the fact that I switched it to run in local mode or if they are actually bugs.

BTW, to run IE7 in local mode --

1) Download and extract (using WinZip). Do not install.

2) Delete file shlwapi.dll

3) Create an empty text file IEXPLORE.exe.local

Alan Turing is largely credited with breaking Enigma and it is quite unfortunate that not many sources give as much credit to Marian Rejewski. Rejewski and his team in Poland had cracked Enigma almost a decade before they shared this with the Bletchley Park code-breakers. Turing was the one who later identified the vulnerabilities of Engima and designed the automated systems to speed up the decipherment.

Yesterday, I spent most of the day at the International Spy Museum. I share everyman's fascination with the spy business and the museum did not disappoint. It has a treasure trove of spy gadgets from all over the world and with some exceptions, does a pretty good job of documenting the exploits of spies throughout history. I especially liked the section on Enigma. Not only is the machine's working explained for the technically proficient, but there are also some nice interactive applications that allow the lay person to be amazed by its magic.

I didn't think much about Rejewski until I passed the Polish Embassy on my way to Starbucks. The museum exhibit had focused quite a bit on Turing, but I seemed to recall from reading on of my favorite books -- The Code Book -- that Poles were involved in cracking Enigma. Looking at the chapter on cracking the Enigma, I found that my memory had served me right for once. Simon Singh does a much better job at giving credit to Rejewski than does the museum. His team did the pain-staking task of developing the techniques that were later used by the Allies.

Unfortunately, that's how it always is, isn't it? History is in the eye of those charged with documenting it. Credit to both -- Rejewski and Turing.