Making Compiler Design Relevant for Students who will (Most Likely) Never Design a Compiler
This particular article changed my compiler perspective in a real ideal way (the perspective not only of the subject but of a compiler in general), I never really fully understand the main purpose of the subject, and the fact that it is considered the hardest one (in terms of programming) and it has changed my perspective due to the fact that it shows how we probably would never need to actually create or develop a new compiler (or compiler in general), but instead the course show us how to manage certain deep level problems that would remain hidden otherwise. In general, the course is designed to help us analyze and structure common problems that we might have to face in the future.
The thing that really caught my attention is the abstraction way to see the things and how that could help us to solve problems, the idea behind this statement is to always try to see the problem as abstract as possible, and that could help us to understand the problem on a simpler and modular way which in the end will help us to develop better solutions.
On the other hand we have the relevant fact of 'optimization' this part is supposed to be the added value that every good compiler/code should give to any project, the idea is not to only complete the project or code, it is also to make it as optimal as possible for it to become better and to have an additional value than other similar codes. In the end it is the efficiency of the code in a compiler that will make it optimal and better for the complete environment.
In general, compiler is almost like a metaphor for solving problems that we will face in our future careers, and I honestly believe that is something very cool.
Comentarios
Publicar un comentario