It has been about 18 months since I announced on this blog that I was working on writing Phoenix in Action for Manning Publications. I’m very excited to announce that it is finished!
Phoenix in Action
All of my writing energy was going towards finishing and releasing Phoenix in Action, so I apologize for the lack of updates to this site. However, it was a great journey from start to finish and although it was harder than I thought it was going to be (and I thought it was going to be hard), I am proud of how it ended up. I’ve received some great feedback over the year and a half since it was released in MEAP (pre-release) format and I look forward to hearing what you think about it.
If you’ve not picked up a copy already, would you do so now? I’d really appreciate the support. If you do buy a copy and enjoy it, please leave a review at your favorite online retailer and tell others about the book. You can buy it directly from Manning.
My experience writing for Manning
I won’t say a whole lot about my experience writing for Manning except to say there were ups and downs but I was overall very pleased with the process. While I did encouter a few frustrations during the writing, Manning was nothing but accomodating and always wanted to do the right thing by me. I also firmly believe that the editing process I went through made the book so much better than I could have made it on my own.
If you want to know more, feel free to contact me on twitter at @geolessel or just read this great (and very in-depth) writeup by Barry Pollard titled “Writing a Technical Book for Manning”. There is very little I found in that post to disagree with or contradict. It very closely mirrored my own experience. I’m just grateful he wrote all that and I can just link to it.
So what about the site?
Manning approached me initially about writing Phoenix in Action presumably because of the writing on this blog (and perhaps a conference talk). I’d like to keep up the writing process and go back to shorter-form writing and tutorials after tackling such a large project.
Updating old posts
Initially, I have plans to go back to old posts and update any code required to make them still relevant. I’m sure there are some things that have broken in the 3 years since they were first published, but I believe the contents are still important and worth making work again.
Adding new posts
I also have some ideas for new posts coming up as well. While writing the book, I shipped a small number of pet projects that could make great posts or tutorials. Here’s some highlights:
- chatbroom.com: a database-less real-time chat site that uses Phoenix Presence, Channels, and React. Since it has no database, it has no persistence (a feature!). If you aren’t there when the post was sent, you won’t ever see the post in the chat history. Also, you can’t get it back if you refresh the page or navigate away and back again.
- cookingwithlink.com: a simple site to view/search cooking recipes for the Nintendo Switch game The Legend of Zelda: Breath of the Wild. This could cover building simple APIs with Phoenix.
- requestecho.com: kind of like requestbin.com, but like ChatBroom, it has no database and no persistence. Use it to inspect web requests.
A little project in which I create a MIDI sequencer for hardware synthesizers. This isn’t all that far along, but here’s a preview:
This will likely not be an open-source project, but I could potentially do a post about what I’ve learned during the process with MIDI and GenServers trying to send millisecond-precise events to external hardware.
I’ve done some testing with Phoenix LiveView as well and it is 🔥🔥🔥. I might do a post about how to set up a simple test application that makes use of LiveView. A preview:
Have you played with @elixirphoenix #LiveView yet? It’s *INSANE*. This is a quick test app re-computing and re-rendering over 200 rows of data every 1/10 of a second. I wrote no JS code. Bravo @chris_mccord and team! #MyElixirStatus pic.twitter.com/E1oEkje8Ji— Geoffrey Lessel (@geolessel) March 20, 2019
A small Nerves application that watches a coffee pot’s current draw. Once it finishes brewing, it notifies a slack channel.
- Other, one-off stuff.
Whew, that’s a list. Of course, I might end up doing posts about none of those things. But if you’d like to see anything in particular, please let me know.
Thanks for sticking around
Thanks for sticking around and for your continued visits to the blog. I really do hope you find it a good resource as you learn Elixir and Phoenix. As always, you can reach me on twitter at @geolessel and @geo in the Elixir slack group.