Software Craftsmanship with Bob Martin

I liked this podcast, it has some strong opinions from Bob Martin that even considering that the podcast is from 10 years ago, are really applicable for the industry of the software. I think that programming is very satisfying just for some of the reasons that are described as the craftsmanship, like the art that involves maintaining the readability and the refactoring always clear into the code, and not getting totally disconnected from the design even when into the Bob's preferences around the agile methodologies.

One of the points that got my attention is the way he expresses himself about the design and architecture documents (and other documents as well) letting us know that the agile methodologies can produce outputs of any kind, that this mentality as programmers of not producing any kind of documents while working agile it's just wrong, and we shall just be used to get great practices into our own process of making software.

Other topic that it's touch is this idea of software craftsmanship and the pride that involves participating into this. Here are mentioned two aspects, one is the production that involves making software, and the other one is the intrinsic value behind the high degree of complexity and the code itself, the appropriation of each project that it's behind the code.

The last topic that actually move me it's the factor that the actual programmers are worried about moving the code and modifying anything because they doesn't understand it as it should happen. This is a quality that I've effort a lot, to be capable to understand code and to be sure that it will work well, because I'm more worry about the idea and the process to be successful than just to get the values by trial and error. All this, at least for me, makes a special value because one programmer is capable of internalize the knowledge and to be more inventive and creative around the software innovation.