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
Total collaboration The process of designing a product at Apple was integrally related to how it would be engineered and manufactured. Ive described one of Apple's Power Macs. "We wanted to get rid of anything other than what was absolutely essential," he said. "To do so required total collaboration between the designers, the product developers, the engineers, and the manufacturing team. We kept going back to the beginning, again and again. Do we need that part? Can we get it to perform the function of the other four parts?" Walter Isaacson, Steve Jobs Like designing things for the first time