Code Freely, Live Fully
Code Freely, Live Fully
Introduction Rust’s ownership and borrowing system is a cornerstone of its safety guarantees, but it can present a challenge when you need to react to changes in your data. Imagine building a UI, a game, or any application where a…
Introduction The command pattern is a behavioral design pattern. It is used by an Invoker to perform one action or a series of actions on objects, called Receivers. The Invoker is unaware of the nature of the receiving objects, it just knows about…
Introduction The singleton pattern restricts the instantiation of a class to a single instance. The singleton pattern makes it possible to ensure that: One of the main uses of the singleton pattern is logging, as all clients who wish to…
Introduction The Decorator pattern can be used to dynamically alter or add functionality to existing classes. This pattern is oftern more efficient than subclassing because it relieves us of the need of defining a new object. So, what does it…
Introduction The Chain of Responsibility pattern describes a chain of command/request receivers. The client has no idea which one of the receivers will handle the request. The beauty of the pattern is again uncoupling: the sender and the receiver do…
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 Bridge pattern is a way to design software that helps you separate two main parts of a system: The goal is to keep these two parts separate so you can change one without affecting the other. Think of…
Introduction Go is known for its simplicity and clarity, but when it comes to managing state or creating reactive data flows, developers often have to write a lot of boilerplate. With the introduction of generics in Go 1.18, new patterns…
Introduction Delegation is like passing a job to someone else. For example, while performing a download from a file from the web, a delegate could handle the events, like starting the download, maintaining updates on the download’s progress, and handling…
Introduction Sometimes, to save time and resources, it’s handy to have a collection of ready-to-use items, which we call a “pool.” This is especially helpful for things that are costly to create, like database connections. Here’s the simple concept: You…
Introduction Most applications require business rules, such as data validation. It’s crucial to implement these rules in a way that’s flexible, clear, and easy to maintain. The Specification pattern offers a solution, allowing the creation of reusable business rules that…
Introduction The Singleton may be one of the most familiar design patterns. However sometimes it is necessary not have just one object of a certain type in your program, but several. That is when the Multiton comes in. The Multiton…
Introduction In delegation, you delegate a certain request to an object to a second object, which we call the delegate. This is almost like a subclass sending a request to its parent class. In Rust we can achieve this by…
Introduction The Abstract Factory Pattern is a way to group the creation of related objects, like products of a certain brand or make by building a common factory interface. If this all sounds abstract, a picture can help: A short…
Introduction In another article we discussed the Lock pattern. In this article we used the Mutex type. The problem with this type is, is that it doesn’t distinguish between reading from a resource, like accessing an element in a vector,…