Some of you may remember the crash of the $125 Million Mars Climate Orbiter in September of 1999. Later review revealed that the Orbiter crashed because of a simple and avoidable problem. One team of software developers assumed English units for their measures while a different team assumed SI. Now maybe you're not building a $125 Million spacecraft to go to Mars but maybe you want to insure that you eliminate errors arising from misunderstandings about the units of measure involved--be that dollars or euros or seconds or minutes or even developer-hours. F# gives us a simple and easy to use mechanism to avoid this sort of dimensional inconsistency in our software. I will be discussing how a developer can specify units of measure in his or her software, how to use F#'s built in dimensional analysis to insure that all dimensions are used consistently and even a few more interesting tricks which can be done via Units of Measure.

Slides can be found on SkyDrive. The source file used for demos is also on SkyDrive.