Code Freely, Live Fully
Code Freely, Live Fully
Introduction In modern C# development, we often find ourselves lost in “If-Else” chains, nested blocks of null checks and error handling which can obscure the actual business logic. Inspired by Rust and functional programming, the Esox.SharpAndRusty library introduces a way…
Introduction In tradition .NET development, error handling often falls into two camps: throwing heavy exceptions for flow control or returning vague string error messages which lose all context by the time they reach the logger. The Esox.SharpAndRusty library introduces a…
Introduction In the world of C# we have been trained to treat errors as occurring under exceptional circumstances, or exceptions if you will. We throw exceptions like stones, hoping someone further up the in the call chain is waiting with…
Introduction You can build applications in many ways. One way to do this is using actors. In this setup, an actor is the ‘primitive’ of the appliction. Actors have a number of important characteristics namely: Implementation in C# with SharpAndRusty…
Introduction As some of you may know, I love working with C#, as it seems to get better with every iteration, but I also love Rust, because of its safety and its performance. Rust has something that C# sorely misses,…
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…