Ir al contenido principal

Software Craftmanship

In this podcast they talked about a topic that I had already heard, or at least they talked about topics that I had already seen. Bob Martin talks about the two types of people that exist in software engineering, which are architects and programmers. Architects are the people who are responsible for making the important decisions on the project, while programmers are the people who do the work of making the project code and achieving the project goals.

Personally, I think that the decisions of a project should be made among the whole development team, because in this way you can discover elements that the architect didn't see at the beginning and in this way everyone will agree and avoid problems in the future.

Wikipedia gives us the following definition of "Software":

Software craftsmanship is an approach to software development that emphasizes the coding skills of the software developers. It is a response by software developers to the perceived ills of the mainstream software industry, including the prioritization of financial concerns over developer accountability.

I had not heard this concept before, however, it became very interesting to me as Bob talks about it and so I decided to look for a definition to better understand it. I like it because this way the developer is more involved in the decisions, as well as the achievements and consequences of the decisions.

As a conclusion and opinion, with the articles read lately and now with this podcast, it makes me see architecture in different ways. As well as the people who get involved and how they classify themselves. This gives me the opportunity to choose the one I think is most suitable and apply it to my professional life. But I agree that programmers should be taken into account for the important decisions of the project they are working on, their knowledge and experience can help a lot to find improvements.

Comentarios

Entradas populares de este blog

Who Needs an Architect?

In this article the author talks about the concept of architecture and what it means to him. At the beginning he starts to give the IEEE definition, and it is very interesting to see what he thinks about this definition, giving his opinion about the parts in which he agrees and the parts in which he disagrees. The author defines two types of architects, these are: Architectus Reloadus: is the person who makes all the important decisions. The architect does this because a single mind is needed to ensure a system’s conceptual integrity, and perhaps because the architect doesn’t think that the team members are sufficiently skilled to make those decisions. Often, such decisions must be made early on so that everyone else has a plan to follow. Architectus Oryzus : This kind of architect must be very aware of what’s going on in the project, looking out for important issues and tackling them before they become a serious problem. The most important activity of Architectus Oryzus is ...

Hidden Figures

When the film started, I thought I wouldn't like it and that I would just talk about the story of the take-off of Apollo 11. However, I liked Katherine's story. It's very admirable the great effort she made to achieve her dreams and to stand out among men. Because at that time women were not considered for the important jobs or could not aspire to great positions. However, she struggled to finish her studies and realize her dream of working at NASA. In the beginning it was quite difficult for others to take into account, because the society was very racist, and they always separated the whites from the blacks. However, his great knowledge proved to be superior to that of the other men at NASA and with this he achieved a great change in society. She had to suffer from ridicule, injustice, abuse and racism. That is why I greatly admire her great courage to excel despite having all those obstacles in her way. In my opinion, I hate the ideas of a society that does not value...

Software Architecture

This chapter was very interesting for me and helped me to see the great importance of software architecture. As well as the functions it has and the benefits we have by paying attention to this step of the software development process. For this we have to consider with the reading of other chapters of the class, that there are different types of software architecture, and that we have to choose the one that more adapts to our project or to what we want to do. You also have to take into account if you already have a certain progress or if you start with an already established base. All this must be taken into account to choose the best option. I like that the author emphasizes points like the points of view, the concept of software architecture, as well as when and where the software architecture should be done, the functions that the development process has, he talks the same about the components, connection components and then he talks about the architecture styles, which are: No ...