Code Freely, Live Fully
Code Freely, Live Fully
Introduction Sometimes, it’s handy to separate when a method is called from when it actually runs. That’s where the Active Object design pattern comes in. It lets us build more flexible and concurrent systems. One key feature is that each…
Introduction When we build programs that do many things at once, we want to make sure they’re secure. Go is a modern language that is really good at keeping things safe in memory but still works really fast. One big…
Introduction The Servant pattern is a way of organizing code where one special object helps out a bunch of other objects. This helper object provides some functions to these objects, so they don’t have to do the same things over…
Introduction The composite pattern allows you treat a group of objects like a single object. The objects are composed into some form of a tree-structure to make this possible. This patterns solves two problems: We do this by doing the…
Introduction The observer pattern is a software design pattern that allows an object, usually called the subject, to maintain a list of dependents, called observers, and notify them automatically of any state-changes. Many languages have this pattern either built-in or…
Introduction You can use the memento pattern to (partially) expose the internal state of an object. One use case for this pattern is to serialize an object to a file or as JSON for example, another is to build an…
Introduction In Design Patterns, the Iterator is a way of traversing over a container, that is access each of the container’s elements. It is used as a convenient way to traverse over lists or arrays, but it could also be…
Introduction The flyweight pattern is a pattern that helps minimize memory usage by sharing and reusing data. A common example is wordprocessor where each character not only holds the character like ‘A’ but also things like markup and formatting data.…
Introduction The Interpreter pattern can be used to interpret and evaluate sentences in a language. The idea is to make a class for each symbol, both terminal and non-terminal and construct a syntax tree which can be evaluated and interpreted.…
Introduction The facade pattern is used as a way to hide more complex logic. A facade can do the following: A facade pattern is typically used in the following cases: This might all sound quite complex, here is what it…
Introduction In Part 1 and Part 2, we established the core principles of using Result<T, E> for type-safe error handling and demonstrated how to compose operations using Map, Bind, and the LINQ query syntax. Modern C# development is dominated by…
Introduction The C# ecosystem has long relied on exceptions for signaling failure. While exceptions are powerful for truly exceptional, unexpected conditions (like a lost network connection or a corrupted file), using them for expected failure modes—such as user input validation…
Introduction: Bye-Bye Exceptions, Hello Type Safety 👋 Welcome to the first part of our series on Esox.SharpAndRusty, a C# library designed to bring the safety and clarity of Rust’s Result<T, E> type to the modern .NET ecosystem. In traditional C#…
Introduction As C# developers, we have all been there. You are calling a method like GetUser(id), and you wonder: does it return null if the user is not found? Or does it throw a NotFoundException? Or perhaps even and InvalidOperationException?…
Introduction In this article I discussed the implementation of the Abstract Factory pattern. The Factory Method is simply an extension of that pattern. Creating an object can sometimes be complex. A factory-method can abstract this complexity away, and let subclasses…