Software Craftmanship


Robert C. Martin (also known as Uncle Bob) is a software engineer and an author of multiple books, in this podcast talk about software architecture, craftmanship and agile development methodology. The talk begins with Robert telling us how his experience as a software architect was and explaining that he thinks that there’s a bad practice at the industry. He thinks that drawing a line that divides the architect and de developers makes no sense, because the architects are the major participants at making code decisions but usually, they’re not well involved in the coding process, they are not familiarized.

In other hand, Robert talks about “software craftmanship”, this idea defines that a coder needs a real knowledge about coding, and this knowledge needs to be “learned” with the help of a teacher. Something like the “pairs programming”, this means that to really learn to program we need to watch and help another person programming. This idea has four statements (manifesto):
  1. Not only working software, but also well-crafted software
  2. Not only responding to chance, but also steadily adding value
  3. Not only individuals and interactions, but also a community of professionals
  4. Not only customer collaboration, but also productive partnerships

The first two are code related, in the first one encouraging the developers to be proud of the quality of what they code, using good practices. The second scope invite the developers to add value with every required change. The last statements talk about the relationships, between the developers, stakeholders, product owners and clients. These statements are based on the agile manifesto, we can consider this as a second part.

In conclusion, the podcast’s talks about some “knowledge and practices” that a developer must have or at least consider, based on agile development. I liked the podcast, because its related with subjects of my projects management class.

Comentarios

Publicar un comentario

Entradas populares de este blog

Hidden Figures

The movie was interesting, this was the first time I heard about it. The plot is simple, but interesting. The movie remind me to one of the articles we’ve previously read, about the software development to reach the moon. It was interesting to know a little bit more about the process that the NASA took to archive this. Notwithstanding that the movie plot doesn’t focused on something closely related to the software development or architecture (even if there’s some exploration about an IBM mainframe) , I think the important thing  is to reflex about  the difficult process that some projects need to get through. In this case, the project needed to analyze and take decisions as soon as possible, because the data became obsolete really fast. Also the data that needed to be reviewed was a lot, and in that time it was really hard due to the low processing power of the computers. In other hand, the movie talks about an important topic of our era, the racism. It’s wonderful to see...
Leer más

Microservices

The reading starts explaining the definition of "microservices", and as I understood the Microservices architecture is similar to the modular architecture. Let me explain, the author's describes that microservices architecture is a set of independently deployable services, this sounds like the "partion of funcionality inside modules". The author continues explaining why this approach is being more used nowadays and the advantages of this model against the monolothic one.  Later on, the article talks about how the developers are trying to build systems the same way we craft things in the real world, plugging together components (little parts that are there to perform some functionality and that together will conform a new thing). An interesting addition to this definition is that a component is a piece that can be "upgraded and replaced". Something interesting is that this architecture as I understand is designed to be implemented in cloud-based ap...
Leer más

The 4+1 View Model

The topics of the two videos are related with the article topic. Starting with the 4+1 video, I think this video information is like the topics of my class of software quality and tests. I’ve worked with some of the mentioned diagrams in the video. The new “scope” is the view encapsulation according to the different type of information that the diagram represents. But it makes sense to divide the diagrams with these criteria, because maybe the needed information may be different for whom is requesting it. And this scope will reduce and define properly the work to produce and deliver the diagrams. In other hand, the other video is a metaphor of the problem that is to design or select a paradigm to develop something, specially when the work is handled by a group. This is a result of the different approaches that each developer takes when defining or implementing requisites, each’s mind works and abstract the information differently. In this case the metaphor uses an elephant as the ...
Leer más