Firstly Thanks for taking time and having a look. That means a lot to me. 
what you mentioned is highly important . I don’t how I missed that.
Thanks a lot for pointing out.
blackode
Mandemus
Medium article was great.
However tbqh the youtube audio sounds like you are speaking orcish with your head stuck in a toilet bowl. You might want to flush that one and re-record.
tyro
This was interesting:
wish = fn -> fn -> fn -> IO.write "this is chain" end end end
wish.().().() # usage
Are there any examples of this being useful/being used in e.g. elixir lang or other well-written projects?
blackode
kelvinst
I know the elixir’s Stream module has a lot of function ref returning, but it is not quite like this. FWIR it does not have any function def chaining.
blackode
Till now I never tried them in real world projects. I just encountered that while reading about the anonymous function. If you find one please share that will help us
Anyway thanks for reading… and mentioning…
davearonson
Pretty cool! The whole “char list” thing has been a pain for me… except when it comes in Very Handy, like when applying a Range, which only works with integers. As for the chains, though, don’t give people any ideas; that’s what leads to Callback Hell, so common in JavaScript. 
mjrode
Cool, thanks for the tips. There were a few things that I did not know about which will be really helpful in my new project.
blackode
romul
Thanks for sharing. I have a few remarks though:
The first tip is a bit odd. Multiple or is much more readable and besides your hack behaves differently (it would calculate all conditions, instead of stop on the first true).
I guess the tip #3 could be more useful if you would mention that .iex.exs could be used in a project directory and any Elixir-code could be putted in that project-specified file, it’s very helpful to put some aliases into it.
As to #6, there is also put_in/2 that imho even more helpful than get_in/2.
In #7 could be described a full form with .. do .. else .. end.
Tip #10: IO.inspect/2 inside pipes.