Ir al contenido principal

What we should do?

A good programmer is not made by how fast he or she can solve a problem, but someone who can help to maintain a whole system  by committing the best practices he or she has been taught.  In this case, what I am referring to is that we are used to hear or think that someone is a good programmer because they  solve first an exam or even because they know all the library of a language, but  that is not right.

There are many elements that can be related to a programming language, but a good practice should be the main one we are searching for ( besides the client's desire). In this case we should consider that everything that we are doing will be running on someone's computer or server and that  there have been many years where people have develop this science up to the point where we have ground rules to understand it or to make it better.

As we have seen, the gang of four has develop some pattern  elements to create a whole program, but these ideas are related to all software engineering theory that we have seen. As we can understand from Pressman's book, there are many steps to follow as a software engineer, and there are many rules we should follow, all of them depend on our client and on our user.  And as we have learned,  if someone has already created something, why not to use it in our program.

In this case, what Edward Guinness has developed is an acronym to  summarize the basic principles on object-oriented languages. It is important to mention that it might apply to other languages but not as a whole. He has developed SOLID principles, where they look forward to make object-oriented programming less redundant, easier to understand and based on the user's needs and the architecture design paradigm.

In the case of architecture design, the main idea is to understand what the user needs, what we have built to solve its problem and  how all the elements are connected. When we develop something we need to follow a process that will give us all the activities or requirements of a client, and with that we can build something.  As we have learned, the way to solve these actions is to develop a plan  and to test whatever we find in our way, but the correct way to develop is to define the smallest activity and  from that element  and all what it needs, to create modules and solve the problem.

Following the last idea and connect with the SOLID principles, we now can understand what we have been doing and to make it better for everyone. We might live forever, o we might not, so we need to create something people understands at first sight and that they will make it better, not to destroy it.  I consider that principles such as SOLID should be ground rules to specific programs and that we should test them, as students, for better understanding and to really learn their use. We have learned many rules and we might forget them but if we understand why we need them we might never forget them.

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

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

Is UX the new design?

Nowadays there  are many ways  to create a new project, a new program, or even a new add-on, but we  live in a society  that lives in the time  where changes are needed  so soon that  sometimes design  is  not done  when it is supposed to, or a methodology is not followed, because we are focused on the project and not  the  way we develop the project.  These ideas were affected by the way technology, clients and users change their ideas and necessities.  We have been developing new ways to satisfy them, but in the process, we have been forgetting the steps that we need to follow to correctly create a new thing. Sometimes we try to develop the necessities that we think that the client has to have,  but we are not truthly sure about it.   An example of what has been told is the point where we start using Extreme Programming to develop a project. When we use this methodology, we tend to forge...
Publicar un comentario
Leer más