Code Smell 241 - Referential Transparency Violationby@mcsee

Code Smell 241 - Referential Transparency Violation

by Maximiliano Contieri2mMarch 3rd, 2024
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

Pure functions ensure consistent output for the same input, without causing side effects. Embrace functional programming principles to write maintainable, readable, and testable code.
featured image - Code Smell 241 - Referential Transparency Violation
Maximiliano Contieri HackerNoon profile picture
Maximiliano Contieri

Maximiliano Contieri

@mcsee

I’m senior software engineer specialized in declarative designs and S.O.L.I.D. and Agile lover.

About @mcsee
LEARN MORE ABOUT @MCSEE'S
EXPERTISE AND PLACE ON THE INTERNET.

STORY’S CREDIBILITY

Guide

Guide

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

L O A D I N G
. . . comments & more!

About Author

Maximiliano Contieri HackerNoon profile picture
Maximiliano Contieri@mcsee
I’m senior software engineer specialized in declarative designs and S.O.L.I.D. and Agile lover.

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite