Let It Crash

This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).

A curated selection of passages from Joe Armstrong's 'Programming Erlang' book, exploring the 'Let It Crash' philosophy. The post covers Erlang's process-based worldview, message-passing concurrency as an alternative to shared-state concurrency, supervision trees for error recovery, and immutable data structures. It draws parallels between Erlang's actor model and CQRS/Event Sourcing patterns, arguing that separating problem-solving code from error-handling code leads to cleaner designs and more resilient systems.

4m read timeFrom verraes.net
Post cover image
1 Impression