A01375332 - Arquitectura de software

It was a funny adaptation of the six blind men fabled repurposed to programming and software. I believe it managed to transmit the lesson It wanted to give, but a final explanation in not fable form would have been appreciated. Like it was really easy after watching the video about the 4 + 1 View Model, but otherwise that part of the fable would have probably flown over my head, and just by reading without thinking in the order of the model I had issues trying to grasp which programmer was which view. For example, the programmer not-programmer confused me about which view they were supposed to be, although I suppose it is in the same order that the model is presented in the graph of the first video. So, I would guess the fourth “programmer” would be the development view in the 4+1 View Model, but after noticing the oscilloscope and the multimeter I realized that she represented the Physical View as it is the one involved with hardware. The fifth programmer was also a mystery for the

  The SOLID principles are really good advice and were explained in a really simple way during this article. Some of them I had already heard as in the past I have read one of Uncle Bob’s books during the Videogame project course. The Single Responsibility Principle is the only one of the principles that until now I always have in mind while writing classes, although being honest just as the article says it is not always that straightforward what would be considered doing only one thing, so sometimes I may not apply it perfectly. The Open/Closed Principle and the Liskov Substitution Principle those are principles that are new to me and certainly go against some of the things I knew.   Because I had learned to use inheritance in those situations, although reading the article I agree that abusing inheritance may not always be a good idea as it may leave the code in an unpleasant state or generate side effects. The Interface Segregation Principle I never had thought about doing that,

I have previously approached microservices during our Web development course, although we had a lot of issues with that course such as the pacing being too slow due to some students from other career getting stuck several times. And we also had issues with us not knowing the basics of web development and then teaching us microservices telling us about how they solve a lot of issues, but us having no idea what those issues were. Curiously, we were taught about microservices using Amazon console, business that the article mentioned several times. Now knowing a bit more about web and after reading the article that finally explained some of the problems they solve, I begin to appreciate them more and would like to learn to better use them although with a better pacing. It sounds indeed a lot better to only have to change a service instead of changing the whole code and then having to rebuild and using them it was really comfortable to use python to manage the database and only having to