MAMario Alberto Arceinpowercsharp.hashnode.dev·Sep 2 · 6 min readThe Cache FamilyProblem .NET already gives you IMemoryCache and IDistributedCache. Both are well-designed for what they are. Neither is an application-level abstraction — they're platform abstractions, and your servi00
MAMario Alberto Arceinpowercsharp.hashnode.dev·Aug 21 · 5 min readThe Features FrameworkProblem A feature flag library answers one question: is this feature enabled? It doesn't answer the question that actually matters in a real application: what happens to dependency injection when the 00
MAMario Alberto Arceinpowercsharp.hashnode.dev·Aug 18 · 7 min readFoundation: Core, Extensions, Utilities, Helpers, CompatibilityProblem For most of twenty years across .NET Framework 1.1 through .NET 8, I wrote the same handful of things in every codebase: a null check before a string operation, a DayOfWeek comparison to detec00
MAMario Alberto Arceinpowercsharp.hashnode.dev·Jul 14 · 7 min readWhy I Built a Feature Module Engine — and Why Feature Flag Libraries Weren't EnoughThe Problem Three years ago, I was building a CORS policy module for a library that would be consumed by teams I didn't control. The infrastructure team wanted to control activation via environment va00
MAMario Alberto Arceinpowercsharp.hashnode.dev·Jul 3 · 5 min read100+ Extension Methods: When Breadth Is a Design Decision, Not a MistakeThe Problem Every enterprise C# codebase I have worked in has a StringHelper.cs. Or a DateTimeUtils.cs. Or an Extensions folder with 47 files and no discernible organization principle. The code works.00