Software Craftsmanship

We are still in the software crisis, and because of that, we still need to develop new methodoligies and strategies in order to mitigate as much as we can this problem. When programming and software engineering arrived, at the first stages people relied on cascade methods, meaning that the phases of a project were done straight. This time, almost everyday we are seeing new programming languages being created, new libraries, frameworks, cloud tools, and technologies that came to change how we develop and operate applications (for example Docker containers and Kubernetes). 

Engineers should need to be prepared for a correct structure of their code, design and project. Corporations and organizations should not try to get better their product or solution by adding new methods or practices, instead, they should rather focus in the responsibles of generating the code, I mean, the programmers or coders. 

I like the analogy of programmers being craftsmen. After hearing the podcast I had curiosity to properly read the Manifesto for Software Craftsmanship. One point caught my attention: 

Not only individuals and interactions, but also a community of professionals

Programmers must not only pay attention to customers, but to their partners around the world. Today, I am aware that there are several communities work together to develop new products and/or services (open source projects like Cloud Native). Though, their product must not evaluate the software, the software must be evaluated by the design, structure, programmed aka well-crafted software.

To conclude, I would like to extend an invitation to every computer science student, programmer and future engineer to learn more about this. We should grow as a community, strengthening the partnership, adding value to their products and above all, have the will to teach and help educate the future generations  in the discipline to become the ideal professionals.

Manifesto of Software Craftsmanship. Available in https://manifesto.softwarecraftsmanship.org/

Comentarios

Publicar un comentario

Entradas más populares de este blog

Microservices

Monolith applications is now a thing from the past. In order to build scalable and efficient applications, a new architectural style has come to try and solve the problems of deploying again and again the entire  code when a single change or modifications has been made to a single part of the project. I found logically correct to segment the application into units called services (each one with a specific purpose) and handle it like an independent application.  Web development and applications are growing, and considering that this will keep trending, HTTP is used as a communication method between services. How it is properly done? Through this incredible and standardized interfaces called APIs (Application Programming Interfaces). Since I learned Javascript,  when defining the routes I was already thinking in the required methods (GET, POST; PUT, DELETE, etc) and the scope for each one of them. Therefore, knowing about HTTP and APis will be (if it is not now) a necessary skill.  I was
Leer más

Is Design Dead

Thsi week's activity... software design... it is said that the more senior you become, the higher level you go through projects and, well... maybe there is a bit of reason of software builders losing respect to the ones designing. But to be able to design such software systems, you need to have experience and had the whole picture of how systems work. You do not need to be specialized in a product or service, you just need to know how they work and interact with other components (perhaps like a black box). Where I work, I interact daily with all types of people. There are software engineers, cloud engineers, architects, consultants and project managers. With my two years meeting different professionals and being in different areas, I would like to tell more about the place I work.  Currently, I am a Cloud Solution Engineer. The job is a mixture of both hard and soft skills, but most of the time I am interacting with customers designing solutions, troubleshooting issues, presenting
Leer más

Who needs an architect?

This week's article was a little short, but there are many ideas that can I can come up with. Basically, what the article was trying to do was to show the importance of architects, especially software architects. We have come a long way on our major of comptuer science, and it is time to start thinking big. Most of the projects we have worked in school are small projects which almost all of them consisted on a set of approximately seven classes, a database and a web server. Maybe for these projects you do not need a special person to check or validate the whole system.  But as the world progresses, organizations require bigger and more complex information systems and applications. Many of them involve the use of applications interacting with each other. Now, with that being said a special role or person is needed for a whole system to work. This includes knowing how a system interacts with a database, an application programming interface (APIs), with other classes, operating system
Leer más