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

Popular posts from this blog

Who needs an archiect?

I n this blog entry we are going to talk about an article written by Martin Flowers entitled, “Who needs an architect”, were it talks about software architecture (kind of obvious don’t you think) and the architect's role in a software development team. To be honest, a didn’t get the author’s purpose of the article, but I think I have got the general idea, so I can review this properly. On the article the author gives many two explanations the software architecture, one of them is quoted by someone else which basically says that a high level concept of a system is only visible (or significant) to developers, now, for me this is really abstract, because I don’t thing it applies to all the projects of this topic, but the second one which is given by the author himself says that the architecture is a a shared understanding of the system design by all of the expert developers involved in the Project, now this makes more sense to me because we can understand that not only the d...

Ethical Reflection on Ready Player One

Todays blog is the last one!!!!!! It has been quite a journey, but as everything, its time to end this. On today’s blog we are going to talk about a book, Ready Player One, written by Ernest Cline, this is the book that everyone in my class has been reading during the semester, and it was really, really good, I actually enjoyed it a lot. The plot is quite simple, it talks about a kid called Wade Watts, in a world were the actual real world is kind of a huge disaster for not saying other words, but in the book exist another world, a virtual one called the Oasis, were technically everyone plays it, because it was a whole new world, not only a videogame, in there people can have jobs, meet people, study in schools. The creator of the Oasis was James Halliday, and I say was because in the book he is dead, and after his dead he created 3 easter eggs that, when a player has the three, that player will own the oasis, and be the richest person in the world, and that is the goal of our dear...

The 4+1 View Model

On today’s blog we are going to talk about the 4+1 view model, which all of this was taken from two videos. This model says that, when we are creating software we need to focus on 4 things: The logical view: which is the logical design of the software The development view: the way the program interacts between its components The process view: the way the program functions The physical view: the way the software and the hardware interact between each other Now to explain more these 4 things, the logical view refers on what are we going to build, not the actual code, but the design and logic it will have, a good example of it is a class diagram.   The development view refers on how the program is organized and how it communicates between its own parts, the component may be a good example of this because it shows exactly that, how is organized and how it communicates to work. The one that refers on how the program works is the process view, it...