Skip to main content

War Games


On today’s blog I’m going to talk about a movie released in 1983, War Games, which has been directed by John Badham.

The movie shows the story of David Lightman, a kid who is kin of a genius in topics of computer science, the plots consists of how this kid started to hack to the system of the US military by accident because he thought he was hacking a videogame company instead, when he hacks the system he discovers a simulation created by the military called Thermonuclear War, now, Lightman thinks is a game so he stars to play it, the “game” consist on two sides or teams, the USSR or the United States, and after choosing sides, the teams decides where to launch a nuclear bomb, all of this is situated during the Cold war so the simulation has  that theme; the problem starts when the simulation actually prepares to launch real bombs and Lightman gets caught by the government because of the hacking, then when they explain the situation to him he finds the creator of the simulation and then together they stop it.

I watched this movie during my class of Software Architecture, and I must say that I enjoyed it, I have heard about the movie before but never got the chance to actually see it, and I think I should have done it a long time ago, this movie shows one of the reasons of how important is the computer science in the actual world, unfortunately it also shows how dangerous it is, but like all the things that do good for the people, it can also harm them, nowadays the security is way more better and advance so that this cases never happen but is never to cautious to keep improving the security to really ensure it will never happen.

Comments

Post a Comment

Popular posts from this blog

Is Design Dead?

On today’s entry we are going to talk about the article “Is design dead?”, which talks about how the design has been changing through the years and how the good practices were developed in order to create a good design. Is no lie that for all the people that develops software, is kind of difficult to come up with a good design because of the lack of and standards to create it, other areas may have standards or even a methodology, but not us. Because of these needs, developers have created a bunch of good practices, not to create, but to reach a good design probably in a 85% of success. For example, a good practice is a that the code we create has to be modular in order to make corrections or complete alterations in a easier, this changes may occur for many reasons, manteinance, update the information or just to simply chage the entire code to something more efficient, the same goes to the design, but the problem is that a design is more difficult to modify when is already d...
Post a Comment
Read more

Microservices

On today’s blog entry we are going to talk about the Microservices architecture. This architecture has an approach where when we are developing a single app, we develop it as lots of small services, each of them running on its own process and communicating with each other with something that can bind them together. Now I have already used microservices without knowing I was actually using them, perhaps this architecture is quite intuitive for best practices or something like that, but anyway the author of the article gives some characteristics about this which are the following: ·          Componentization via Services: The components of the microservice need to be gather into libraries that will be used later on by the microservice to communicate with remote parts of the whole program. ·          Organized around Business Capabilities: This characteristic refers that we need to create divisions, e...
Post a Comment
Read more

Understanding the SOLID principles

On today’s blog we are going to talk about the SOLID principles, which were discovered by Robert Martin, the famous Uncle Bob from the podcast of the previous entry. This principles are recommended to be used whenever someone wants to create an object oriented program. There are 5 principles where the acronym SOLID comes from which are the following S ingle Responsibility Principle (SRP) -> it says that any class should only have one responsibility. Yet, the author ends up saying that there might be some classes that have two responsibilities (the invoicing class that has some logging routines). In the end, I didn’t understand this principle well because I found the explanation confusing (as the author said, practice is much more difficult than theory).  O pen/Closed Principle (OPC) -> open extension but closed modification Although the author says that if you change a parent class method it might kill another part of the ...
Post a Comment
Read more