Vernacularism in Software Design Practice: does craftsmanship have a place in software engineering?

Abstract

Convention dictates that an information discipline matures from an informal shared practice to a defined and repeatable process through the externalisation and formal expression of its underlying theory. The inevitability of this progression should not be allowed to over-shadow the essential values, skills and knowledge transfer mechanisms of the superseded vernacular or craft-like practices. This paper examines the tension between software engineering's professionalisation of the software design role-exemplified by the software architect-and its antithesis, the software craftsperson, a characterisation that continues to emerge despite attempts to suppress reliance on individual skills and abilities through software engineering process. In other design disciplines, the professionalisation of design marks a distinct progression from ad hoc, unrepeatable, unselfconscious craft to a selfconscious, demarcated type of design found in most forms of engineering. Software engineering has partially failed to make this transition and this failure undermines the exclusivity of the engineering metaphor and engineering-based process models as a model of practical software design. Software methods must acknowledge and find ways of incorporating vernacularism and informality if the creative act of design is to be correctly characterised, supported in methods, and taught.

Towards an Anatomy of Software Craftsmanship

“…Seed-1 P1 [81], P2 [62], P3 [71], P4 [50] Seed-2 P5 [51], P6 [40], P7 [20], P8 [68], P9 [53] Iteration 1 213 references and 186 citations P10 [64] Iteration 2 30 references and 1 citation P11 [49], P12 [82], P13 [63], P14 [9] Iteration 3 217 references and 517 citations P15 [76], P16 [7], P17 [48] Iteration 4 18 references and 78 citations P18 [89] Ref. Books 146 referenced books B1 [13], B2 [57], B3 [47], B4 [54] B5 [78], B6 [37], B7 [77], B8 [55] B9 [52], B10 [35], B11 [88] (2) Does the paper describe themes, practices, or otherwise conceptualize software craftsmanship?…”

Point-and-shoot security design

“…Using photography as an analogy to discuss security engineering embeds this paper in the age-old debate whether we should conceive software development as engineering [17,70,9,48,4], art [34,28], science [10], craft [66], or something else, and whether we would be better off emphasizing one view or the other [18,49,14,41]. The author does not take sides, but rather looks for lessons to be learnt from one field for another.…”