Approach to development in Elixir - Utilising Elixir tools better

Sometimes tracing is more informative than manual IO.inspect

• GitHub - nietaki/rexbug: A thin Elixir wrapper for the redbug Erlang tracing debugger. · GitHub
• GitHub - ferd/recon: Collection of functions and scripts to debug Erlang in production. · GitHub

In tests I start tracing before the failing function is called:

test "some curious failure" do
  Rexbug.start("Schrodingbug :: return", msgs: 30)
  refute Schrodingbug.maybe_fail()
end

In dev I can run it before execution some function in UI / API request, like before logging in:

iex> Rexbug.start("Accounts :: return", msgs: 100, time: 10000)

# ... starts printing out traces of the function executed in the login flow
# ... gives a better understanding of how things fit together

Best of all it works in prod, but that use-case is already described in the project descriptions above.

Will check it out and let you know!

Seems powerful.

It is. If you look into tracing, give the Rexbug print_fun option a try: print_fun

Custom function to use to print the trace messages.

So you have full control. You could eg color the trace for starters.