Sure. Have you read it and can you give a summary of it? Several people have upvoted, so presumably the content is pretty good, but I couldn’t get a good handle from the abstract on exactly what it’s about. It says it’s about making your software reliable even when you have a software error, which sounds to me like using parts that have not so many 9s* in clever ways so as to add 9s to them. Is that what it’s about? Does he have interesting points on the topic, or is generally what you would expect?
*If you wish, replace “have 9s” with “is reliable” everywhere.
Its fairly long and I don’t feel comfortable trying to boil down.
The rules it lays out are embodied in the OTP libraries that ship with Erlang. If you have a familiarity with them, then you would have a practical exposure to the ideas.
This seems pretty cool. Is it basically about adding 9s?
9s is really just shorthand for reliable
Sure. Have you read it and can you give a summary of it? Several people have upvoted, so presumably the content is pretty good, but I couldn’t get a good handle from the abstract on exactly what it’s about. It says it’s about making your software reliable even when you have a software error, which sounds to me like using parts that have not so many 9s* in clever ways so as to add 9s to them. Is that what it’s about? Does he have interesting points on the topic, or is generally what you would expect?
*If you wish, replace “have 9s” with “is reliable” everywhere.
Its fairly long and I don’t feel comfortable trying to boil down.
The rules it lays out are embodied in the OTP libraries that ship with Erlang. If you have a familiarity with them, then you would have a practical exposure to the ideas.
Hmm, I don’t, although that sounds interesting. Thanks, I’ll put it on my read it later list.