Ir al contenido principal

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 and understand how to work. Also, their technology has not changed in a while, in another way, their technology changes in smaller steps.

In our area, we have changed every day and in this case,  they affect the way we think and the way our clients' necessities change every day.  As the speaker talks about it, we find ourselves in the point where we believe that we just need to program and generate more code and more code, up to the point where we do not really understand what we are doing. That is the idea of many coders,  we just programme to find a solution. In this case,  the solution might change and might not be the best way to really solve the problem, but in the point where we got to it, it might be. 

Something that I'm not okay with is the point where he mentions that the business cases that we've been told to develop to really understand a problem are something that we should not do. In this case, I consider that these elements are important to generate due to the fact that we should understand where we are working and what we need to do. 

Comentarios

Publicar un comentario

Entradas populares de este blog

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...
Publicar un comentario
Leer más

“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...
Publicar un comentario
Leer más