paint-brush
Fail Fast Philosophy, Explained by@mcsee
904 reads
904 reads

Fail Fast Philosophy, Explained

by Maximiliano Contieri7mMay 26th, 2020
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

The best way to fail fast is to properly represent objects while being faithful to our only design rule: A misrepresentation of a geographic coordinate using an array with twointegers is not going to “defend” itself from possible invalid situations. Most of “modern” languages ‘hide the dirt under the carpet’ and allow “continue (as if nothing happens)” the execution so that we have to debug the cause of the problem with logs in order to carry out a forensic analysis.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - Fail Fast Philosophy, Explained
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.
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