Compiler Design

 I was very happy that this article also was from our professor, even do web have nerve been y favorite in the article we have a new approach of the compiler design class with the web overview. I fell part of the article when the author mention all of the activities that we are making but got also get a little bit disappointed where I read that there activities are not enough to have a the topic fully acknowledge. After having this in the field, the author brings a web approach and mentions the real fact of letting all of the students choose their own path and explain the possibility that most of the wont became web developer but those that choose a web developer path will be huge benefit from this methodology. Having the level of communication that the compiler brings to the tables is very useful because in a way you will have to create rules and apis until we get the structure needed. looking thru all this web technologies that are so modular, will be pretty beneficial to anyone that

 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

 The story of Grace Hopper described in the article and in the video emphasizes something obvious but which is uncomfortable to highlight, this is the fact that women's achievements have been overshadowed and although they exist, they have been less due to the different historical trajectory that men and women have had and because of the late incorporation of women to many professional activities and even issues that reach the legal framework designed by men that historically exclude women. It is for this reason that the story of "The Queen of Code" is inspiring and stands out the important role of women in technology,  It is very devastating to see how talented people in this case Grace Hopper, was so underestimated and held back in her attempt to bring knowledge to humanity, simply because she was a woman. Despite that, she became the mother of Cobol, becoming an expert in an area that was unknown back then, with the proposal of Cobol becoming the universal language.  S

 After listening to the podcast i got a whole new vision to the "layers" and the importance into understanding the benefits that you can get from looking into every layer, and for that every day there is  a lot of effort from all the compiler developer in order to improve this functionalities. Now we can actually threw all of the stages in which the source code that is written by the programmers into the target code that understands the computer and can execute it. First the lexical analysis we are going to check all of the characters stream into a token stream, that basically means looking for all of this reserved word or variables that will be used justa as "and, or, do". The second stage is the is where we introduce the abstract syntax tree in order to see the order in which the operations are going to be compute.The third phase is going to be a check to see if the variables were declared in the previous version. And Finally the code generation  that can be easy

 Somehow this remember me a chapter of the Arrow series where the son of green arrow "William" talks in the future about the old program files but still mention techniques as recursive algorithms, In my own opinion there will be a lot of upgrades maybe in the way we manage memory or maybe how we will run things in parallel, Today we can't imagine to work in parallel using the same space of energy, but maybe in the future there would be some awesome threads that can talk between each other and manage a memory space together, We I got the chance to be in the IBM hackaton's, I got just a few understanding of how the quantum computation works an they were talking about the use of python but not as a common programmatic skills , there were talking about connections and the need of knowing quantum physics. I am sure there are a lot of things that will surprise us in our future and for sure there will also be tons of challenges. In my imagination I can picture some problems

 After having my time with the reading I got the opportunity to answer some of their questions I did to myself when I heard of this subject. First it was the doubt of How many compilers I will have to make in my future life?, now I know that the maybe I will never have to do another compiler, but that I have to pay more attention into the problems and learn about the solution in a more modular way. Looking for the problems like this even outside the subject is a very good philosophy for any life. You are basically just taking all of the huge problems and solving them in small parts just as the programming advices always tells you. One of the examples that remberme something is the translator of Latex into html because somehow remembers me the tool web of symbolab, when I need to make some math notes or I have math homework I use symbolab tool as GUI for making my matrix and just having to Ctr+c in order to get the Latex commands and export them to my document. From the text I will reme