---
title: "Comment by Markos Korvesis on \"Code Smell 156 - Implicit Else\" | Hashnode"
description: "Hey Maxi Contieri , good article! I feel, however, that the wrong vs. right cases you provided are not comparable with each other. The &quot;wrong&quot; example"
url: "https://hashnode.com/posts/code-smell-156-implicit-else/62eea0e4ba649046e8d8dbfa/comment/62fea7bff1a220fcdbb6553d"
---

[Discussion](https://hashnode.com/posts/code-smell-156-implicit-else/62eea0e4ba649046e8d8dbfa)

Comment [Code Smell 156 - Implicit Else](https://hashnode.com/posts/code-smell-156-implicit-else/62eea0e4ba649046e8d8dbfa)

[Markos Korvesis](https://hashnode.com/@MarkosK)

[Aug 18, 2022](https://hashnode.com/posts/code-smell-156-implicit-else/62eea0e4ba649046e8d8dbfa/comment/62fea7bff1a220fcdbb6553d)

Hey [Maxi Contieri](https://hashnode.com/@mcsee), good article!

I feel, however, that the wrong vs. right cases you provided are not comparable with each other. The "wrong" example is an if/else and the "right" one is an if/else-if/else.

Implicit "else" seems fine to me when the "if" body is surrounded by curly braces, if not then I'd prefer a ternary return assuming there would only ever be two cases.

From my point of view, the most important takeaway is the suggestion to give up on the if/else\* block altogether and replace it with polymorphism.
