Ruby and the Interpreter Pattern

 In a way reading this text means to me a lot of responsibility, somehow I image that if I didn't understand anything was because I was not really paying attention to the class, or even if I didn't understand the meaning of all of this text the understanding of the next class will be limited. Just pint where am I in this topics, I got to known ruby when I was just beginning to look into the iOS developer dependencies where all of the Cocoa pods were written in Ruby. This one is the inly approach that I have gotten until know, but I have already heard from some classmates that we see this language in Software Architecture.

First the reading mention the S-Expressions (SIF), a topic that I got the chance to understand it in the last semester maybe not as deep as in other semesters because of the migration to zoom classes where we lose like three weeks.  But the things I remember the most is the importance of their order in order to have the compiler working perfectly. And just as we mention in the case that we find the "if special form" we will also have to define the new class that has the Node attributes, just to be used for the interpretation of the pattern tree.

From my point of view it's very easy and well explained the notation that the S-expressions have in the Lisp Family, just like any other explanation tha Ariel gave us, seems pretty easy just until we get the need of implement it. The next phases of the compiler will be more and more complicated not just because of the phases itself but the need of having all of the phases working correctly. Any way I have the fully trust in my team that we will solve all of the problems together and in the perfect timing.