Refactoring Messy Code: My Approach to Coupling and Cohesion

TL;DR: High cohesion means classes focus on one job. Low coupling means classes don’t depend too much on each other. When I refactor messy code, these two principles guide every decision I make. Why I Focus on Cohesion and Coupling When Refactoring After 10+ years of building enterprise applications, I’ve inherited my fair share of messy codebases. The pattern is always the same: tangled classes doing too much, components that break when you touch something seemingly unrelated, and tests that require half the application to run. ...

August 4, 2025 · 7 min

Polymorphism in C#: How Template Method, Strategy, and Visitor Patterns Make Your Code Flexible

Polymorphism isn’t just a language feature, it’s a way to build systems that are easier to extend, change, and maintain. Learn how polymorphism powers design patterns like Template Method, Strategy, and Visitor in C#.

July 16, 2025 · 5 min

How Does Composition Support the SOLID Principles? (C# Examples & Best Practices)

Discover how composition helps you follow the SOLID principles in C#. See practical examples for each principle, learn why composition is more flexible than inheritance, and get actionable tips for writing robust, testable, and maintainable code.

June 30, 2025 · 4 min

Composition Over Inheritance in C#: Write Flexible, Maintainable Code

Discover why composition is often a better choice than inheritance in C#. This article explains the drawbacks of deep inheritance, demonstrates how to use composition for flexible and maintainable code, and provides practical tips for applying these principles in real-world projects. Includes code examples and guidance for testable, scalable software design.

June 29, 2025 · Last modified: July 16, 2025 · 12 min

DIP vs DI vs IoC: Understanding Key Software Design Concepts

TL;DR: DIP (Dependency Inversion Principle): High-level modules should not depend on low-level modules; both depend on abstractions. DI (Dependency Injection): A technique to supply dependencies from outside a class, improving testability and flexibility. IoC (Inversion of Control): A broader concept where control of object creation and dependency resolution is delegated to a container or framework. Together, they enable decoupled, maintainable, and testable applications. DIP is a design principle, DI is a pattern, IoC is the overarching concept. Introduction If you’ve ever been in a job interview for a software developer position, chances are you’ve been asked to explain the difference between DIP, DI, and IoC. I know I have, and the first time I was asked, I definitely stumbled through my answer! ...

June 20, 2025 · Last modified: July 26, 2025 · 13 min
×