Learn Phoenix with Step by Step Screencasts
Okay so admittedly I&#x27;m ignorant to the true content of the screencasts-- but I&#x27;d like to say something on things like this:<p>With elixir and more specifically, BEAM and Erlang, the issue isn&#x27;t &quot;how to do X&quot; it&#x27;s &quot;how to do X with BEAM.&quot;<p>A lot of folks are coming to the ecosystem which is wonderful-- but by not learning the alternative paradigm (which is easy because the Ruby-esque appearance) they&#x27;re missing the true beauty of BEAM&#x2F;Erlang.<p>As I&#x27;ve shipped to production Elixir apps-- I&#x27;ve felt this personally. Ive also learned a lot from doing so... The most valuable lessons haven&#x27;t been &quot;how to use Phoenix&quot; or &quot;how to do X in elixir.&quot; Rather, I&#x27;ve learned, lot of the elixir community is reinventing the wheel instead of using the ones (Erlang&#x2F;BEAM) we already have. There&#x27;s a reason you can&#x27;t find a &quot;tutorial to do X&quot; because the problem is probably largely solved through idioms provided by the language and platform being designed to work together.<p>Erlang has mature web frameworks, database adapters, etc. and it would&#x2F;does benefit one to learn them. To learn how they function and WHY they function that way.<p>Not to sell the authors of this short, but an insane amount of Phoenix is very easy to learn once you learn these principals. The reason being Erlang is idiomatic (generally) in how problems are solved. Phoenix becomes simply &quot;implementation details.&quot; Not something truly &quot;new.&quot;<p>--<p>Note: It&#x27;s late hopefully this isn&#x27;t nonsensical.