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
The iMac Ive and his team worked with Apple's Korean manufacturers to perfect the process of making the cases, and they even went to a jelly bean factory to study how to make translucent colors look enticing. The cost of each case was more than $60 per unit, three times that of a regular computer case. Other companies would probably have demanded presentations and studies to show whether the translucent case would increase sales enough to justify the extra cost. Jobs asked for no such analysis. Topping off the design was the handle nestled into the iMac. It was more playful and semiotic than it was functional. This was a desktop computer; not many people were really going to carry it it around. But as Ive later explained: Back then, people weren't comfortable with technology. If you're scared of something, then you won't touch it. I could see my mum being scared to touch it. So I thought, if there's this handle on it, it makes a relationship possible. It's approachable. It's intuitive. It gives you permission to touch. It gives a sense of deference to you. Walter Isaacson, Steve Jobs Customers don't know what they want