rey
Can I learn / use Phoenix without fully learning all that Elixir has to offer?
Hey all,
First post! I really fell in love with Elixir and Phoenix, and the community as well.
So here’s my problem: I’m a front end developer by trade. Elixir (Phoenix) will be my first backend language that I’m seriously trying to learn (I’ve tried before with python and php earlier in my career, but quickly lost interest, half because of the api / documentation, and half because once I learned, I didn’t know of anything interesting I wanted to build.
I want to learn Elixir & Phoenix to build websites. So I’m about 100 pages into the Programming Elixir book by Dave Thomas, in addition to 52% into the video Hangman course by Dave Thomas (I started with the course, then tore open the book as I wanted them to go more over data structures, pattern matching, and recursion).
The problem I’m having though, is the same one as always: I’m being confronted with tons of “Enum” methods which I have no chance of ever remember or caring about. I want to just start actually using Phoenix to build a site.
So my question is: do I for some reason need to completely finish this Elixir book before I move onto Phoenix? Or should I just finish the course and that would be good enough?
Most Liked
Eiji
Don’t try to remember that! That’s definitely not a good way to learn anything related to documentation.
I don’t believe that you would need to pay for anything and read any books. Of course they are awesome and would help a lot, but you can definitely deal with Elixir without them.
Here is my general proposition:
-
Firstly learn basics (like guides from official website). You can’t use
PhoenixwithoutElixir, so its definitely required. -
After it take a look at least one good website for learning Elixir like ElixirSchool. After that your knowledge should be enough to learn on your own way faster or slower.
-
Once you read them you should (it’s not requirement) read whole Elixir API module by module.
Of course you should not remember anything of that. You should know that something like this (here: specific function) exists, so when you are stuck then you can return back to specific documentation much more faster - that’s point - it’s basically your learning optimization i.e. if you know what you want to find then it’s already 90% of your research.
-
After that I recommend to read some forum posts and
Slackconversations for example elixir-news. I think that @josevalim explains best his ideas and takes lots of his time to answer questions even from beginners. Being so close allows you to understand way of programming inElixirlike why this is introduced, why it has biggest priority, why this should be implemented as standalone library etc. -
If you are going to use database go to step 1, but change
Elixirtoecto. Welcome in infinite loop.
-
At this step take care of
Phoenixguides. It’s your final step. I don’t believe that there is quicker free way to write goodElixircode and usePhoenix.
Make sure you consider also optional steps. They are like friends in MMORPG games which can level up you much quicker. ![]()
Other threads which may help you:
-
What is your number one tip for anyone new to Elixir?
I think it’s related thread. Some tips always under price.
-
Why Enum.filter_map is deprecated?
I choose this one as a simple example of thinking in core team. -
Your Elixir Tips Thread
Again tips … Is it déjà vu already or just another my SPAM tip?
-
https://stackoverflow.com/questions/37445838/returning-values-in-elixir
This is important example especially when you used another language before.Elixiris much easier to learn in my opinion. It’s like a cat i.e. really cute syntax, but follows its own way.
-
Elixir's biggest gotchas?
The biggest gotcha is actually not read this thread!
peerreynders
dimitarvp
IMO any time you might save now you will repay tenfold down the line in the future. Not worth it.
I went through the official Elixir tutorial in one long weekend afternoon.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









