Functional programming in F# Fad or Fabulous
summary
A runnable drone-tracking demo shows F# integrated with .NET: Wolverine for HTTP and messaging, Entity Framework for storage, and NUnit/XUnit for tests; code uses computational expressions (let! await), piping and railway-oriented programming to validate flights and reject collisions. Notable specifics: ID fields use CLI mutable for EF, discriminated unions require JSON serialization (Newtonsoft works reliably), and messages need a generic envelope to cross C# buses. The demo compiles and the workflows execute end-to-end.
AI-written summary · about
chapters (13)
- 0:00🚀 Build Stuff Conference – Get Your Tickets!
- 0:30Introduction: F# – Fad or Fabulous?
- 3:10What is F# and Why Consider Functional Programming?
- 6:20Functions, Values, and Type Inference
- 10:10Building a Simple API with F# and Wolverine
- 14:00Immutability and Working with Data Models
- 17:30Discriminated Unions: Modeling States and Outcomes
- 22:00Pattern Matching and Safer Logic Flows
- 26:10Computational Expressions Explained
- 29:20Piping and Building Readable Workflows
- 32:40Railway-Oriented Programming and Validation
- 36:00Real-World Challenges: EF, Serialization, and Messaging
- 39:00Unit Testing and Final Thoughts on F#
related talks
01h 14mFunctional Programming in F#: Fad or Fabulous?
01h 00mFunctional-first programming with F#
58mWhy you should use F#
01h 09mFunctional Programming with C#
58mFunctional Programming with C#
01h 07mPipe forward : Using Elixir and F# together
01h 08mWhy Every Day as a Developer Would Be Easier with F#
01h 01mF# as a Better Python