Fail Fast Philosophy, Explained by@mcsee
898 reads

Fail Fast Philosophy, Explained

May 26th 2020
7m
by @mcsee 898 reads
tldt arrow
Read on Terminal Reader
Read this story w/o Javascript

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

@mcsee

Maximiliano Contieri

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


Receive Stories from @mcsee

react to story with heart

RELATED STORIES

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