The practices of programming

Bergström, Ilias; Blackwell, Alan F.

doi:10.1109/vlhcc.2016.7739684

Cited by 23 publications

(15 citation statements)

References 46 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…High variance: Performance in cognitive processes can be difficult to predict [58]; other domains in which this might be relevant include chess and music [46]. Range of working styles: Bergström and Blackwell described a diverse collection of different approaches to programming problems [7], such as bricolage/tinkering and engineering. These different styles may be used even by different people using the same language, impeding a designer's attempts to anticipate a user's strategy or behavior.…”

Section: Discussionmentioning

confidence: 99%

Pliers

Coblenz

Kambhatla

Koronkevich

et al. 2021

ACM Trans. Comput.-Hum. Interact.

View full text Add to dashboard Cite

Programming language design requires making many usability-related design decisions. However, existing HCI methods can be impractical to apply to programming languages: languages have high iteration costs, programmers require significant learning time, and user performance has high variance. To address these problems, we adapted both formative and summative HCI methods to make them more suitable for programming language design. We integrated these methods into a new process, PLIERS, for designing programming languages in a user-centered way. We assessed PLIERS by using it to design two new programming languages. Glacier extends Java to enable programmers to express immutability properties effectively and easily. Obsidian is a language for blockchains that includes verification of critical safety properties. Empirical studies showed that the PLIERS process resulted in languages that could be used effectively by many programmers and revealed additional opportunities for language improvement.

show abstract

Section: Discussionmentioning

confidence: 99%

Pliers

Coblenz

Kambhatla

Koronkevich

et al. 2021

ACM Trans. Comput.-Hum. Interact.

View full text Add to dashboard Cite

show abstract

“…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?…”

Section: Included Papers and Booksmentioning

confidence: 99%

Towards an Anatomy of Software Craftsmanship

SundelinAnders

González-Huerta

WnukKrzysztof

et al. 2021

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Context: The concept of software craftsmanship has early roots in computing, and in 2009, the Manifesto for Software Craftsmanship was formulated as a reaction to how the Agile methods were practiced and taught. But software craftsmanship has seldom been studied from a software engineering perspective. Objective: The objective of this article is to systematize an anatomy of software craftsmanship through literature studies and a longitudinal case study. Method: We performed a snowballing literature review based on an initial set of nine papers, resulting in 18 papers and 11 books. We also performed a case study following seven years of software development of a product for the financial market, eliciting qualitative, and quantitative results. We used thematic coding to synthesize the results into categories. Results: The resulting anatomy is centered around four themes, containing 17 principles and 47 hierarchical practices connected to the principles. We present the identified practices based on the experiences gathered from the case study, triangulating with the literature results. Conclusion: We provide our systematically derived anatomy of software craftsmanship with the goal of inspiring more research into the principles and practices of software craftsmanship and how these relate to other principles within software engineering in general.

show abstract

“…The human factors and organisational concerns of first-and second-wave HCI offered business benefits and addressed educational policies that focused on professional skill and productivity. These new informal, experimental and everyday practices of coding treat code as a kind of craft material, and discuss programming skill and experience in relation to other craft practices in which malleable materials are explored toward creative ends (Bergstrom & Blackwell 2016). The 29th annual meeting of PPIG in 2018 was convened together with the Art Worker's Guild of London, a respected establishment of the 19th century English Arts and Crafts movement.…”

Section: Accepted Manuscript 7 Future Agendamentioning

confidence: 99%