4 ms·
Most of the time I would precisely give the opposite advice. That's especially true if I had to deal with a large and/or legacy codebase. It only really works
by thibaut_barrere 16y ago
Most of the time I would precisely give the opposite advice. That's especially true if I had to deal with a large and/or legacy codebase.
It only really works if applied equally at all levels of the codebase.
- Semiapies 16y agoThat's a good practice in many languages and systems. It's a bit different here, as the standard way to handle things in Erlang (as I understand it) is for the function involved to crash, an error log to be made, and then the program to restart, usually seamlessly. Linking this rule without discussion, context, or explanation is basically useless.
- thibaut_barrere 16y agoThanks for giving more context actually - this totally makes sense.