Software Engineering as a Craft An Article by Thomas Wilson thomaswilson.xyz The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance. So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it. craftsoftware
Tossing an idea around Can we do anything to increase creativity? There are training courses, and books, as well as “brainstorming sessions” which are supposed to do this. Taking the brainstorming sessions first, while they were very fashionable at one time, they have generally been found to be not much good when formally done, when a brainstorming session is carefully scheduled. But we all have had the experience of “tossing an idea around” with a friend, or a few friends (but not a large group, generally), from which insight, creativity, or whatever you care to call it, arises and we make progress. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn SceniusThe Small Group