How to Find The Stinky Parts of Your Code [Part XIII]by@mcsee

How to Find The Stinky Parts of Your Code [Part XIII]

tldt arrow
Read on Terminal Reader

Too Long; Didn't Read

The code smells are just hints of something that might be wrong. They are not rigid rules. Use interfaces or traits (if available) to solve problems. Use Dependency Injection (if possible) or use interfaces (if not) The code smell is not bad luck, but it's just hints that something is wrong. The smell of code smells is a symptom of a problem in software development. We can call and invoke classes any time. We can't fake or mock this method since it always expects an instance of MyCollection to be called.

Company Mentioned

Mention Thumbnail
featured image - How to Find The Stinky Parts of Your Code [Part XIII]
Maximiliano Contieri HackerNoon profile picture

@mcsee

Maximiliano Contieri

About @mcsee
LEARN MORE ABOUT @MCSEE'S EXPERTISE AND PLACE ON THE INTERNET.
react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!
Hackernoon hq - po box 2206, edwards, colorado 81632, usa