Thursday 1st November, 2012
11:45am to 12:30pm
They keep telling us we should foresee and catch every possible exceptional situation in our code. But programs keep on crashing. Why? Because they can't help doing it. Solution? The ʺlet it crashʺ principle. It allows writing more robust software. This talk is guided by design principles and best practices well known from the Erlang world, but which can be transported to different technologies.
Sign in to add slides, notes or videos to this session