Software-Design

Quick Reference Table Feature Abstract Class Interface When to Use Inheritance Single only Multiple allowed Abstract: shared logic; Interface: contracts Implementation Can provide Contract only Abstract: code reuse; Interface: flexibility Constructors Supported Not allowed Abstract: initialization; Interface: pure contracts State/Fields Yes No Abstract: data sharing; Interface: behavior only Performance Slightly faster Virtual dispatch Abstract: hot paths; Interface: most scenarios Testing Can be difficult Easy with mocks Abstract: integration tests; Interface: unit tests Common Pitfalls: ...

TL;DR: Immutable objects can’t be changed after creation. In C#, this can make your code safer, easier to test, and bug-resistant, especially in multithreaded or async scenarios. Have you ever had a bug where some object mysteriously changed its value? Or spent hours debugging a weird race condition? Immutability might be the solution you need. In simple terms, immutable objects can’t be changed after they’re created. Instead of modifying an existing object, you create a new one with the updated values. It’s like the difference between editing a document and making a new copy with your changes. ...

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! ...