I'm glad to see someone posted this book. I think it's far undervalued. Definitely a must read. The Ruby written could be completely replaced by pseudo code, and it wouldn't change the lessons taught.
The challenge is going to be adoption, plain and simple. I worked two years on an Erlang project, and most of our frustration came from the lack of community to lean on when we needed help understanding best practices. Also, when you find only one library to solve your problem that has been abandoned for at least two years that is never fun.
Few projects actually need the level of scalability that Erlang brings, and the cost of building and running an Erlang project as an enterprise application is non-trivial. People need to understand this if they want Elixir to succeed where Erlang hasn't.
I'm not sure CS and programming go hand in hand anymore. I'm a college dropout that landed a job as a software developer at a good company, and everything that I use daily is self-taught knowledge. I can't remember a time when I used something I learned in CS for the past three years, and I made it to my senior year.
What I can recommend is to learn Github and git. Beyond that, it really depends on what you want to focus on.