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

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

https://www.youtube.com/watch?v=YSkGmkH8h0Q

Nowadays we tend to talk about elements of service  as components and big companies tend to create new ways to sell you just what you need with the name " microservice". In this case what they tell you is that the whole thing they offer you, you can choose what you need or what you can pay.  An important company that does that is Amazon which created a big infrastructure for developers to use. In this case, they include many elements such as database management, access management, and so on. This is an important improvement in life due to the fact that companies do not need to buy everything or rent something bigger for their needs. I consider that microservice is an important element in our life due to the fact that tech companies do not have the infrastructure needed to really show what they need. In this case, bigger companies just offer what they need. This is an important fact because technology changes every day and to be up to date is really expensive and we n...

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