This one is on Relups and Appups, or a way to do hot-code loading and live software upgrades in a safe manner, hidden from race conditions and state changes. This is done using the OTP framework's release_handler. The process is a good bit messy, requiring some manual work that would benefit from being automated more.
However, this section of Erlang is hardly ever explained, so I attempted to make one effort into documenting it and its quirks for other fellow Erlang developers out there. Hopefully, Rebar and other tools will be able to build on that documentation to foster better relup abstraction layers, also making everyone else's work easier.
This safe way to do code upgrades is one of the feature that differentiates Erlang from many other languages when it comes to ad-hoc code updates. I've seen other languages do the equivalent of loading new code (reloading a module, calling eval() on a new version of the code, etc.), but I don't recall seeing many of these taking care of handling state change or race conditions on events the way Erlang/OTP does it.