I had this blogpost open in a tab for ages. Finally read it. I must say, this is a magnificent write-up! Both in style and content. It deserves more praise. I am type-averse (or better: type-scared), but this was a great summary of everything type-related in Elixir.
Thanks for sharing! I see it’s your first post, but hope to read more. Keep it up!
Thank you very much, I’m glad you liked it!
I’ve been a bit in the weeds for the last few months building a product (with LiveView!), but I’m starting to see the light at the end of that tunnel so I’ll probably start publishing again soon (it’s certainly given me a lot to write about).
Indeed, as I’ve written even more Elixir in the time since I wrote that article, I’ve become all the more convinced that most of their value comes from serving as a form of documentation. Dialyzer does surface the occasional bug, though, which is convenient, but I probably wouldn’t use typespecs so heavily if it wasn’t for the nice popups I get from them in nvim (courtesy of ElixirLS).
In the same vein I go out of my way to write a full @doc with an example for basically every internal function in my applications, even though (at least for the time being) I’m the only one who reads them. Eventually I forget how my own code works (don’t we all?), and having a little example pop up when I autocomplete the function makes all the difference.
I forgot to reply to this at the time, but many thanks to you as well! Indeed, Erlang style pattern matching is probably much more intutive for those with a background in math - something I hadn’t considered. I really do think the pattern matching is probably the most confusing part of learning Elixir, more so than immutability. Probably because immutability/recursion are still taught and used in C-style code even if they are not the focus.
Ironically, j = j + 1 is perfectly valid in Elixir (though not in Erlang)!
the title should be something like:
This is by no means exhaustive, and some values may be not completely accurate, so its very possible that you find something not completely right. If so, please correct anything in the comments (or here)
https://joez99.medium.com/calculate-the-memory-used-by-a-process-and-its-descendants-e0bcc93d4652
After my previous livestream I went ahead and made a text version of what we covered. If you want to learn about S3-compatible Object Storage and cool things you can do to it with Elixir, read on. Basics as well as presigning, chunked uploads and range requests.
I’ve been working with Livebook much more extensively over the last few months and there’s a lot to love about it.
So I wrote a blog post about why I think every Elixir developer should add it to their toolkit.
Hi everyone. I’ve tried once more to create a nice development setup using docker, or by now rather podman, on my local Mac. The goal was to be able to mount the sources of my projects using a shared folder, so that I can edit them using the tools installed on my Mac, but still use containers for managing Elixir versions and being a bit closer to the production environment.
Since setting this up was a bit more complicated then expected (see also this Thread on this forum), I’ve decided to write a blog post about it as documentation for myself and anyone who might be interested:
In the second post in my series on Elixir macros, I introduce the concept of a “quoted expression”, and show how to create them using quote and unquote .
I wrote up an experiment I did using metaprogramming to add guard clauses to the match operator.
Match Operator Guards
