Tackling property data with readable code
summary
Built a property-tax system for Norwegian municipalities using F# on .NET and Event Sourcing, storing ~dozens of domain events per property to reconstruct state and audit every change. Uses pattern matching, small pure functions and a durations library to handle overlapping valuation periods and messy legacy data. Tests favor isolated domain unit tests with minimal mocking and verify snapshot testing for large outputs, and uses Norwegian domain names for clarity; maintainability and onboarding measurably improve.
AI-written summary · about
chapters (10)
- 0:00Property data and readability
- 2:39Code readability factors
- 12:37Isolating domain logic
- 15:32F# for domain development
- 22:30Bilingual code precision
- 25:06Event sourcing traceability
- 30:28Breaking down domains
- 34:50Testing readable F# code
- 40:00Key learnings
- 45:51Q&A
related talks
46mTesting in the world of Functional Programming
52mDomain Modeling Made Functional
01h 06mFunctional Design Patterns
48mMake your tests tell the story of your domain
56mProperty based Testing for Functional Domain Models
36mIntroduction to stateful property based testing
55mF# and Fable: re-think web development
21mProperty-based testing - let your testing library work for you
