Sensing Interruptibility in the Office

Züger, Manuela; Müller, Sebastian; Meyer, André N.; Fritz, Thomas

doi:10.1145/3173574.3174165

Cited by 43 publications

(10 citation statements)

References 71 publications

(61 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…All our participants were male and working in Spain, and although we do not suspect significant regional differences, they cannot be ruled out. Furthermore, a sample size of 13 participants is not very large, though not particularily low compared to other studies in software engineering (e.g., [26,44]). Given that we recruited both experienced and novice developers from several sources (universities and an international Python conference), we are confident to have mitigated this issue as far as possible.…”

Section: Threats To Validitymentioning

confidence: 94%

On the usage of pythonic idioms

Alexandru

Merchante

Panichella

et al. 2018

Proceedings of the 2018 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Sof

View full text Add to dashboard Cite

Developers discuss software architecture and concrete source code implementations on a regular basis, be it on questionanswering sites, online chats, mailing lists or face to face. In many cases, there is more than one way of solving a programming task. Which way is best may be decided based on case-specific circumstances and constraints, but also based on convention. Having strong conventions, and a common vocabulary to express them, simplifies communication and strengthens common understanding of software development problems and their solutions. While many programming ecosystems have a common vocabulary, Python's relationship to conventions and common language is a particularly pronounced. The "Zen of Python", a famous set of high-level coding conventions authored by Tim Peters, states "There should be one, and preferably only one, obvious way to do it". This 'one way to do it' is often referred to as the 'Pythonic' way: the ideal solution to a particular problem. Few other programming languages have coined a unique term to label the quality of craftsmanship gone into a software artifact. In this paper, we explore how Python developers understand the term 'Pythonic' by means of structured interviews, build a catalogue of 'pythonic idioms' gathered from literature, and conjecture on the effects of having a language-specific term for quality code, considering the potential it could hold for other programming languages and ecosystems. We find that while the term means different things to novice versus experienced Python developers, it encompasses not only concrete implementation, but a way of thinking -a culture -in general.

show abstract

Section: Threats To Validitymentioning

confidence: 94%

On the usage of pythonic idioms

Alexandru

Merchante

Panichella

et al. 2018

Proceedings of the 2018 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Sof

View full text Add to dashboard Cite

show abstract

“…Such measures could be considered in a potential early warning system as physiological indicators to measure autonomic nervous system activity to measure stress-related disturbances (i.e., interruptions) during task performance ( Stangl and Riedl, 2022a , 2022c ). Indeed, empirical research showed that a combination of biometric data together with computer interaction data can predict with high accuracy the interruptibility of software developers at a given moment to avoid inappropriate moments for interruptions ( Züger and Fritz, 2015 ; Züger et al, 2018 ). Another conceivable approach to extending the taxonomy is third-party evaluation.…”

Section: Review Results and Research Agendamentioning

confidence: 99%

Interruption science as a research field: Towards a taxonomy of interruptions as a foundation for the field

Stangl

Riedl

2023

Front. Psychol.

View full text Add to dashboard Cite

Interruptions have become ubiquitous in both our personal and professional lives. Accordingly, research on interruptions has also increased steadily over time, and research published in various scientific disciplines has produced different perspectives, fundamental ideas, and conceptualizations of interruptions. However, the current state of research hampers a comprehensive overview of the concept of interruption, predominantly due to the fragmented nature of the existing literature. Reflecting on its genesis in the 1920s and the longstanding research on interruptions, along with recent technological, behavioral, and organizational developments, this paper provides a comprehensive interdisciplinary overview of the various attributes of an interruption, which facilitates the establishment of interruption science as an interdisciplinary research field in the scientific landscape. To obtain an overview of the different interruption attributes, we conducted a systematic literature review with the goal of classifying interruptions. The outcome of our research process is a taxonomy of interruptions, constituting an important foundation for the field. Based on the taxonomy, we also present possible avenues for future research.

show abstract

“…This chain is composed by stages of preparation, diversion, resumption and recovery that result in time away from an ongoing task. Since interruptions can have a large impact on the focus and productivity of office workers, several studies have examined the prediction of interruptibility-the availability for interruptions-using a variety of features, including computer interaction and biometrics [46,47,48,49,16,50]. Most of these studies were again conducted for small and controlled tasks over shorter periods of time.…”

Section: Focusmentioning

confidence: 99%