Two customers, same plan, same start date, different invoice. Why business rules that change over time need their own binding policy, not one shared effective date — and why changing a rule isn't finished until someone decides what happens to the customers already bound to the old one.

Forecasting pension rights across 42 legal regimes over 40 years causes combinatorial explosion. Hexagonal architecture isolates the policy core for testability.

Null reference exceptions are C#'s billion-dollar mistake. The Maybe Monad, borrowed from functional programming, offers a safer way to handle absent values.

Why relying on raw strings, ints and bools instead of dedicated types, Primitive Obsession, makes C# code fragile, and how to replace them with value objects.

A deep dive into how EF Core maps C# entities to database tables, conventions, Data Annotations, and Fluent API, and when to reach for each.

Task.ContinueWith gets messy for chained async C# calls. Then and Catch extension methods bring Promise-like fluency and cleaner error handling.

How to containerize a Jekyll site with Docker, a Dockerfile plus build and run commands that remove the local Ruby and dependency setup hassle.

Replace long chains of OR comparisons in C# with a generic In extension method, plus an IEqualityComparer overload for custom equality checks.

A mindmap summary of Robert C. Martin's Clean Code, the book's key ideas distilled into one visual reference for writing more maintainable code.

Zakaria SMAHI introduces this blog, notes from a senior .NET engineer on architecture, SQL Server, Azure DevOps, and the technical books worth reading.