WarGames

The movie is funny and attractive, at the beginning I was not expecting anything from the film, in fact I though the subject was going to be different from what I imagined when I read the reference in Ready Player One. The plot is amazing but dumb, maybe it was true, I do not know but the going of a kid being able to hack a super sophisticated army computer and initialize the World War 3 prelude is as I said amazing but realy dumb.

In other hand the other part of the movie, the militars and scientists from the base are again, dumb, the lack of mechanisms and plans to aboard a situation like the one presented in the movie is surpressingly worrying, the whole movie is supported with this premise, the lack of capacity of the staff of the base to deal with the idea of ​​someone being capable to hack their super sophistifies device so easily and their incapacity to detect and stop the computer malfunctioning

As an engineering I think the movie touch important subjects of our area, the importance in certain level of the documentation, the pros and cons of using backdoors, the cons of the blind pride of an engineer towards their systems (if the scientists chief had not been so proud arguing that it was not possible to a young kid to hack their machine alone withouth russian help, all the problem could had been resolved earlier). I think the problem could had been resolved easily if the scientists would have took some time to document what to do or how to verify the malfunctioning or search for errors in the developers code.

I do not want to sound like a critic, I really enjoyed the whole movie, I really felt tension at the end when the team was trying to avoid the missiles launch, the movie is really good, and I like that now I can "fill" the picture the next time I read Ready Player One.

Comentarios

Publicar un comentario

Entradas populares de este blog

Hidden Figures

The movie was interesting, this was the first time I heard about it. The plot is simple, but interesting. The movie remind me to one of the articles we’ve previously read, about the software development to reach the moon. It was interesting to know a little bit more about the process that the NASA took to archive this. Notwithstanding that the movie plot doesn’t focused on something closely related to the software development or architecture (even if there’s some exploration about an IBM mainframe) , I think the important thing  is to reflex about  the difficult process that some projects need to get through. In this case, the project needed to analyze and take decisions as soon as possible, because the data became obsolete really fast. Also the data that needed to be reviewed was a lot, and in that time it was really hard due to the low processing power of the computers. In other hand, the movie talks about an important topic of our era, the racism. It’s wonderful to see...
Leer más

Microservices

The reading starts explaining the definition of "microservices", and as I understood the Microservices architecture is similar to the modular architecture. Let me explain, the author's describes that microservices architecture is a set of independently deployable services, this sounds like the "partion of funcionality inside modules". The author continues explaining why this approach is being more used nowadays and the advantages of this model against the monolothic one.  Later on, the article talks about how the developers are trying to build systems the same way we craft things in the real world, plugging together components (little parts that are there to perform some functionality and that together will conform a new thing). An interesting addition to this definition is that a component is a piece that can be "upgraded and replaced". Something interesting is that this architecture as I understand is designed to be implemented in cloud-based ap...
Leer más

The 4+1 View Model

The topics of the two videos are related with the article topic. Starting with the 4+1 video, I think this video information is like the topics of my class of software quality and tests. I’ve worked with some of the mentioned diagrams in the video. The new “scope” is the view encapsulation according to the different type of information that the diagram represents. But it makes sense to divide the diagrams with these criteria, because maybe the needed information may be different for whom is requesting it. And this scope will reduce and define properly the work to produce and deliver the diagrams. In other hand, the other video is a metaphor of the problem that is to design or select a paradigm to develop something, specially when the work is handled by a group. This is a result of the different approaches that each developer takes when defining or implementing requisites, each’s mind works and abstract the information differently. In this case the metaphor uses an elephant as the ...
Leer más