It is a while I don't code in elixir however when I was learning the complex part definitely wasn't the one in this course.
The complex part is to start to think about decompose a big problem into smaller problems solvable by different Erlang modules.
When to spawn another process or when to re architecture the code.
Really great work but I would go a little bit ahead and add some more specific Elixir/Erlang part.
Also what really really helped me was to understand how a GenServer was written, it may be worthed to make the student write its own limited version of a GenServer...
Yeah, the difference between "this is suitable for a library (that is then called from within the context of someone else's process)" and "this is suitable to be its own process (that is called via message passing)" is something that takes a while to fully grok from an architectural perspective.
Howdy @siscia! When I wrote Elixir School the intention was never to be a full fledged tutorial or to "hand hold". The purpose of the site is to get you familiar with the topics, wet your appetite, and enable you to go out and learn more on your own.
We're working hard on some big changes this year including additional lessons and a blog. The blog will allow us to cover topics and material that don't fit well without our current lessons. Check back!
The complex part is to start to think about decompose a big problem into smaller problems solvable by different Erlang modules. When to spawn another process or when to re architecture the code.
Really great work but I would go a little bit ahead and add some more specific Elixir/Erlang part.
Also what really really helped me was to understand how a GenServer was written, it may be worthed to make the student write its own limited version of a GenServer...