Ir al contenido principal

A kid? A kid just broke my program?

LNowadays is common to think that anyone can use your software. In this group of anyone, there is the group of people who know and people who doesn't. We, as software engineers, need to take I to consideration both sides because just anyone can get access to  information that might not be for them. A clear example of that is Netflix, which includes a restriction for kids, or YouTube and even Facebook.

To get to that point we need to think in our users,  and what they could do. In software engineering there are many methods to create these elements and to really analyze if they are really necessary restrictions or add-ons. On the other hand, we need to take into consideration the data that we are managing and to really send it in the correct way  to avoid people who steal our information even though that we are not that famous or important.

In the case of the movie  War Games, set at the begining of the internet connection as a service, who anyone can access just by a call and they didn't think the point where this method  could get them to. In this case, an important element to take into consideration is that the main company who had access to this kind of technology is the USA government. They didn't take into consideration the security to access to their systems and that everyone who had access to a computer was connected to them . We normally think that a password is something just enough to protect our information. In those days information was sent just as text or as signals so anyone could access  their secret programs with just a small imagination.

In this case, the movie presents a problem in the USA government access to  their secret war system and create an imaginary war, caused by a kid with just a telephone and enough time.  In this case the problem was generated due to  a backdoor in this program.  I consider that we should always take into account that  we need ways to access as developers  to our systems and to what we are creating, but this way needs to be a something more hidden such as the eggs in the book we are reading, up to the point where people cannot access or even forget about  this.  In this case we have learned from the problems that we've been through and  increased security up to the point of encryption, double access, keys, and so on which is a great advantage in our society. Also it is important to mention that in our are we cannot see at first sight the leaks, the problems, and what we are really doing, so we need to observe  and analyze our systems.

Comentarios

Entradas populares de este blog

What we should do?

Nowadays we think that computer science is a big factory, where even though that our offices are fancy and do not look like an office, we just program to generate more code, so get more money.  In this case, we think that coding is just an alone activity that does not include more activities, such as the whole software engineering process or something like that. As we have known,  there is a process that we should follow to generate code in a more efficient way and something that our users really need and when they need it. As time goes by, there was a point where we thought that cascade method was the ultimate idea and that its use was gonna stay forever and that its use was something that we will need to use for a while. We might get this idea from other engineers where they just get the requirements at one point and to change just for special moments accept the change. The basis is of this idea is that these type of engineers have got just enough time to really see...

“God is in the details.”

When we talk about architecture,  what we normally think are buildings, their characteristics, how they make beautiful our city. We do not think about the time architects take to build something big and beautiful, and how changes affect the whole project.   We know that architecture is something that has been evolving since the beginning of time, where people tried to build what they needed. But also, this science has been evolving and the way people build takes more time and there is science behind every decision they make.   When we think about the software we do not identify this process that we need to follow to create something functional, useful and that will be used, we think about the algorithms or complexity of the problem.  We are not used to planning, hear the necessities that people have and even the methodology that we should follow to keep our software for future generations.   I consider that this practice...