> Design patterns are a way to describe how abstractions are passed around in code
In an object oriented language the abstractions are Interfaces, Abstract classes, Virtual Methods, etc..
For inst Continue Reading
I'm often asked at conferences and on twitter how to get into Functional Programming from an Object Oriented or Imperative mindset. This series of posts aims to provide a bridge between the two parad Continue Reading
Partial Application and Currying are two common confusion points for people coming to autocurried languages for the first time. Often they'll say things like "this function takes 2 ints and returns a Continue Reading
At the most recent [@FunctionalKnox](http://twitter.com/functionalknox) meetup a question came up about the Elm architecture and how that might be implemented to develop a console application in F#. Continue Reading
Many blog posts have covered this topic by explaining the function signatures of each of these functions. While I think that is valuable, that's not the way I think about them when I'm writing code. Continue Reading
In the process of creating a web service backend for a large web application for Diamler I've come across a few patterns that allow me to provide functionality without bloating my codebase. As the ap Continue Reading
> Successive arguments should be separated by spaces or tupled, and arguments involving function or method applications should be parenthesized
If you're new to F# you may have seen this exception on Continue Reading
In part one of this series we walked through [modeling the domain of our card game](/blog/f-card-game-part-1-modeling-the-domain/). In this post we'll use that domain as a guide to help us create a d Continue Reading
This is the first post in a series where we'll walk through creating the card game [Crazy Eights](http://www.pagat.com/eights/crazy8s.html) in F#. Playing cards are a fairly well known domain and, de Continue Reading
In a previous post on [F# data access](/blog/how-to-example-application-with-data-access-in-f/) I dropped a hint about a functional way of handling invalid arguments. The code in question looked like Continue Reading
One of my biggest hurdles when starting with F# was how I should structure an actual application. There was documentation for individual libraries and scripts but not so much for app structure [this Continue Reading
I'm going about my business dealing with option types thinking I finally have a good handle on monad usage within F# when suddenly I receive the following error.
This expression was expected to have Continue Reading
In my previous post on [getting into higher order functions](/blog/getting-into-higher-order-functions/) I wrote about how I've been using higher order functions instead of foreach loops. All of the Continue Reading
Recently I've developed a love for F# and functional programming principals in general. Something about the way I code in those languages makes the code just seem to work the first time.
After a sh Continue Reading
When I started learning F# I had a hard time grokking how and when to use a Discriminated Union (Sum type). I had experience in several paradigms and languages, but had never seen or used this data c Continue Reading
>This post is part of the [F# Advent Calendar in English 2015](https://sergeytihon.wordpress.com/2015/10/25/f-advent-calendar-in-english-2015/). Thanks to Sergey Tihon for organizing and letting me be Continue Reading
While reviewing the bugs that I've written in F# over the course of my most recent project I've found that the only recurring bug I had was passing arguments of the same type in the wrong order.
###B Continue Reading