Software Craftsmanship

Software Craftsmanship with Bob Martin


This week I am going to talk about the podcast “Software Craftsmanship with Bob Martin”
First of all, Bob, also known as uncle Bob, is a software developer but he is also an architect and many other things but the center of the idea are those two, but what he likes most is developing software, he loves to have the hands in the keyboard.

To be in context, uncle Bob is founder of a company that offers mentoring, training help to the code teams to adapt and get better practices. One of the things he emphasizes is that people who take decisions as architect or team leader should be involucrate in the coding process, I really liked the phrase, they need to have the fingers on the keyboard.

The software craftsmanship as Bob Martin tells is a way where new developers that are involved in programming world can learn, not only coding techniques, from the more experimented people in the industry. The basic idea is that a master or mentor whose labor is to share the knowledge, tools and skills for code, document, or work in teams with the “new guys”. Why? The goal is to create a community for developer to developers, like happens with lawyers or doctors where all the knowledge is flowing from one person to another changing the way in that the community works.

Also, Bob mentioned that you have to learn many things when you are working in order to get a high-quality code, because the software creation is a process for learning how to code it. Besides if you learn many ways to refactor and optimize the code and of course, you follow them, you will be proud of it when you see your code is not a mess.

The radio announcer asked Bob for some good practices for developing high quality software, Bob´s answer was

  • ·       Test of development.
  • ·       Check the code continuously and when some unit test fail, stop the developing process, check the code and find why and where the code failed.
  • ·       Pear programming and extreme programming.

Comentarios

Publicar un comentario

Entradas populares de este blog

Is Design Dead?

Is Design Dead? I am going to write about the article “is Design Dead?” By Martin Fowler, it was a interesting article and was written in a unfamiliar way considering the title. He starts talking about the extreme programming and how it is one of the causes of the poor pre design that nowadays is (barely) used for big or small development. Software development needs like almost everything a design which defines not only how it will work, but how to make the specific modules and what job they are going to perform to accomplish a global goal. And well he basically explains the differences between planned design an evolutionary design, that is the reason why I think the title is funny, two kinds of design but he says it is dead, basically what happens is that, the extreme programming and the constant use of the technique pushes the developers to use the evolutionary design. Why? Easy, the extreme programming is a practice thas searchs the simplicity in the creation of...
Leer más

Software Architecture

Software Architecture This week I read the chapter 14 of the book "Code Craft: The Practice of Writing Excellent Code" titled " SOFTWARE ARCHITECTURE Laying the Foundations of Software Design" the first thing we should do is define what is software architecture, as we use the word architecture sounds logical that a building comes to our mind, but talking about software we can take the idea of a structure, so the author told us we can join the concepts to create in our brain the idea of high level design but of course the reason of the “similarity” in the concepts comes because the software architecture is used to create a propitious place to make code, at the end this can be used as a guide for the development. Some benefits of the software architecture are that this helps to validate requirements and conditions of a project so it can be used in a more free way for the different areas like design and development and can help to “talk the same language”,...
Leer más

Understanding the SOLID Principles

This week the blog will talk about the article "Understanding the SOLID Principles" written by Edward Guiness, this is a brief summary that presents the definition of the SOLID Principles. The general objective of the SOLID principles, and so the author in the article, is to implement best practices in the creation of objects and classes in specific cases depending on the situation that is presented. And with you, the 5 principles *drumroll*: • Single Responsibility Principle • Open/Closed Principle • Liskov Substitution Principle • Interface Segregation Principle • Dependency Inversion Principle The first of this is the Single Responsibility Principle, it says that a class, should have just exactly one responsibility, just one reason or an only class of reason to exist. This responsibility should be implemented to the class, so for this reason a class just has one reason to be modified. Why implement this? Easy, in a big project you will have lots of classes ...
Leer más