Software Craftsmanship

Having working software is not enough. We need to have well-crafted software.

This is one of the many interesting points Uncle Bob focused on his interview in the software engineering radio podcast. He is a software engineer who co-wrote the Manifesto Software and leads “Uncle Bob Consulting LLC” and “Clean Coders” companies where he hosts videos based on his experiences and books, also he writes and consults codes. He became an architect and designed for a while but after that, he left it because it wasn`t his thing, despite this, he thinks that  architects shouldn’t be separated from the coders because  if they will separate them, architects make important decisions but they don’t know how to react because they aren't coding experts.

(If all the team Will be architects, they should make wise decisions)

Then Bob starts to explain about software craftsmanship which is an approach to software development that emphasizes the coding skills of the software developers themselves. It is a response by software developers to the perceived ills of the mainstream software industry, including the prioritization of financial concerns over developer accountability. The problem begins when a software developer starts working after college they know very little about what is going to be done on the job so they have to learn in their Jobs by themselves so, Craftsmanship helps young coders to become a master about software, you learn from other people by helping them do, not by studying in lectures and books. Software that works is fine, but the software that works and can't be maintained or can't and understood is a frightening thing to have on a system, and unfortunately most of the systems out there are in an unfortunate state of disrepair, and this disrepair is hidden from the users.