hrowing exceptions is often used to handle errors, validations, and other specific use cases. It is considered by many to be the standard way of indicating a failure and providing feedback to the caller. However, this approach can cause significant issues like being hard to detect, obfuscating the flow or leaving the system invalid.
In this talk, I want to show you a faster alternative that offers more transparency and predictability. We will see how to integrate ideas from the Functional paradigm, such as "Monads", into an Object-Oriented codebase using a real-life project: Vonage's open-source .NET SDK. This talk will be the perfect opportunity to show you what they are and how easy they are to use.


It's all about sharing an alternative to exceptions when it comes to error handling: Monads. The purpose is to explain what they are and how we can use them. C# has a feet in both the OOP and Functional paradigms - this flexibility allows us to leverage benefits from both paradigms.
Of course, it isn't a theorical talk - it's a technical one which relies on a lot of code, and I'm using my current open-source project (the Vonage .NET SDK) to explain everything. Everything I say can be verified by the audience afterwards.
Here's the structure of the talk:
- Downsides of exceptions
- Build our own monad step-by-step using an example from quantum mechanic
- What Monads bring to the table
- Monads in the real world, in a real solution