CodeOpinion: You Don’t Need an Interface for Everything

You’ve probably noticed services like IOrderService, IEmailService, IPaymentService popping up everywhere—even when there’s only one implementation. This piece argues that most interfaces are just pointless boilerplate, only earning their keep when you actually swap implementations or need fancy mocking for tests. It also traces this habit back to how Dependency Injection is taught in the .NET world.

Instead of throwing interfaces at every class, consider lighter-weight alternatives like delegates or overrides (or just good old comments) to keep your code cleaner and more maintainable. You’ll learn where interfaces truly shine and how to ditch the rest for a leaner codebase.

Watch on YouTube