It's code review and design time! Here's some refactoring to remove the usage of null and throwing exceptions.

DiscDot provides insights into distributed systems, cloud computing, and scalable architectures, offering articles and best practices for designing and implementing resilient and scalable distributed systems. By exploring DiscDot's curated content, developers can learn about distributed data storage, fault-tolerance mechanisms, and distributed computing frameworks for building highly available and performant applications. Whether you're architecting microservices, deploying containerized workloads, or managing distributed databases, DiscDot offers  insights and practical guidance to help you tackle the challenges of building distributed systems.

Discover .NET

The article discusses code review and refactoring to improve design. It addresses design decisions related to persistence ignorant queries, the usage of null, and throwing exceptions. It suggests using option types instead of null and exceptions for handling invalid values.

Code Review & Refactoring to a Better Design

<p>Very instructive, I really like the final design improvement</p>


<p>Option&lt;T&gt; is a monad which makes it composable. However, for some reason almost all uses in C# I see in the wild - like here - is a glorified way to represent a missing return value. With nullable reference types there’s good support for that in the C# type system - just annotate your type to indicate that it can be null. Until you start using the composability of Option&lt;T&gt; it doesn’t really add any value in my opinion.</p>
