Stephen's first law of diagnosing problems in production: try to replicate in test. (Assumptions: you have a test environment, you use it regularly, and it is reasonably close to production). Sometimes you just can't replicate the problem — for instance, it might be due to an oddity in a customer data file that you're not allowed to run outside of production. In those cases, see if you can use a proxy. For instance, try copying the file and masking the sensitive data, then running it in the test environment (of course, the masking process might cover up the error that is causing all the problems).

Production needs to stay clean, and as developers we need to keep our hands out of it as much as possible. This is particularly true in a highly secure environment with strong separation of duties, wherein you might have to drag a sys admin into the picture just to get to obscure log files, for instance. Replicate the issue, solve it, document it, and make sure everyone else in the company is able to share in the lessons learned.

I've just uploaded some statistics for the Mississippi River Twin Cities Landbird Monitoring Project. Go into an individual species and you can see a color-coded table of results, histogram showing species presence over time, and a Google maps display with the count of birds at each exact point count location within the various sites monitored. Interestingly, Gold Finchs are the most common bird across these parks. Its definitely fun to pour through this data. Later in the summer, data from previous years will be loaded into the site as well. Check out the Great-Crested Flycatcher — at 8 of 9 sites, they showed up all at the same time (week of 5/9). I can't wait to compare that to previous years' migration results.

This morning at Battle Creek West, where we saw an adult Barred Owl drying itself after a bath two weeks ago, we found two fledged babies. They were adorable. If human babies looked like this, we might have a few already. Someone else's great photo (dead link removed; SF 2025).

Also seen, in another part of the park: small milkweed plant with a monarch egg and 2nd molt monarch caterpillar, and flying nearby was an adult monarch. Seeing three stages of monarch within a minute was quite gratifying. Next time we're out there (two weeks) we'll have to check in on their progress. (T. is now associated with the Monarch Larva Monitoring Project.)

This year is the tenth anniversary of the charter signing of the United Religions Initiative. To mark the occasion, the URI has launched a brand-new, gorgeously-professional website. If you have interest in the world of interfaith action and cooperation that is "bound for peace", then I invite you to stop by the site. I've not been so involved with the URI's work in the past few years, but I am still proud to call myself a supporter of this dynamic, idealistic-yet-grounded organization.

This month, the "Friends" (Yaran), a group of informal national Bahá'í leaders in Iran, began their third year in prison. The charges against them are specious, e.g. "corruption on earth", and the Iranian government will not even give them the dignity of holding a trial. I know that the Iranian people are better than this. I pray that their government will come to recognize their duty to respect the freedom to worship, and release this group. Last weekend I attend a devotional gathering in honor of this group, and others, who are imprisoned in Iran. I opened a particular Bahá'í prayer book with which I am not familiar, and this was the first prayer I encountered:

I beseech Thee, O Thou Who art the Lord of all names, to guard Thy loved ones against Thine enemies, and to strengthen them in their love for Thee and in fulfilling Thy pleasure. Do Thou protect them, that their footsteps may slip not, that their hearts may not be shut out as by a veil from Thee, and that their eyes may be restrained from beholding anything that is not of Thee. Cause them to be so enraptured by the sweetness of Thy divine melodies that they will rid themselves of all attachment to any one except Thee, and will turn wholly towards Thee, and extol Thee under all conditions, saying: “Praised be Thou, O Lord our God, inasmuch as Thou hast enabled us to recognize Thy most exalted and all-glorious Self. We will, by Thy mercy, cleave to Thee, and will detach ourselves from any one but Thee. We have realized that Thou art the Beloved of the worlds and the Creator of earth and heaven!”

Glorified be God, the Lord of all creation!

~ Bahá'u'lláh, Prayers and Meditations, LXI

I wonder how many others didn't think to scroll down further on the Pex download page, and find this link? Visual Studio 2010 Moles - Isolation Framework for .NET. Moles is available for free, while the full Pex environment requires MSDN.

Once again I've learned the hard way that it pays to read the release notes. After installing Pex v0.91.x, suddenly I was having trouble running my tests in a particular solution. It has been driving me nuts - Visual Studio was throwing "object reference not set to an instance of an object" errors every time I tried to run tests, and the Test View was refusing to load any test names.

Finally, I noticed that I had a few tests that were still instrumented with HostType "pex" instead of "moles". I changed these around, and still got the error. Closed Visual Studio, restarted, and voìla, the tests can run, and Test View is populated again.

Pex and Moles - Release Notes

Can someone please tell me why Visual Studio 2010 no longer has the "Promote Local Variable to Parameter" refactoring? I use this every day. Thankfully CodeRushXpress has it, but the current version is a bit unstable, causing VS2010 to crash periodically.

I've been using AccuRev, including AccuBridge integration in Visual Studio, for close on two years now. And I like it. I don't know anything about the licensing fees, but for the enterprise that is interested in spending some money, it is certainly a good option. So, for anyone considering using AccuRev for source code control, and who happens to stumble across this site, here are a few points to consider:

I am using the latest edition of Service Factory - Modeling Edition (VS2008). I've created a number of FaultContracts in my DataContract model, and utilized them in my ServiceContract model. The generated code for the ServiceContract does not include the namespace or action for the FaultContract, e.g.