[erlang-questions] [ANN] Stuff Goes Bad: Erlang in Anger

[Mark Nijhof]

Nice! Will read when back home, Erlang stack traces have always been hugely
cryptic to me.
 On Sep 17, 2014 5:45 PM, "Fred Hebert" <mononcqc@REDACTED> wrote:

> Hi everyone,
>
> After a lot of time on the backburner, the Heroku routing team and I are
> excited to announce 'Stuff Goes Bad: Erlang in Anger'
>
> From the introduction:
>
>     This book intends to be a little guide about how to be the Erlang
>     medic in a time of war. It is first and foremost a collection of
>     tips and tricks to help understand where failures come from, and a
>     dictionary of different code snippets and practices that helped
>     developers debug production systems that were built in Erlang.
>
> This is our attempt at bridging the gap between most tutorials, books,
> training sessions, and actually being able to operate, diagnose, and
> debug running systems once they've made it to production.
>
> It's entirely free (as in beer), available as a PDF, and using a CC
> license (almost free as in freedom).
>
> We hope this will prove useful to the community! If you have feedback or
> whatever, you can send it directly to me, or meet some of our team
> members at the http://www.chicagoerlang.com/ conference early next week!
>
> Blog post at:
> http://engineering.heroku.com/blogs/2014-09-17-erlang-in-anger
>
> Download at:
> http://www.erlang-in-anger.com/
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140917/6f88111c/attachment.htm>