S/W Design and Architecture by Angel Andrade

I deeply believe that creating something like this, something of such magnitude, would really be fascinating and incredible, having so much information and all the people in one place, traveling through different fantasies and besides everything, free, that better than a place like that, where the only thing you need (the most basic equipment) is a viewer and an internet connection. I would probably spend a lot of time in that reality, something that would be bad, because in my opinion, it is living a false life, as the quotes say, and probably that world maynot become terrible, but the real world may become terrible. People so obsessed with the game can get to do many things in order to have the best items in the game or to be the best, etc. Despite not having something like OASIS, I believe that there are already many people who live immersed in technology, not only in games, also in their computers or more commonly in their mobile devices, there can not be a family me...

It is impossible that after reading this article we can´t remember the Programming Languages class. That part of the course when we began to learn about metaprogramming also I remember that in the class’ book were pages that have the quote that said that if is not necessary to create a macro don’t do it or in my case don’t try to do it and this was because that topic is difficult to understand, this topic was not an intuitive knowledge, I think that you need to be a high level programmer in order to make this kind of code. This kind of code calls himself a program that generates other programs or program parts, yes, this sound a bit confusing. So, the professor Ariel Ortiz told us in the Programming Languages class that the people who recommend to don’t use metaprogramming only if it is very necessary are people that don’t know how to create macros and the potential that these tools have and, in the article, we can see reflected that hypothesis of the professor. Even he puts an exam...

This article talks about microservices. The microservice architectural style us an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms. These services are built around the business . In order to understand what a microservice is, the author puts and the monolithic example: a monolithic application built as a single unit. But what does it mean? Enterprise Applications are often built in three main parts: a client-side user interfaces a database and a server-side application. The server-side application will handle HTTP requests, execute domain logic, retrieve and update data from the database, and select and populate HTML views to be sent to the browser. This server-side application is a monolith - a single logical executable. Any changes to the system involve building and deploying a new version of the server-side application. Monolithic applications can be successfu...

These videos and article talk about in a short way the 4+1 view model, this little model consists in four sections and an extra section which is the +1 part, that allows us to make better software architecture. I will explain these sections in order to understand better this concept. This four section is the logical view, the development view, the process view and the physical view. The extra one is called: Use-Case View/Scenarios. The Logical view talks about class diagrams, communication diagram, sequence diagram , state machine diagram, and an object diagram. All of these in order to obtain an object model, what components will be made and how will the behave. The development view is about, component diagram and package diagram , all to the make the organization of the assets during the development work, in other words, which belongs to what. The process view is about concurrency and synchronized aspects. These mean activity diagram and timing diagram. The Physical vi...

This article talks about the SOLID principles which in fact as you known is an acronym that stands for five principles of object-oriented programming and design. Those principles allow us to avoid dependencies. So that means that the more things you depend on the greater the chance of something will go wrong. The principles are: Single Responsibility Principle, Open/Closed Principle, Liskov Substitution Principle, Interface Segregation Principle and Dependency Inversion Principle. I will talk about them quickly and explain why are they so important in our life as programmers. The single responsibility principle talks about that a class should have exactly one responsibility. That means that we have to have classes with a specific purpose and not mixed classes that if we erase something all the code went wrong or different. The open/closed principle talks about that a class should be open for extension but closed for modification. That means that we have to counter the tendency for...