Ir al contenido principal

“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, of planning and following some methodologies that might facilitate the development is something that we are used to ignoring. Anyway, and personally speaking,  I try to follow this kind of methodologies due to the fact that they give you examples of what you expected to do.  When I try to use these methodologies is when I do not know what to do, or when the problem is really complex and I do not know where to start. 

Another thing that we might be loosing without using these methodologies, is the path of activities that you need to do first.  As programmers, we might have some big projects, but we do not use a methodology, we just program and try to solve the problem.  I think that we need to see the problem from the outer space to really understand and do not program twice or more than we should. 

According to the best practices in software engineering  from Pressman, there are some activities that we should be following:
  1. Be agile
  2. Focus on quality at every  step
  3. Be ready to adapt
  4. Build an effective team
  5. Establichmechanism for communication and  coordination
  6. Manage Change
  7. Asses risk
  8. Create work products that provide value for others
  9.  Divide and conquer
  10. Understand the use of abstraction
  11. Strive for consistency
  12. Focus on the transfer of information
  13. Build software that exhibits effective modularity
  14. Look for patterns
  15. When possible represent the problem and its  solution form a number of different perspectives
  16. Remember that someone will maintain  the software 
 
In this case, we should follow these activities as our mantra or laws, but we think that we just program. I consider that this is due to the fact that we, as an area,  have been developing since the 1950s as a science and where create a methodology. Our case is that we are still learning how to really develop with the changes in technology that changes every day.  We are okay as science  but we as students should follow and treat as the way that experts have been developing and we have been taught and do not follow the malpractices.

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...

I am blind without my glasses

As far as we have learned in all our classes, we should always think of our clients need and uses. But after we get the requirements, a war starts due to the fact that everyone wants to set their point or perspective as the most important one. As we have learned from this case, there is no wrong perspective, but a blindfold one. We tend to seek out what we know and to think that this will be the right answer,  because that is what our story and our world works, but there are many other options.  In this case, I can relate this case to what we live everyday on our classes, where we need to create teams with our classmates. Normally we create these teams with our friends even though they have got the same perspective  and abilities as us. This case becomes a problem because when we need to understand what the client needs and desires we can only see one way of it, when there are many others. We need to think in our users, that could be our friend  or a stranger in an...

Everyone is relevant in our life

As life has been going on, and as science has been evolving, we find out that there were more people doing certain things that we recognize one or two people.  We normally think about the faces of the company, Jobs, Gates, and so on, but not on the faces that really made it come true. That was the case of the Apollo mission, where more than one University or even one part of the government has part of it, but we only think about Aldrin, Armnstrong and Nixon.  And we normanny forget the ones that really made it possible, the scientists, mathematicians, phisics, engineers and so on.  Inside this minority group there are other groups that are part of these groups, but because of  their time,  they were not recognized of doing this job.   Personally there's one story that I like, where they say that Kennedy was going to visit the headquarters of the  mission, and due to the importance of it, and the agenda that was following, he needed to visit this p...