Recent posts tagged designpatterns

We live in a time when artificial intelligence has moved from being an emerging technology to a critical infrastructure. Algorithms decide what information we see, what transactions are suspicious, what diagnoses are likely, and increasingly, what de...

Five small details that make a short url feel clearer, safer, and more memorable A short link is not automatically a good link. Removing characters from a URL solves a length problem, but it does not answer the questions people ask before clicking:...

What is Dependency Injection? Dependency Injection is a software design pattern where a program component receives the external resources or tools it needs to function from the outside, rather than creating them itself. In simpler terms, instead of...

Go makes concurrency feel easy. Goroutines are cheap, channels are built into the language, and the standard library gives you everything you need to spin up a worker pool in under 30 lines. That ease is genuinely valuable — but it also means bugs sn...

Go Interfaces: Why Less Is Almost Always More If you’re coming to Go from Java or C++, interfaces look familiar at first glance. You define a set of methods, types implement them, you write code against the interface. Same idea, right? Not quite. ...

Introduction The Prototype Design Pattern is a creational design pattern that allows new objects to be created by copying an existing object called a prototype instead of creating them from scratch. This pattern is particularly useful when: Obje...

Exploring a Practical Billing API Built with Modern .NET Patterns The Billing repository https://github.com/stevsharp/Billing is a practical example of how several common .NET architectural patterns can be combined within a billing-focused applicat...

I published an article diving into the reflection architectural pattern. If you've ever wondered how Spring Boot uses annotations to magically wire your dependencies, or how ORMs map database fields without explicit code, reflection is the answer. I ...

Refactoring a Simple C# Method Step by Step Refactoring is not about changing what the code does. It is about improving how the code is written. The goal is to make the code easier to read, easier to test, and easier to maintain. In this tutorial...

Understanding the Producer-Consumer Pattern in C Sharp The Producer-Consumer pattern is one of the most common patterns in concurrent programming. In simple English, it means this: One part of the program creates work. Another part of the program...

Are you a Laravel developer. Do you love Blade. It’s simple, expressive, and fits naturally with the framework. But let’s be honest, most projects eventually turn their Blade files into dumping grounds for random variables. The Controllers pass loose...

When I started my career as a developer, one of my senior team members used to construct queries in core PHP using concatenation based on different parameters. Once the construction was complete, he would echo it for different use cases and run it in...

While building a vibe coding platformhttps://jigjoy.ai/spektrum, I started building Mozaikhttps://jigjoy.ai/mozaik, a library for working with LLMs. Very soon, a need emerged to handle multiple LLM providers - and with that, different request and res...

I tend to think of reporting and production as incompatible roommates. They need the same space, they optimize for completely different things, and every accommodation one makes for the other is a debt that gets called in later. The production schema...

I have been a part of a dev team where poor observability constantly brought us to a standstill. Not because the tooling was missing, but because the data it collected never carried meaningful context. Alerts fired constantly, so operations teams ign...

This is a highly opinionated take on shared libraries and the damage they do to team autonomy and development tempo. Teams deliver value faster and more consistently when they can make decisions, ship changes, and evolve their domains without coordin...

About 8 years ago I came across the Chain of Responsibility pattern. I remember I was genuinely happy when I understood it, because all those long if / else if / else blocks suddenly felt unnecessary. Instead of one method trying to decide everythin...

Carter in a CQRS API, advantages and alternatives. In this project I wanted the API layer to stay small and structured. I like minimal APIs, but I don’t like having 200 endpoints inside Program.cs. That’s why I used Carter, it keeps the minimal API...

Systems that stay cheap to change for years aren't the ones built to fit today's requirements perfectly. They're the ones that bend without breaking when requirements shift, technologies evolve, and teams discover what they didn't know upfront. Build...

The tech stack I used and why updated, with Repository and Unit of Work This project is small, but I wanted it to feel like a real API you can extend. The repository is here: https://github.com/stevsharp/ChainOfResponsibilityWithMediatR Carter f...