Erlang endorses the “Let it fail” (or “Fail Fast”) philosophy.
The quick explanation would be that there is no need to write your programs in a defensive way.
The idea is also that if your program expects particular crash to happen, then maybe it is not a crash.
Elixir, as a functional programming language, normally follows declarative programming paradigm instead of imperative.
By defining lots of small independent functions and use some tools Elixir provides us, we will use less of control flow constructions comparing to other languages. Well, maybe comparing to imperative languages.
Let’s talk a little bit more about Maps. I’ve already covered basics in the one of my previous articles.
Now it is time to go deeper and discover how we can update Maps and add new items to it.
Have you ever worked on the project which contains no documentation?
Did you have the desire to add documentation but didn’t know where to start?
Well, now we can check how we can do that in Elixir and see how powerful that functionality is.
Last time we were talking about functions I have mentioned that named functions are living inside modules.
Modules provide the namespace for functions and other things defined inside.
Usually grouped by same meaning.