1-1: About.me

Hi everyone, my name is Fabián Camp Mussa. Being completely honest, I really don't have an expectation about this course but I'm pretty sure that with this course I will learn a lot of interesting and challenging things. I think that one of that challenging things will be learning Ruby language (hope won't happen).

Talking about me I like a lot to spend my free time reading a novel, playing video games, writing stories or poetry and listening to music. Also, I spend my time watching The Witcher series I think the Netflix adaptation its pretty good, so I recommend it.

Finally, I will put all my effort to learn all the things the teacher has to teach us and being able to use this knowledge someday in the future.

Comentarios

Publicar un comentario

Entradas populares de este blog

Summary Second Period

Imagen
So far we have been seeing a lot of different things this second period. So it is important to make a summary of all that topics that covered this second period. In this occasion the second record exam will cover the following topics: Design Patterns covered in the theory book. Microservices. SOLID principles. The 4+1 view model. As I said earlier, this blog entry will be a summary of all these topics but I encourage you to see all your notes, programming activities and even read again the theory book of Olsen. Design Patterns Design Patterns are typical solutions to commonly occurring problems in software design. These patterns were proposed by the Gang of Four: Erich Gamma, John Vlissides, Ralph Johnson and Richard Helm. Template Method Pattern The Template Method Pattern is a behavioral design pattern that defines a skeleton of an algorithm in the superclass but lets subclasses override specific steps of the algorithm without changing its structure. In this kind o
Leer más

2-3: Microservices

We can define Microservices as an architectural style which approach is to develop a single application as a suite of small services, each of them, running its own processes and communicating via lightweight mechanisms, often Microservices uses an HTTP resource API. We also need to compare a traditional monolithic application in order to compare and to give a better explanation of what is a Microservice. A monolithic application puts all its functionality into a single process and scales by replicating the monolith on multiple servers. But, microservices do not work like this, a microservices architecture puts each element of functionality into a separate service and scales by distributing these services across servers, replicating as needed. Having this context, we can have a better idea of what is a Microservice. Now, it is time to enumerate the important characteristics of a Microservice Architecture, have in mind that it does not exist a silver bullet in development so, no
Leer más

2-4: Understanding the SOLID Principles

The first thing that came to my mind when I read the title of the lecture was, what does SOLID stands for? So, first let me contextualize what is SOLID and then explain the meaning of all the letters in this acronym. As I said before, SOLID is an acronym that stands for five principles of object-oriented programming and design. The objective of these principles is the avoidance of dependencies, because the more things you depend on, the greater the chance something will go definitively wrong; these 5 principles are the following ones: S => Single Responsibility Principle (SRP): States that a class should have exactly one responsibility. This means, that it should have exactly one reason (or one class of reasons) that cause it to be changed; nevertheless, many programmers have the superstition about the systems they maintain things like "Don't touch this module" or the difficult task of selecting that single responsibility. O => Open/Close Principle (OCP): St
Leer más