Loading post…
HerokuFred HebertAnnouncement
Stuff Goes Bad
Summary
The Heroku Routing team describes a manual created to preserve hard-earned operational knowledge from developing and maintaining Erlang systems at scale. That knowledge had typically been passed informally through incident simulations, code reviews, and similar practices, leaving no persistent record for new team members. The manual presents itself as a guide to being an “Erlang medic” during failures, combining tips, tricks, code snippets, and practices for understanding failure sources and debugging running production systems. It is available as a free PDF under a Creative Commons License at erlang-in-anger.com, and was released in time for the Chicago Erlang conference, where Routing team members and Erlang community participants could discuss real-world applications.
Context
The team wanted to preserve operational knowledge that was usually transmitted informally through incident simulations, code reviews, and related practices, rather than recorded persistently for new members.
Approach / What changed
The manual collects tips, tricks, code snippets, and practices from Erlang production work to help developers operate, diagnose, and debug running systems.
Takeaways
The manual focuses on operational failures and debugging in production Erlang systems, rather than tutorial-level development alone.
Its material includes code snippets and practices intended to help readers understand where failures come from.
The free PDF is published under a Creative Commons License at erlang-in-anger.com.
Source and freshness
- Source
- heroku.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.