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
A state of energetic repose Read the text before designing it. Discover the outer logic of the typography in the inner logic of the text. Make the visible relationship between the text and other elements (photographs, captions, tables, diagrams, notes) a reflection of their real relationship. Give full typographic attention even to incidental details. Invite the reader into the text. Reveal the tenor and meaning of the text. Clarify the structure and the order of the text. Link the text with other existing elements. Induce a state of energetic repose, which is the ideal condition for reading. Robert Bringhurst, The Elements of Typographic Style The inner nature of material typography