@AstonJ: I am:
- Learning Elixir
- Looking and at least try to answer on some questions here
- Working for Makestry LTD
- Planning and working on some libraries/projects, see my special announcement.
Eiji
davearonson
Finally getting some downtime to get back to Elixir. Been going through the drips at https://hackernoon.com/a-free-introduction-to-elixir-otp-ecto-and-phoenix-228d0e994fc1 and highly recommend it to those newish to Elixir.
marciol
I’m learning Elixir, Erlang and OTP stuff as fast as I can. In parallel I’m grasping all about Phoenix, Ecto and related subjects in order to start an MVP in a week. (I don’t want to start this in Rails or even Hanami, which would be the natural choice for me).
ChaseGilliam
Working on a library that turns ExUnit test cases and their tags into markdown documentation to use with ExDoc. It parses the ast and build up an intermediate representation to output as json/markdown/?. GitHub - Ch4s3/bartleby: Elixir Test parser and documentation transcriber · GitHub
OvermindDL1
Hah, that looks cool, you should post it in its own thread when it gets docs and published! 
ChaseGilliam
Yeah I intend to. It’s basically a tool for satisfying some client requirements for “compliance” in the health space, but other folks might find it useful.
Qqwy
TypeCheck Core Team
Today I investigated how unreadable code would get when @/1 were overridden… 
EDIT:
defmodule Foo do
defmacro @(ast) do
IO.inspect(ast)
case ast do
{:@, _, [{name, _, arg}]} ->
IO.inspect(name);
quote bind_quoted: [name: name, arg: arg] do
case arg do
nil -> IO.inspect("So, you like Super Attribute #{name}, dontcha?")
[val] -> IO.inspect("Super Attribute #{name} now contains #{val}!")
others -> IO.inspect("Super Attribute #{name} get all these things: #{inspect(others)}")
end
end
_ ->
quote do Kernel.@(unquote(ast)) end
end
end
end
import Foo
import Kernel, except: [@: 1]
@@foo
@@bar 1
@@baz 2, 3, 5
@thingy 3
Or even better:
defmodule AtAt do
defmacro __using__(_opts) do
quote do
import AtAt
import Kernel, except: [@: 1]
end
end
defmacro @(val) do
case val do
{:@, _, [{name, context, args}]} ->
{count, inner} = count_ats({name, context, args}, 2)
quote bind_quoted: [count: count, inner: inner, escaped_inner: Macro.escape(inner)] do
IO.inspect("Wow! Running #{Macro.to_string(escaped_inner)} with #{count} ats!")
inner
end
_ -> quote do Kernel.@(unquote(val)) end
end
end
defp count_ats({:@, _, [{name, context, args}]}, accum) do
count_ats({name, context, args}, accum + 1)
end
defp count_ats(other, accum) do
{accum, other}
end
end
iex> use AtAt
iex> @@@@@@@@@@@@@@@@@@@@@@@@@@self()
"Wow! Running self() with 26 ats!"
#PID<0.85.0>
AstonJ
I’ve just finished Elixir in Action 
(after reading 50% of Programming Elixir) - definitely feel like I have a fairly good overview of Elixir now.
I’m not sure whether to finish Programming Elixir next, or start Programming Phoenix (or maybe read them together?) - I’m itching to get a Phoenix done… but not sure whether I should wait for the book to be updated for 1.3 (/contexts etc).
Any suggestions? 
marciol
I read part 1 and 2 of Programming Elixir, it is a good book when you are interested in a good prose and are available to learn in a slow pace, it is great for the exercises, but I think that now the Starting Guide from https://elixir-lang.org is enough. I’m now reading Programming Phoenix and Learn You Some Erlang for the Great Good, and after that Elixir in Action and Designing for Scalability with Erlang/OTP (O’Reilly), so I think that start Programming Phoenix would be a good choose.
AstonJ
I am probably going to leave any Erlang-specific learning till last (Saša has years of Erlang experience so you definitely get that point of view in Elixir in Action).
I might continue with PE for now then, and see if we hear anymore of when Programming Phoenix might get updated…