As you might have guessed, it’s “Learn You Some Erlang”. It takes you by the hand and guides you through the foundations (syntax, types, etc) up to recursion (very important), through functional concepts and concurrency up to everything OTP and beyond.
What I really like about the book is the examples. Every (well, most) chapters are built around a small , self-contained toy project. This way, when you want to (re-)read any chapter, you don’t have to read the chapters before that to understand the example code; you need to know the concepts that were covered in the earlier chapters, but not the examples.
As @Maria-12648430 mentioned, this book was written based on an older OTP version (R16 I think it was, maybe even older), and some things have changed in OTP since then. Maps, introduced in OTP 17, are covered only briefly in a postscript chapter, and gen_fsm has been deprecated and replaced by gen_statem in OTP 19.
At some point (not at the very beginning, mind you), it may also be good to start browsing the Erlang docs instead of solely relying on the book. After all, when you’re finished with the book(s), this is pretty much what you will have to rely on, so better get familiar with it.
Morning. Just a quick question. When you folks were studying Erlang, how did you come up with ideas of problems to solve in relation to your studies. Also, in your current work environment, do you form part of a team and do a part of the solution or do you do the entire thing.
Apologies if this question is vague, because I have the basics fairly well nailed down but cannot think of a problem to solve. It is all very well doing the excercises in the manuals, but coming up with something to solve is rather difficult as most of the problems are solved with other software (Excel, Word, messaging programs, etc etc.).
It’s a very valid question, and one that I struggled with when first learning Erlang.
I reimplemented part of a codebase I’d currently been working on. Actually, that was a poor idea as it was running before I could walk, requiring learning how to use the mnesia database etc. But I did revisit it later.
Implementing a solution to one of our interview questions. This was actually a good move. I then re-implemented it using OTP.
Various small, standalone examples, as if I was trying to teach someone else. E.g., a state machine for a traffic light (not using OTP) and the simplest possible multi-user “chat” program.
in your current work environment, do you form part of a team and do a part of the solution or do you do the entire thing.
This is doesn’t just apply to Erlang. In very general terms, I’d come up with a concept and run that past others (in a formal or informal way, depending on context). I’d then have an iterative process of adding functionality, refining/reworking the design, fixing the inevitable issues and integrating with other components in the system. In short, if you are working in a team, you can use that to your advantage whether you implementing part of the solution or the entire thing.
Good morning. Firstly, I ask that you please do not laugh at my progress as this is the VERY FIRST time that I did not look at any manuals. I did have to look up the ASCII, but in the spirit of the season:
-module(message).
-export([greeting/0]).
%% To everyone that I know here on the Erlang forum who has been extremely kind, patient and helpful …
PS I still had to look up the lists module (lists:join/2 didn’t do what I immediately expected). It’s always good to keep the docs handy/bookmarked, especially for lists as they are so core to Erlang.
Eshell V11.1.8 (abort with ^G)
1> Greeting = [77, 101, 114, 114, 121 ,32 ,67 ,104 ,114 ,105 ,116 ,109 ,097 ,115].
"Merry Chritmas"
^^ missing an 's' which is 115
2> {L1, L2} = lists:split(10, Greeting).
{"Merry Chri","tmas"}
^^ Splitting the list at the point of the missing 's'
3> L1 ++ [115 | L2].
"Merry Christmas"
^^ adding the parts back together with the missing 's'
