design patterns - bencope.land

bencope.land

design patterns

A collection of 9 posts

F# Discriminated Unions with SQL Enumerations

💡This post is part of F# Advent Calendar 2024. Having worked extensively with both C# (including Entity Framework) and F#, I've found that F# allows us to elegantly model the business domain while seamlessly bridging the gap between code and database. In this post, I'll outline

design patterns

YAGNI and Building Good Practices into Your Architecture

In software development, the mantra “You Aren’t Gonna Need It” (YAGNI) serves to keep projects lean, avoiding features or complexity until absolutely necessary. But over my 16 years in development, I’ve noticed that when it comes to architecture, this mindset often backfires. Certain patterns - like asynchronous programming,

Empathy in Software Design

Designing for Real Life One of the books that have been most influential on my thinking in software design was not a book on technical design patterns or theory, but a book called Design for Real Life by Eric Meyer and Sara Wachter-Boettcher. The book talks about designing your software

Adaptability

In software development, the lure of the latest fad can be intoxicating. Whether it's an influential thought leader extolling the virtues of their favorite project management methodology, or the notion that enterprise software must be built with the hot language or framework, it's easy to find

Mapping Database Values to Discriminated Unions for Domain-Driven Design

Let's explore two strengths of F# and their application in a typical enterprise app, using an example that is relevant to any subscription-based service - working with a user's subscription status in both the code and the database. The first strength is it's focus

Abstraction

💡My thinking around this topic is influenced by Eric Normand's Lispcast episode on abstraction. Check it out, and his podcast. Abstraction is a common topic in programming discussions. You hear a lot about the right abstraction, the wrong abstraction; this level of abstraction or that level; leaky ones,

functional programming

Functional Reactive Programming

There's something about FRP specifically that makes programming an absolute pleasure. Designing an elegant reactive application is a great feeling and opens you're mind to just how rewarding it can be to focus on decoupling. Thinking in reactive (message driven) streams has clear benefits between multiple

design patterns

Demystifying Design Patterns

Often times I find it beneficial to look outside of one's own industry for inspiration. There is often a lot of practical wisdom to be gained from areas that seem unrelated to our own domain, and possibly even similar problems that have already been solved. This has proven

game development

Throwaway Code

Sometimes we write code that we know will be thrown away - especially in the discovery phase of a feature or product. The problem is, often circumstances cause this sort of code to be shipped. I imagine a fair amount of cursing under one's breath the previous developer