Welcome to the Lounge

public interface ISomething { ... }
public class Something : ISomething { ... }

// Scattered throughout the code:
ISomething something = new Something();

// But then also:
public Whatever DoSomeCalculations(Something something) { ... }

Ravi Bhavnani wrote:

That's one of the tenets of dependency injection because it makes for a testable and extensible design

Ravi Bhavnani wrote:

That's one of the tenets of dependency injection because it makes for a testable and extensible design.

Ravi Bhavnani wrote:

It's basic software engineering, not rocket science or a buzz word.

1. Contractual obligation Interfaces define a contract that classes must adhere to. By requiring a class to implement an interface, you ensure that it provides specific functionalities or behaviors as defined by that interface. This promotes consistency and predictability in your codebase.
   
   
2. Polymorphism Interfaces enable polymorphic behavior in C#. When a class implements an interface, instances of that class can be treated as instances of the interface. This allows for greater flexibility in designing systems where different objects can be used interchangeably based on their common interface.
   
   
3. Code reusability By implementing interfaces, classes can share common functionality without being directly related in terms of inheritance. This promotes code reuse and modular design, as multiple classes can implement the same interface to provide similar behavior.
   
   
4. Decoupling and DI Interfaces facilitate loose coupling between components. Code that depends on interfaces is not tied to specific implementations, making it easier to change or extend functionality without affecting other parts of the codebase. This also enables dependency injection, where objects are passed into a class via interfaces, allowing for easier testing and maintenance.
   
   
5. Design patterns Interfaces are integral to many design patterns such as Strategy, Observer and Factory. Requiring classes to implement interfaces enables the use of these patterns, leading to more maintainable and scalable code.
   
   
6. Documentation and readability Interfaces serve as documentation for the expected behavior of classes. When a class implements an interface, it's clear what functionality it provides without needing to inspect the implementation details ("what vs. how"). This improves code readability and makes it easier for devs to understand and work with the codebase.
   

Ravi Bhavnani wrote:

and bug counts.