Domain Driven Design, F# and Types

Want to find out ways you can use types as part of a domain driven process? With real world examples in F#, come along to this no jargon, no maths, no prior F# experience necessary event.

Statically typed functional programming languages like F# encourage a very different way of thinking about types. The type system is your friend, not an annoyance, and can be used in many ways that might not be familiar to OO programmers.

Types can be used to represent the domain in a fine-grained, self documenting way. And in many cases, types can even be used to encode business rules so that you literally cannot create incorrect code. You can then use the static type checking almost as an instant unit test — making sure that your code is correct at compile time.

YOU MAY ALSO LIKE:

• Gojko Adzic's Impact Mapping Workshop (in London on 27th September 2017)
• Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 1st - 3rd November 2017)
• Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 7th - 8th November 2017)
• Agile Testing & BDD eXchange 2017 (in London on 9th - 10th November 2017)