S/W Design and Architecture - JP

Even though I believe the movie is a dramatized representation of the events, I also believe that, at the time, at least some people at NASA came to that realization. In the movie it is shown very explicitly when Katherine has to tell Al Harrisson (the boss - already on the moon guy) where she goes for forty minutes a day, and why she does it. Nowadays it can be observed in highly productive environments such as big companies, and organizations alike, where non-oppresion organically becomes part of the culture (like it happens in the movie, but maybe not that dramatically). I'm not sure how or why exactly, but I have a feeling that an one can use the fact that an oppresive culture slows down progrss as an argument for proving human equality to a certain extent. The body of the argument or it's specifiications are content for some other, much longer blog post (maybe even another medium). On an entirely different topic, another thing that I liked about the m...

Today I'll talk about the the 4+1 view model, which basically 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 fourth 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 ...

Hi everyone! In this week, we'll talk about SOLID principles. So let's get to it. The first principle called "Single Responsibility Principle" is one of the easiest to understand but at the same time one of the hardest to apply. To get a class to have only one responsibility, there has to be a very good software design, but developers must also devote time to code analysis (especially those that are dedicated to maintenance). Otherwise, programmers will simply do what is faster and simpler: Add code wherever it is going to work (Apparently) what was requested by clients. The principles with which I do not agree at all are "Open / Closed Principle" and "Liskov Substitution Principle" since I believe that the base classes should have the flexibility to be modified as long as the repercussions of the modification are understood. On the other hand, I think that classes must certainly be made to be extended or replaced by functions, si...

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...