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
ArchDaily A Website www.archdaily.com We began as a platform to collect and spread the most important information for architects seeking to build a better world. Today, we are an ever-evolving tool for anybody who has a passion and determination to shape the world around them, including the 13.6 million readers that visit ArchDaily every month. 125 Best Architecture Books architecture
125 Best Architecture Books Essential Reads Guides Architects, Firms, and Movements Novels History Theory Cities & Urbanism A Pattern LanguageThe Eyes of the Skin: Architecture and the SensesThe Image of the CityIn Praise of ShadowsThe Poetics of SpaceSeven lampsCities for PeopleInvisible CitiesBLDGBLOGThe Death and Life of Great American CitiesLife Between BuildingsSoft City