The third entry in the ValueObjects series. This one tackles validation — instead of scattering range checks across every function that touches a value, you push the constraints into the constructor. If the object exists, it’s valid. The post ties this back to the Curry-Howard Correspondence: making illegal states unrepresentable through the type system.
Read the full post on Benevity Tech Blog →✶