S/W Design and Architecture

Morrow wrote in his autobiography that he’d left GSS because ... he felt that the OASIS had evolved into something horrible. “It had become a self-imposed prison for humanity,” he wrote. “A pleasant place for the world to hide from its problems while human civilization slowly collapses, primarily due to neglect.” (p. 120) I deeply agree with this quote, I believe that the world would hide its problems inside Oasis, we can see that the world it's collapsing when you see the conditions in which Parzival was living on, he was living in a kinda dump. I'd love to test the Oasis and see how VR has grown. For me VR it's an incredible technology we can take advantage of, currently, I'm taking a class of VR and I can say I'm really impressed how much it has grown, it's really like if you are in another world. Sometimes I forget where I am and nowadays VR it's not as developed as in Ready Player One, so I understand how easy it can get to lost in the game.  I

Today's blog is about Microservices architectural style, this refers to the approach of developing a single application as a suite of small services. As I was reading the article I really understood that I did not know anything about Microservices, I had a bearly idea about it but I was on the lost path. The authors give some characteristics of microservices and I will list them. *Componentization via Services *Organized around Business Capabilities *Product not Projects *Smart endpoints and dumb pipes *Decentralized Governance *Decentralized Data Management *Design for failure *Infrastructure Automation *Evoluionary Design Every one of these explains to us what the Microservice should have, I will explain some of them.  *Componentization via Services: Components will be set up into libraries that will be broken down into services. *Design for failure: Software must tolerate the failure of the external services *Smart endpoints and dumb pipes: E

UML diagrams are used to describe the system, the three types of diagrams are, Structure diagrams, Behavior diagrams and Integration diagrams. UML it's only a way to convey knowledge from one place to another. As we can see UML it's only a design tool. There are other useful tools that help us a lot, and it's called system architecture or software architecture, like blueprints in like in construction,  help with the design of the building. One of these helpful part of system architecture it's called 4+1 View Model. The first part of the 4+1 model is the logical one, that states what sort of objects we¿re going to build, here are described all the classes, objects and logistics of the project.  The second one it's called development view, which states to the developer how the system is organized, which part is connected to what. It's often called the "Implementation view". The process is our third view in the 4+1 view model, it describes the concur

These 5 principles are great advice discovered by Robert Martin also known as "Uncle Bob", the same we heard a podcast blog entrance ago. His acronym makes it easier for learning his principles, whenever we're developing object-oriented programs. The 5 principles are listed down below: S ingle Responsibility Principle (SRP): States that any class should have only one responsibility, although the author at some point says that there could be some classes that have 2 responsibilities. As the author continued with his explanation it confused me a little bit, because he contradicts himself. Maybe it could be clearer with the practice, as it's with all things in life.  O pen/Closed Principle (OPC): States that a class or a function should be open for extension but closed for modification. It attempts to counter the tendency for object-oriented code to become easy to be broken.  When adding new behaviour you need to leave alone the base classes instead you

So Ernest Cline does an excellent job, building up the expectative in Ready Player One, about WarGames. The first time I heard about this movie was in the book Ready Player One, I did not understand the reference about this movie, it's supposed to be one of the favourites movies of one of the main characters. I was born in 1996 so this movie was a bit old for me. Being a guy who likes geek stuff this was so awesome for me.  A professor of mine who is one of the professors who teaches me compilers told the class that this movie was one of the main reasons for him and most of the people he knows to study a major related with computer science. So we were watching a piece of history. At first, I was so amazed to watch those old computers, they were so big and yet for the age so powerful. I was intrigued by how they have all this set up they need to have to program. But not only I was intrigued by the computers, but I also was surprised about how a 14-year-oldish boy can almost start

Having working software is not enough. We need to have well-crafted software. This is one of the many interesting points  Uncle Bob  focused on his interview in the  software engineering radio podcast . He is a software engineer who co-wrote the Manifesto Software and leads “Uncle Bob Consulting LLC” and “Clean Coders” companies where he hosts videos based on his experiences and books, also he writes and consults codes. He became an architect and designed for a while but after that, he left it because it wasn`t his thing, despite this, he thinks that  architects shouldn’t be separated from the coders because  if they will separate them, architects make important decisions but they don’t know how to react because they aren't coding experts. (If all the team Will be architects, they should make wise decisions) Then Bob starts to explain about software craftsmanship which is an approach to  software development  that emphasizes the coding skills of the  software developers