S/W Design and Architecture - JP

In this entry is about a new idea that has been growing into architectures, this is because it allows developers to turn complex systems or applications into microservices which can be modified because in this architecture they are modular, so when we need to make an update to the service or application, or only fix it, the process of implementing the changes is far more easier than it used to be, as we can see there are many advantages and benefits of using this new and trending type of architecture and in this entry we are going to talk more about how microservices work and my perspective as a software developer. Basically, microservices allow us to deploy parts of any system individually, as I mentioned this before this is because of the modularity that we can bring with the microservices architecture, thanks to the deployment of the individual parts the full deployment of the application is done far simpler because at the end we will be able to make changes without the nee...

This blog entry is about an article by Martin Fowler and this article is called “Is Design Dead?” and it is a really interesting reading, something really great of this article is how Martin talks about the different aspects of working in a project and makes a great job speaking of agile programming, this are used to improve the teamwork in a team or company and it uses the “client” as a part of the team, this is because in this type of programming it is used to make consultations to the client all the time, this is to make sure that the client is happy with the work we are doing and well the idea behind this kind of practice is great and I believe that nowadays many companies use this practice to work faster and better. However, the reading did not speak only about this, also it had some focus into design, specifically planned design and this is done by first listing all the issues that can happen in the project, this is because we will try to avoid this problems on every ite...

Ever since I read through the part of Ready Player One where the movie 'War Games' appears I've been thinking that we should watch it in class one day instead of the other media that we usually do watch (Silicon Valley). I even mentioned it to some of my classmates out loud. I know that watching it was probably planned in the course all along (I believ that it's in the nature of our professor to have things planned like that all along) but a tiny part of me still likes to believe that he overheard me saying it in class and thought 'you know what? yeah we should watch War Games one of these days' and so he mercifully got it and played it for us. Anyway, I really enjoyed the movie. Even though our professor warned us that the movie was old and that it showed a lot I don't quite believe it did. Not enough for that warning. Where it did, it didn't bother me at all. I think that when a movie is good like that my brain just accepts the universe i...

This blog entry is about an article by Martin Fowler and this article is called “Is Design Dead?” and it is a really interesting reading, something really great of this article is how Martin talks about the different aspects of working in a project and makes a great job speaking of agile programming, this are used to improve the teamwork in a team or company and it uses the “client” as a part of the team, this is because in this type of programming it is used to make consultations to the client all the time, this is to make sure that the client is happy with the work we are doing and well the idea behind this kind of practice is great and I believe that nowadays many companies use this practice to work faster and better. However, the reading did not speak only about this, also it had some focus into design, specifically planned design and this is done by first listing all the issues that can happen in the project, this is because we will try to avoid this problems on ever...

In this reading, written by Martin Fowler, entitled "Who Needs an Architect?", an attempt is made to explain, in a terrible but useful way, what an architect is, specifically, a software architect. In addition, the author tries to define what is a software architect through mental exercises, or some attempt with linguistic absurdities. On the other hand, the author talks about his epistolary exchanges with other characters in the area of information technology, in which the true definition of what a software architect is, or something similar, is discussed. Much of the text is devoted to this. Finally, the author exposes the expert developers, saying that only they know the true definition of what makes a component important, and so the author continues to expose the industry, in search of a true definition for software architect.