In the previous articles, we have implemented the Toy Robot (you can find it here Part 1 and Part 2).
This time we will improve the implementation and turn it into a console application.
In that application, we will be able to run the simulator and give commands to the robot.
In the first part, we have implemented the placement, rotation and for our toy robot. The robot can also provide us the report about its position. At this part, we will proceed with the implementation. We will implement movement functionality and improve our code a little bit.
Now as we already covered the basics of Elixir in the previous articles we can try to practice a little bit.
Here I would like to solve the Toy Robot Simulator problem which I’ve
I guess that is not original source and it was reposted at many other resources.
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.