Recently I ran across and old article from Phil Haack, about moving his blog to Jekyll using GitHub. And I realized that this is (or might be?) a perfect solution for managing content about the FlightNode project (though it will not be part of the platform itself).

There is a lot of work to do in terms of getting content up and getting it formatted. This is just the start of getting the framework going, so that I can get all the text and pictures out of my head and into documentation that other team members can use.

Citizen-science: meet open source software. I'm starting an open source project called FlightNode, which will be a platform for citizen science bird conservation monitoring projects.

This project builds off the IbaMonitoring.org project I took on in 2010. I've been approached by a conservation organization here in Texas, asking for my help to build something similar to that site, but tailored for their purpose (I need to get their permission before using their name). What they want and need is more than I can provide in my "spare time." And I know of other programs that would be interested in using components of these projects.

Recently I was talking with a friend and extolling the virtues of using NuGet packaging for application and web site deployments - and I nearly forgot the core advantage: dependency management. It is all fine and well to have a fancy zip file, relabeled as .nupkg. You get the benefit of version control on the package itself, and you get the nuget.exe or choco.exe installer (or coming soon, OneGet).

But the most important piece is this: you don't have to bundle your dependencies with your installer package. You just need to "wire" them up properly in the .nuspec specification file, and make them available. Now, let's talk about managing those packages.

NuGet has been helping .NET developers maintain package dependencies for a number of years now, and any good dev should know the basic operations from within Visual Studio – how to add, update, and remove packages in a solution, using the NuGet Gallery. But to use only the NuGet Gallery is to know only half – or less – of the story. You might be missing out on…

• Testing out pre-release versions of your projects key dependencies.
• Reverting to older versions of libraries.
• Stand-alone tool installations using NuGet.
• Full-fledged Windows installations using Chocolatey.
• Placing your custom packages into private repositories.

Here are a few tips for moving toward mastery of this crucial part of the .NET development ecosystem.

More than twenty years ago, the National Spiritual Assembly of the Baháís of the United States published a statement declaring that "[r]acism is the most challenging issue confronting America" (The Vision of Race Unity). This past year has reinforced the public awareness of this truth: 59% of the nation's population believes that "our country needs to continue making changes to give blacks equal rights with whites", compared to only 46% about a year ago (Pew Research Center). I grieve to wonder how many of the remaining 41% recognize the systemic challenges faced by African Americans, and either don't care or, worse yet, are satisfied with them.

The Elm Fork of the Trinity River has returned to its secondary banks at last and the Sam Houston Trail Park on the Campión Trail is once again accessible, after two months of flooding. Riding my bike there today, I managed to get a few good photos, which are posted on Google Photos. First six in the gallery are from last fall, but the rest are from today.

A social media challenge was posed, #PlasticFreeJuly: try to avoid plastic in the month of July. Taken literally, many of us would be unable to read the challenge, without the plastic of our corrective lenses. Perhaps someone, somewhere, still makes glasses from melted, ground, sand. I shudder to think of the weight required to correct my own poor vision this way.

But there is a deeper truth: the gauntlet was delivered through a medium whose human-tangible representation beamed out through melted sand, encased in plastic, with circuits embedded in plastic. Perhaps someone, somewhere, manufactures computers using naught but metals, sand, and rubber insulation. With vacuum tubes.

This past Friday I finally completed the "public expression" portion of the eco-theology project for the GreenFaith Fellowship. The presentation is accessible at GreenBahai.com. It addresses the following topics from an multi-faith perspective:

• Highlight key themes in religious responses to climate change:
  • Love of Creation
  • Urgency
  • Love and Compassion
  • Justice
  • Oneness and Interdependence
• Call to Action — statements and declarations
  • Prevention
  • International Action
  • Awareness and Advocacy
  • Taking Action

I've spent the weekend preparing a presentation on the Call to Action on Climate Change, which I'll be giving at the Bahá'í Center of Irving on this coming Friday evening.

Joining so many others in the worldwide faith communities, I am overjoyed at the Pope's encyclical Laudato Si, which came out officially just a few days ago. Although I will not be saying much about it, it is a large part of the inspiration for the up-coming presentation. And I would like to share the heart-achingly beautiful second paragraph:

This sister now cries out to us because of the harm we have inflicted on her by our irresponsible use and abuse of the goods with which God has endowed her. We have come to see ourselves as her lords and masters, entitled to plunder her at will. The violence present in our hearts, wounded by sin, is also reflected in the symptoms of sickness evident in the soil, in the water, in the air and in all forms of life. This is why the earth herself, burdened and laid waste, is among the most abandoned and maltreated of our poor; she "groans in travail" (Rom 8:22). We have forgotten that we ourselves are dust of the earth (cf. Gen 2:7); our very bodies are made up of her elements, we breathe her air and we receive life and refreshment from her waters.

The news has been going around: "refactoring doesn't work," say researchers. Code quality does not improve. It isn't worth the time and effort. Here's why I don't buy it — why the research is fundamentally flawed and real software groups should ignore it.