About the service
I'm an F# developer and I write server services in a functional style on the dotnet platform. F# for me is not a side language I picked up casually, but a way of thinking about programs. Instead of mutable state and defensive checks scattered throughout code, I model the domain with immutable records, discriminated unions and pattern matching — so whole classes of errors simply cannot be expressed. The result is code that's short, readable and much easier to understand than the equivalent object-oriented solution.
My focus is exactly backend: web APIs, message and event handlers, background workers and the data pipelines that feed them. For me type-safe domain modeling matters, the principle of "impossible state is unrepresentable" and working with the compiler as an ally, not an obstacle. I try to write pure functions, push side effects to system boundaries and cover complex logic with modular and property-based tests so behavior stays predictable as the project grows. When performance matters, I profile first then optimize.
This pitch is specifically about functional programming: if you need someone who reaches for F# and functional design first, not a generalist in C#, Haskell or Scala, we'll work well together. I'm equally comfortable joining an existing dotnet solution and starting a service from an empty folder, leaving your team maintainable code.
— Functional backend and web APIs in F#
— Type-safe domain modeling: records, unions, pattern matching
— Data pipelines, ETL and stream and event processing
— Modular and property-based testing for correctness
— Refactoring imperative code toward functional core
My focus is exactly backend: web APIs, message and event handlers, background workers and the data pipelines that feed them. For me type-safe domain modeling matters, the principle of "impossible state is unrepresentable" and working with the compiler as an ally, not an obstacle. I try to write pure functions, push side effects to system boundaries and cover complex logic with modular and property-based tests so behavior stays predictable as the project grows. When performance matters, I profile first then optimize.
This pitch is specifically about functional programming: if you need someone who reaches for F# and functional design first, not a generalist in C#, Haskell or Scala, we'll work well together. I'm equally comfortable joining an existing dotnet solution and starting a service from an empty folder, leaving your team maintainable code.
— Functional backend and web APIs in F#
— Type-safe domain modeling: records, unions, pattern matching
— Data pipelines, ETL and stream and event processing
— Modular and property-based testing for correctness
— Refactoring imperative code toward functional core
