4 ms·

I am currently reading this book. Currently in chapter 2. So far author's explanations have been really good. Although this book has a chapter on Elixir it's ma

I am currently reading this book. Currently in chapter 2. So far author's explanations have been really good. Although this book has a chapter on Elixir it's main focus is in Phoenix. He introduces enough Elixir to work with Phoenix.

nicolasd 9y ago
How good is the "Blueprint for Phoenix Context" part? I am already working with phoenix/elixir on a daily basis and would be only interested in good examples with contexts.
- pvsukale3 9y ago
  Sorry, Don't have that book.
thejosh 9y ago
You should learn elixir before phoenix. Phoenix is just elixir.
- andruby 9y ago
  I don’t necessarily agree. I think you can learn both at the same time. A decade ago, I learned Ruby through the original Agile Web Development with Rails book. Afterwards I read Ruby-only books. I think both approaches work. The most important thing is probably keeping the learner engaged. For me, being able to create something I wanted (a webapp) quickly, was rewarding enough to keep me going.
  - iamd3vil 9y ago
    I think if you are coming from Rails and Ruby to Phoenix, you should learn elixir first. Or else, like a lot of people, you may think that it's similar to Rails. Phoenix may look similar to rails, but there is a huge difference on how they work. Also atleast from my point of view, you should know about OTP too. Your application is an elixir app, with phoenix which provides just the web interface to your business logic.
  - ajmurmann 9y ago
    I learned Ruby and Rails at the same time just like you and many others. I found that people I got to work with who had learned Ruby first and then Rails had a clearer understanding of how things actually work. Rails was doing so much magic that some people never learned how things work without Rails. Autoloading is the strongest example that comes to mind.
  - thejosh 9y ago
    You can learn both, but learning the basics of elixir will help. Phoenix is not your app, don't treat it like that.

nicolasd 9y ago

How good is the "Blueprint for Phoenix Context" part? I am already working with phoenix/elixir on a daily basis and would be only interested in good examples with contexts.

pvsukale3 9y ago
Sorry, Don't have that book.

thejosh 9y ago

You should learn elixir before phoenix. Phoenix is just elixir.

andruby 9y ago
I don’t necessarily agree. I think you can learn both at the same time. A decade ago, I learned Ruby through the original Agile Web Development with Rails book. Afterwards I read Ruby-only books. I think both approaches work. The most important thing is probably keeping the learner engaged. For me, being able to create something I wanted (a webapp) quickly, was rewarding enough to keep me going.
- iamd3vil 9y ago
  I think if you are coming from Rails and Ruby to Phoenix, you should learn elixir first. Or else, like a lot of people, you may think that it's similar to Rails. Phoenix may look similar to rails, but there is a huge difference on how they work. Also atleast from my point of view, you should know about OTP too. Your application is an elixir app, with phoenix which provides just the web interface to your business logic.
- ajmurmann 9y ago
  I learned Ruby and Rails at the same time just like you and many others. I found that people I got to work with who had learned Ruby first and then Rails had a clearer understanding of how things actually work. Rails was doing so much magic that some people never learned how things work without Rails. Autoloading is the strongest example that comes to mind.
- thejosh 9y ago
  You can learn both, but learning the basics of elixir will help. Phoenix is not your app, don't treat it like that.