Making Compiler Design Relevant for Students who will (Most Likely) Never Design a Compiler

 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 remember the phases for making a compiler that are:

• Lexical Analysis
• Semantic Analysis
• Code generation
• Code optimization

These on are pretty good explained an in a way these seems a little bit easy but at the end some implementations are one that may have their complexity when I get the chance to implement them, From these phases the one that I always have issues is the Code optimization because the optimization I thinks is so relative and in some times this part always become so  competitive between the team.

This reading gave me the chance to see all of the things i can still learn or to improve, It still is going to be a challenge but also help me see why we can take this subject as a las subject exam but create a new doubt about how is going to be the legendary final exam.