design-patterns

You should prefer modern C# language features over classical design patterns when a lightweight construct achieves the same goal. Use records, delegates, and dependency injection to keep solutions idiomatic and avoid over-engineering complex structural or behavioral implementations.

To choose the right C# design pattern for API design, evaluate whether a creational, structural, or behavioral pattern fits the integration scenario. Compare classical GoF patterns against modern alternatives like DI delegates and MediatR pipeline behaviors to ensure testable, simple architecture.

The best way to implement a runtime-selectable notification sender is by using dependency injection delegates or a factory pattern. This approach allows dynamic selection of notification mechanisms while maintaining loose coupling and testability in modern C# projects.

Yes, you can use MediatR pipeline behaviors to compose cross-cutting concerns as a modern replacement for the decorator pattern. This approach simplifies system integration by handling logging, validation, and routing centrally without wrapping individual service classes manually.

Use C# record types during refactoring to replace traditional builder or factory patterns because they provide built-in immutability and value-based equality. This reduces boilerplate code and simplifies data transfer object creation without over-engineering.

Refactoring state machines with enums simplifies C# system integration by replacing complex behavioral pattern implementations. Enum-based state machines provide clear, lightweight state transitions that are easier to read and maintain than traditional state pattern classes.