---
title: "Discussion on \"Code Smell 135 -  Interfaces With just One Realization\" | Hashnode"
description: "Discussion on \"Code Smell 135 -  Interfaces With just One Realization\". Being generic and foreseeing the future is good."
url: "https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Code Smell 135 - Interfaces With just One Realization](https://maximilianocontieri.com/code-smell-135-interfaces-with-just-one-realization?utm_source=hashnode&utm_medium=feed)

Being generic and foreseeing the future is good.

May 26, 2022 · 2 min read · maximilianocontieri.com  
Updated May 30, 2022  
Read the article

-   [#programming-blogs](https://hashnode.com/tag/programming-blogs)
-   [#programming](https://hashnode.com/tag/programming)
-   [#clean-code](https://hashnode.com/tag/clean-code)
-   [#code-smell-1](https://hashnode.com/tag/code-smell-1)
-   [#object-oriented-programming](https://hashnode.com/tag/object-oriented-programming)

## Written by

[Maxi Contieri](https://hashnode.com/@mcsee)

@mcsee · Buenos Aires

  
[View profile](https://hashnode.com/@mcsee)

Software Engineer

I’m a senior software engineer loving clean code, and declarative designs. S.O.L.I.D. and agile methodologies fan.

## Responses 4

Markdown supported · ⌘↵ to post

[Cesar Kohl](https://hashnode.com/@cesarkohl)

[May 26, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f694f8826d59c309db8ea)

Agreed!

[Tapas Adhikary](https://hashnode.com/@atapas)

[May 26, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f35ce43220290a7eec318)

Great article.

[Maxi](https://hashnode.com/@mcsee), let it go to 1K(articles from this series)

[Maxi Contieri](https://hashnode.com/@mcsee)

[May 26, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f35ce43220290a7eec318#reply-629007698826d59c309dc896)

Let's stress test Hashnode platform :)

[Davide Bellone](https://hashnode.com/@davidebellone)

[May 26, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f273719bda58ac7fb25d7)

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](https://hashnode.com/@mcsee)

[May 27, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f273719bda58ac7fb25d7#reply-62914931d97f80b5091d82ee)

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

[Miki Szeles](https://hashnode.com/@mszeles)

[May 26, 2022](https://hashnode.com/posts/code-smell-135-interfaces-with-just-one-realization/628eea5b19bda58ac7fb1f45/comment/628f0fd619bda58ac7fb22b6)

Great article again, Maxi. I love your series. 😊
