Lunchtime blogging strikes again - this post has probably been brought to you over the course of a few lunch times.
Like most of my posts on the subject of
F# there really isn't much I'm adding to the wealth of the community, but I feel as if contributing to the community in blog posts from an average .NET developer's perspective does have value. F# is pegged and marketed as a great language for niche problem domains (just look at the Try F#: Learn page) - but I'm all about using F# as a great general purpose language, instead of C# or VB.NET.
This post is probably a long time coming since I'm really enthusiastic about both test-first software development and F#. I've been mostly prompted to write my thoughts and findings down in response to seeing @@RobAston's blog post - On testing and the REPL in Clojure; who I've been following (which as I can see from Twitter, most of the developer community does!) while he adopts Clojure.
So what am I going to be writing about? Basically how using F# makes it easy for me to drop some of the dogma and get on with it. I've done a few projects now at work which involved writing F#, and this kind of outlines the how I work while doing it.