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
Don’t Be an Ostrich An Essay by Chuánqí Sun medium.com You just handed off a major redesign. Three months of research, twenty-seven major revisions, and hundreds cups of coffee have all culminated in this pinnacle of glory. It’s finally done! Except it’s not. It’s not, even after you have answered every single question the developers have about your red-line. It’s not, even after you have addressed all the technical constraints developers encountered during the implementation. It’s not, even after you meticulously documented all the patterns and styles into a library for reference and reuse. It’s not, because neither you nor the developers have talked to a real user. At the bottom of your heart, you are secretly wishing: My design looks great on paper, so let’s keep it on paper. You are an ostrich. Post-occupancy evaluation
Post-occupancy evaluation Post-occupancy evaluation (POE) is a practice in the building industry where an architect would visit the building after its occupancy and interview its residents. It sounds like a great opportunity for collecting feedback and learning from mistakes, but it’s rarely practiced. Why? Many awe-inspiring, prize-winning architectures are half building, half sculpture. Often made of specially molded concrete and steel, they are extremely expensive to alter, let alone any alteration would also attack the architect’s prestige and pride. So whatever usability issues the POE identifies will remain as issues, unless the architect wants to accept the public criticism and shame that comes with the remodeling. In fear of criticism, an architect would turn down the opportunity for POE, and continue to design the same roof that would leak water in future projects. In fear of criticism, a developer would use customer service representatives as a shield against user complaints, while focusing on the “technical” aspect of things. In fear of criticism, a designer would close the contract as soon as the client accepts the design, even though none of the real users are represented by the client. architectureux