Software Patterns

A decision framework that tells you which architectural patterns to apply and when, covering the foundational ones (Dependency Injection, SOA) and situational ones (Repository, Domain Events, Circuit Breaker, Anti-Corruption Layer). The philosophy is problem-first: it gives you decision trees based on specific pain points like "code is hard to test" or "one slow service breaks everything" rather than pattern catalogs to memorize. Useful when designing new systems, adding integrations, or refactoring existing architecture. The best part is the explicit anti-YAGNI warnings, like stopping you from adding patterns preemptively or cargo-culting "best practices" without understanding what problem they solve.