Learning Elixir, Phoenix and Ash: Preface
For reasons that I might (or might not) get into some other time I’m going to give Elixir and Phoenix another shot. I have been coding recreationally with Elixir for several years. It’s a language I enjoy using but I haven’t used it for anything substantial. I have tried learning Phoenix a couple of times, but other than demo apps in tutorials I haven’t built anything with it. So I’m going to give it a proper try this time.
I’m also going to throw Ash into the mix. Ash is a declarative application framework for Elixir. It was recommended to me by a good friend whose opinion I rate highly. My only worry is it’s massive and moving quite fast. Also the author has stated that onboarding isn’t their priority, they are prioritising power users so it might be a rocky road ahead.
Phoenix is also changing a lot. I have several books about Phoenix but unfortunately they are a version or two behind. The directory structure and some code looks nothing like what you get when you mix phx.new my_app. Good way to sell books I guess ¯\_(ツ)_/¯ I bought them through Humble Bundle so at least I didn’t pay full price.
This might turn into will be an ongoing series about my journey, trials and tribulations, learning Phoenix. I’ll preface this by saying I don’t know what I’m doing so some of this will be obvious to more experienced developers. As I state on the homepage I’ll post about things that I struggle with so that I can find them again when I forget how it works.
Learning Elixir, Phoenix and Ash Part 2: Relationships
Learning Elixir, Phoenix and Ash Part 3: Multi-tenancy
Learning Elixir, Phoenix and Ash Part 4: Code Interfaces
Learning Elixir, Phoenix and Ash Part 5: Authentication
Learning Elixir, Phoenix and Ash Part 6: Validations
Learning Elixir, Phoenix and Ash Part 7: Migrations
PS. Elixir and Phoenix came out pretty well in the 2024 Stack Overflow developer survey