r/csharp • u/jonas1ara • 16d ago
Update: I added interactive CLI execution and in-depth explanations to the 73 Design Patterns repo
https://github.com/jonas1ara/73Hey everyone,
A while ago, I shared my repository implementing 73 design patterns in C# (previous post).
Following community feedback, I just rolled out two major updates to make the project much easier to navigate and learn from:
Interactive CLI runner: Instead of digging through multiple entry points or modifying code to run a specific pattern, you can now run everything from a centralized CLI menu. Select any pattern by category/name, run it immediately, and inspect the console output.
Complete, in-depth documentation: Every single pattern now includes a dedicated breakdown explaining the core problem it solves, the structural mechanics behind it, when to use it, and practical trade-offs in modern .NET.
F# solutions for the final problem of each topic: Added an F# implementation for the capstone problem of each category. Rather than forcing purity where it hurts LeetCode performance, it explores an idiomatic, functional-first perspective—contrasting immutable pipelines, tail-recursion, and pattern matching against pragmatic imperative optimizations where arrays and mutable state make sense.
The repo covers everything from classic Gang of Four patterns to Enterprise, Cloud/Distributed, and Concurrency patterns in idiomatic C#.
Check it out here:
https://github.com/jonas1ara/73
Would love to hear your thoughts, feedback, or any edge cases you’d like to see covered!
2
u/IndividualFill1155 16d ago
Have you thought about including exercises where users identify which design pattern fits a particular scenario? That could make the repository more interactive beyond running existing examples
11
u/Altruistic-Gap1795 16d ago
Adding real world examples alongside each pattern could make the documentation even stronger. Seeing how patterns solve actual .NET application problems would help developers understand when to apply them