Software Craftsmanship

This podcast about software craftsmanship made me think about how we learn from others, how we can teach others and in software development there is a notion of coders who first learn from someone and in the podcast Bob makes a reference in the software and how someone does not stop learning software, you learn software all the rime and even though it would be ideal to have someone show you how things are done, the first steps into programming, if you do not have a mentor you can always learn by trial and error. There are many positive things into being able to learn from someone and for you to teach someone and it is a rich experience and in the manifesto of software craftsmanship gives us a small insight into how advices are written in a few lines of text, and the important ideas are summarized in four principal learnings that takes us to the idea that software craftmanship allows us to be better software developers and protectionists.

In this podcast there is also the idea that the industry should know what a software architect is and there are some tools that Bob believes are important for coders to improve, IDEs are one of them, source control and bug tracking systems are others and overall it’s important for us software engineers to know that collaboration is a great tool for everyone and by letting someone teach you something perhaps this will allow you to understand it better and finally the cohesion of the team its important and you should never forget what the client wants.

Comentarios

Entradas populares de este blog

Ethical Reflection on Ready Player One

Microservices

Is design dead?