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 Apple Marketing Philosophy Markkula wrote his principles in a one-page paper titled "The Apple Marketing Philosophy" that stressed three points. The first was empathy, an intimate connection with the feelings of the customer: "We will truly understand their needs better than any other company." The second was focus: "In order to do a good job of those things that we decide to do, we must eliminate all of the unimportant opportunities." The third and equally important principle, awkwardly named, was impute. It emphasized that people form an opinion about a company or product based on the signals that it conveys. "People DO just a book by its cover," he wrote. "We may have the best product, the highest quality, the most useful software etc.; if we present them in a slipshod manner, they will be perceived as slipshod; if we present them in a creative, professional manner, we will impute the desired qualities." Walter Isaacson, Steve Jobs A ritual of unpacking