Let It Crash
Joe discusses the limitations of traditional specifications in software development, emphasizing the chaotic nature of ad hoc decision-making when deviations occur. He advocates for the "let it crash" philosophy, where processes fail gracefully, allowing supervisors to maintain system integrity. This approach not only simplifies error management but also enhances the ability to upgrade code dynamically, particularly in highly concurrent environments.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
Episode 89: Joe Armstrong on Erlang
Related Questions