TLDR
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.via the TL;DR App
no story
Written by mcsee | I’m a sr software engineer specialized in Clean Code, Design and TDD
Book "Clean Code Cookbook"
500+ articles written
