“Software Craftsmanship with Bob Martin”

I have listened to the podcast that is actually an interview to Robert C. Martin, which is a software engineer and author of a lot of books; you can also know him as the uncle Bob. We can hear some subjects like software architecture, software craftmanship and agile software development approach during this interview.

The first thing we hear is Uncle Bob talking about his experience of being a software architect. We also hear him saying that the worst part is the people that tends to separate architects from software developers. He believes is weird because architects make decisions about the code and have no familiarity with it.

Robert Martin, talks in this interview about software craftsmanship (I have never heard about this concept in my life) , and he tell us that is a concept that says that every young coder or developer  needs to have a master because we can not learn coding just with theory, you must help another person to learn, in a project or whatever you want but help someone. This is similar to attending to college, here you have classmates that maybe have some issues with a subject and as a good classmate you can help someone and with that receive more knowledge and feedback. 

Software craftsmanship has also a manifesto with four points, which are:

• Not only working software, but also well-crafted software

• Not only responding to change, but also steadily adding value

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

• Not only customer collaboration, but also productive partnerships

We hear uncle Bob explaining each point. The first two main points consist on code related to issues, is to have good practices to code and do well-crafted software, not just do what you need to do, but also know how to do it, this applies also when you make changes to the code. You must add value not just to accomplish the requirements.  

Uncle Bob also mentioned some tools and abilities that a good developments craftsman should have:

• Understanding the IDE you are working with

• Version control

• Bug tracking

• Unit testing

• Acceptance testing tool

• Lisp

• Knowing a programming language of each type