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.
My heart belongs to the details.
I actually always found them to be more important than the big picture.
Nothing works without details.
They are everything, the baseline of quality.
Truly functional design only comes from the most careful and intense attention to detail.
Although he did not directly design all products and even had very little to do with some of them, he constantly encouraged tiny improvements that could make a good design better. This attention to detail ranged from the acuteness of angles in forms; the size, feels and distances between switches; the integration of handle fixings; the placement and nature of graphic elements on the products themselves and extended to product photography and packaging.
Designing detail is about achieving a fine balance in all aspects and areas of the product, including those external to the object.