Become a member
Sign in
Sébastien VARLET
Sébastien VARLET

Sébastien VARLET

4 Following
3 Followers
·
  • Profile

  • Claps

  • Highlights

Highlighted by Sébastien VARLET

See more

From Exceptional: Freedom from {:error}s by Brooklyn Zelenka

Yes, there are stack traces for when an error gets raised, but stepping through a stack looking for the cause of a generic error is tedious and sometimes error-prone, and makes for some terrible log messages. We often don’t surface information to users, other than some cryptic error message or an unannotate…

From Exceptional: Freedom from {:error}s by Brooklyn Zelenka

Why not use a pattern like try/catch? While try/catch is well-understood, it has a tendency to hide information. By being explicit, we keep our code clean, clear, contextual, and easy to follow.

From Exceptional: Freedom from {:error}s by Brooklyn Zelenka

…O anywhere), it’s still good practice that leads to better software. Falling out of this principle: the caller should have the power to decide what to do with an error state, inverting the responsibility of alerting or handling to the caller.

Claps from Sébastien VARLET

See more

Life with the iPad Pro and Apple Pencil

Matej ‘Retro’ Jan

A Week on Huel: One Small Step for Man, One Giant Leap for My Bowels

Jared Hill

Kleisli Compositions in JavaScript

Luis Atencio