Chapter 1: Discovering I chose the incorrect career ft. Lego Bricks.


Welcome to my first blog entry, I´m your host Esteban Gil, in this chapter I will introduce myself and some other insights about my feelings towards this course.

First let´s get rid of the (academical) elephant off the room; my expectations from the Software Design and Architecture Course. I would like to understand and have the ability to differentiate between different types of architecture, know their advantages and disadvantages, and learn to develop my own. I haven't had any experience on the topic, and haven't coded in Ruby, so this is going to be all new for me. Also, I haven´t taken a class fully in English for years, so that will be interesting. Also, it´s my first class with Ariel, so I have great expectations of this class.

Here we can see Steve, reflection on his poor life choices... again...

And now my hobbies and personal interests, as well as books, music, movies and programs I have enjoyed. I consider myself an avid gamer, specially in Super Smash Bros Melee (SSBM for short). Currently sponsored by SHFFL, I´m ranked in the top 25 players in Mexico City, but I still have a lot to learn.

Because I don´t have a lot of free time, I don´t see movies, read books or see TV programs that often. However, the last series I watched was Rick and Morty (My type of humor). Finally, you can call me Steve, Esteban, or whatever comes first in your mind.


Comments

Post a Comment

Popular posts from this blog

Chapter 4: Architectus Reloadus vs Architectus Oryzus

Image
So, who needs architects anyways? Here lies one of the most important roles in the software world the unstoppable Architectus Reloadus. After reading the article, it reminded me of an image picturing 2 groups of people; each group having either a boss or a leader commanding them. While the boss was just instructing where to go and what to do, the leader was working with its group. This is the same analogy we get in the article with the 2 types of architects mentioned, the  Architectus Reloadus  and the  Architectus Oryzus . Architectus Reloadus  is the architect that proclaims himself as the  most important part of the project , as the design is made only by him, leaving the other developers to follow. While the  Architectus Oryzus  works within the team to improve the team’s level so they can approach harder and more complex issues. In other words, the Architectus Oruzys  is a guide, skillful enough for being the anchor of the team, and clearly selfless, as he works at the
Read more

Chapter 11: Metaprogramming

Image
The last article read was “An Introduction to Metaprogramming”, an interesting article where Ariel explains the concept and some examples of metaprogramming. Starting of describing the different types of metaprograms, like compilers, interpreters, parser generators, assemblers and preprocessors, metaprograms come in many shapes and forms, which main goal is to eliminate or reduce error-prone programming tasks. I have heard of this concept as a utopic approach to things, however, I haven’t seen metaprogramming first hand. At first, I thought it was a really complex way to do things, but after reading the article, it doesn’t go that deep into weirdness. Beginning with the first example; it clarified how the concept of metaprogramming works, a script that wrote another file with the code expected. While the ruby snippet shown was not some other world stuff, but the example is pretty clear, we can write codes through code. Now, the second example goes a little bit deeper
Read more

Chapter 9: Microservice Architecture: A whole new Architectural world.

Image
After reading the article, I started relating microservice architecture with the activity we made when we talked about components and Lego bricks in class: This type of architecture is made of smaller and independent services that are linked together to form a concrete service. With the image below, we can see a clear representation of how this is conceptualized. However, there is a small detail that separates microservices from monolithic services; while the later gathers all functionality into a single process, the microservice separates each part of the functionality into a separate service, allowing scaling with distribution of the services, replicating as needed. This is the aspect I liked the most; low key planned modularity for software architecture (or at least that’s how I see it) There are a lot of interesting features of this type of architecture (with a heavy approach to encapsulation, as I dare to confirm), such as Componentization via Services, Organized ar
Read more