Discussion on "Code Smell 135 - Interfaces With just One Realization"

Maxi Contieri · 2022-05-26T02:47:55.606Z

TL;DR: Don't over-generalize Problems Speculative Design Complexity Over-Engineering Solutions Remove the interface until you get more examples Context In the past, programmers told us to design for change. Nowadays, We follow the scientific...

Discussion on "Code Smell 135 - Interfaces With just One Realization" | Hashnode

Davide Bellone

Principal backend developer | Content Creator | Microsoft MVP

May 26, 2022

What do you think of interfaces implemented by only one class, when that class represents a Service and not a DTO?

Something like

public interface IDoSomething{
void Do();
}

public class DoSomething : IDoSomething{
void Do();
}

Maxi Contieri

Software Engineer

May 27, 2022

IDoSomething is a name problem. I've never seen an IDoSomething in real world. I assume it is a bad convention.

If this a service provided as an API interface for other systems it might suit the Exceptions scenario.

If it is for internal use is a code smell on premature generalization

Search Hashnode

Code Smell 135 - Interfaces With just One Realization

Responses(4)