[sbuttgereit]

Learning the syntax and libraries is one thing and there are any number of resources which can inform you and get you through getting those things under your fingers.

I would suggest that "getting" Erlang is more than that however and is important as code that does "something", but not necessarily in a good way, can be avoided by understanding the broader ideas you're dealing with. On that count I recommend Joe Armstrong's doctoral thesis: https://erlang.org/download/armstrong_thesis_2003.pdf. It's basically a detailed examination of what the language and runtime environment are trying to achieve: it answers "what?" and "why?". It's not a difficult or obscurely technical read and even though it's a couple hundred pages, you could probably get through it pretty easily in a couple of days depending on how fast you read.

I don't code Erlang myself, but I do a fair bit of Elixir work, and found it very enlightening for establishing the context from which all the details I do deal with using a BEAM language follow.

[mixmastamyk]

I liked his “history of erlang” a bit better. Gets to point a lot more quickly about design choices and skips excessive code listings. Which I feel not as useful until you get some hands on experience.

[minhlq]

Can you share link to "history of erlang"?