3 Responses

  1. Anyone Can Be A Codesmith. | DEVOPS | Scoop.it

    […] he barrier to being a codesmith should be low.This is why I think that anyone who writes code in any shape or form should feel free about calling themselves a codesmith. The ideals of craftmanship should be followed, with a healthy dose of pragmatism, but learning the skills to become a good coder takes time and experience. I also do not believe that you can always tell if someone will make a good codesmith or not. Some codesmiths who have few skills at the moment might just need a small push in the right direction to make their code better.But the barrier to being a codesmith master should be high.Because this is what will help keep the term codesmith synonymous with the ideals of craftmanship and quality that being a codesmith should imply.  […]

  2. Software Craftsmanship | Igfasouza
    Software Craftsmanship | Igfasouza February 15, 2015 at 2:00 am |

    […] “Anyone Can Be A Codesmith” Further […]

  3. Graham Trott
    Graham Trott February 4, 2019 at 12:22 pm | | Reply

    I pretty much agree with what you say. The trouble with software is it’s been professionalised to an undesirable extent, where only Jedi Masters have a chance of really understanding what’s going on. We have the domain of the customer and the domain of the programmer; they do not in general overlap except in rare cases such as SQL.

    This gap gives rise to massive misunderstandings and consequent project failures. The problem is one of language; a subject for which I am gradually formulating an appropriate treatise. But basically, I believe that 3rd-generation so-called “computer languages” should never be seen by customers; like assembly-language they belong way down and invisible to all but specialists.

    Customer requirements should be expressed in something as close to natural language as it is possible to get. I’m not talking about AI; that’s for the birds. I mean simple ways of expressing domain-level concepts, where the only essential features are that they must be both unambiguous and understandable by domain experts as well as engineers. Once this is achieved then a computer can do something with it. I’ve been doing this for over 20 years so I know it’s not pie-in-the-sky wishful thinking; it actually works.

    The proof is complete when your client, with whatever help he may be able to find, can open up the project a decade later and still make sense of it. It’s a big ask but we’re supposed to be professionals and I for one am not afraid to ask.

Think you could have written this better? Then leave a reply and tell me what you think.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close