Slides and videos explaining a functional approach to error handling| fsharpforfunandprofit.com
The "The Return of the EDFH" series| fsharpforfunandprofit.com
These terms and conditions form your agreement with this site (hereafter, the SITE) and ScottW (hereafter, ME).| fsharpforfunandprofit.com
So you’re all excited about functional programming, and you’ve been learning F# in your spare time,| fsharpforfunandprofit.com
The "Recursive types and folds" series| fsharpforfunandprofit.com
One comment I hear often is a complaint about the gap between theory and practice in F# and functional programming in general.| fsharpforfunandprofit.com
The "Computation Expressions" series| fsharpforfunandprofit.com
One of the most common complaints about F# is that it requires code to be in dependency order. That is, you cannot use forward references to code that hasn’t been seen by the compiler yet.| fsharpforfunandprofit.com
In this series, we’ll look at some of the ways we can use types as part of the design process.| fsharpforfunandprofit.com
The "Expressions and syntax" series| fsharpforfunandprofit.com
In this series of posts, I’ll look at how you might handle the common security challenge of authorization.| fsharpforfunandprofit.com
In this series of posts, I’ll look at how you can thread state through a series of pure functions in a convenient way.| fsharpforfunandprofit.com
As has been stressed many times before, F# is fundamentally a functional language at heart, yet the OO features have been nicely integrated and do not have a “tacked-on” feeling. As a result, it is quite viable to use F# just as an OO language, as an alternative to C#, say.| fsharpforfunandprofit.com
The "Optimization" series| fsharpforfunandprofit.com
The "Porting from C#" series| fsharpforfunandprofit.com
This series of posts will introduce you to the fundamentals of property-based testing: how it is different from traditional example-based testing, why it is important, and how to work with properties in theory and practice.| fsharpforfunandprofit.com
This is a very common question, so I thought that in this series of posts I’d describe a recipe for doing exactly this, covering design, validation, error handling, persistence, dependency management, code organization, and so on.| fsharpforfunandprofit.com
The "Thinking functionally" series| fsharpforfunandprofit.com
F# is not just about functions; the powerful type system is another key ingredient. And just as with functions, understanding the type system is critical to being fluent and comfortable in the language.| fsharpforfunandprofit.com
The "Understanding monoids" series| fsharpforfunandprofit.com
The "Why use F#?" series| fsharpforfunandprofit.com
In this series of posts, I’ll attempt to describe some of the core functions for dealing with generic data types (such as Option and List).| fsharpforfunandprofit.com
The "Understanding Parser Combinators" series| fsharpforfunandprofit.com