How to Find The Stinky Parts of Your Code [Part XII]by@mcsee
498 reads

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

tldt arrow
Read on Terminal Reader🖨️

Too Long; Didn't Read

There are 56 code smells that make us doubt the quality of our development. Most of these smells are just hints of something that might be wrong. We want our code to behave different on different environments, operating systems, so taking decisions at compile time is the best decision, isn't it? We need clean code and we must leave premature optimization buried in the past. We need to remove all compiler directives, model it with objects, make a serious benchmark instead of doing premature optimization. This technique was used when CPU were scarce, and nowadays, we need to leave it buried in past.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - How to Find The Stinky Parts of Your Code [Part XII]
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