Software Craftsmanship

The Interview to Bob Martin was quite interesting. Oscillating from personal technical preferences to stories about the good ol' times. It seems that for Bob software development was never fully tamed and it is still necessary for a programmer to create his own craftsmanship and take pride on their job. Developers should be learn to create software by actually working on the industry, starting as an observer of what more experienced craftsmen do. I have to agree with Bob on this one, on my little experience on actually developing software you don't only learn the profession by writing code. I had to stick to an experienced employee who had the patience to guide me. I had to learn how to use tools which are stated to be one of the main characteristics of any kind of craftsmanship. Git, Jenkins, Spring, Jira, Maven, there were so many things I had to use to a decent level before I could make something out of a programming language. And on top of it you must consider the way you are organizing for work. A very interesting point of the interview was the never ending improvement of the tools for software developers in such way that the interviewer hoped that perhaps human intervention is no longer necessary in the creation of software. For Bob the human will still be needed to make decisions at the time software is crafted. In this point I believe it is hard to tell if the vision of automating the software industry in such way the automobile industry has would ever come, as software is something quite abstract. However I have seen certain tools and frameworks that are able to partially replace programming. Unfortunately I can't remember the name of the tool, but I had to watch a couple tutorials of a tool that was able to set up servers automatically and handle request with a drag and drop interface. I don't know how good this tools are nowadays, all I can think of how horribly Adobe's Dreamweaver generated HTML. But still, maybe the day will come for the old fashioned software craftsmanship.