Emotional labor of software engineers
•
2 likes•423 views
The concept of emotional labor, introduced by Hochschild in 1983, refers to the “process by which workers are expected to manage their feelings in accordance with organizationally defined rules and guidelines”. For instance, judges are expected to appear impartial, nurses—compassionate and police officers—authoritative. While software development has been traditionally stereotyped as a nerdy “lone wolf” job less likely to induce emotional labor, nowadays software developers become more and more social, on the one hand, and are subject to increasing amount of behavioral expectations, e.g., formulated as codes of conduct. In this position paper we stress that software developers are subject to emotional labor, envision how emotional labor can be identified based on emotion detection techniques applied in software engineering, suggest possible antecedents and consequents of emotional labor and discuss interventions that can be designed to address the challenges of emotional labor.
Report
Share
Report
Share
Download to read offline
Recommended
Towards Supporting Emotion Awareness of Software Developers
My talk @Shonan Meeting on Human Aspects in Software Engineering (March, 2023)
Abstract - Software development is an intellectual activity requiring creativity and problem-solving skills, which are known to be influenced by emotions. Developers experience a wide range of affective states during programming tasks, which may have an impact on their job performance and well-being. Early recognition of negative emotions, such as stress or frustration can enable just-in-time intervention for developers and team managers, in order to prevent burnout and undesired turnover. In this talk, I will present an overview of recent research findings of our empirical studies aimed at investigating the link between emotion and productivity, understanding the triggers for developers’ emotions, and the strategies they implement to deal with negative ones and restore positive feelings. Furthermore, I will present the results of a field study involving software developers from five different companies investigating the feasibility of emotion recognition using a minimal set of non-invasive biometric sensors i.e. a wristband capturing the electrodermal activity and heart-related metrics. To conclude, I will be discussing open challenges and presenting early results of ongoing empirical studies.
Interaction between abstract agents: Increasing the readability of causal e...
Muhammet Ramoğlu; İdil Bostan, Koç University
Mohammad Obaid, Uppsala University
Tilbe Göksun; Oğuzhan Özcan, Koç University
A Journey Into the Emotions of Software Developers
Emotions are part of our everyday life and are known to impact cognitive skills, thus influencing job performance. This is true also for software development, an intellectual activity requiring creativity and problem-solving skills that are known to be influenced by affective states. In particular, early recognition of negative emotions, such as stress or frustration can enable just-in-time intervention for developers and team managers, in order to prevent burnout and undesired turnover. In this talk, I will provide an overview of recent research findings on developers’ emotions and their relationship with self-assessed productivity. Next, I will argue in favor of the emergence of tools to support developers’ emotion awareness at the individual and team level to improve productivity, resilience to failures and wellbeing.
SenseTheClassroom Live at EC-TEL 2022
Privacy-Preserving and Scalable Affect Detection in Online Synchronous Learning
written by Felix Böttger, Ufuk Cetinkaya, Daniele Di Mitri, Sebastian Gombert, Krist Shingjergji, Deniz Iren & Roland Klemke was accepted at the Seventeenth European Conference on Technology Enhanced Learning (EC-TEL 2022) Educating for a new future: Making sense of technology-enhanced learning adoption – Toulouse, France, 12-16 September 2022
The paper reports on a research prototype which stems from the cooperation between DIPF and the Open University of the Netherlands.
Abstract
The recent pandemic has forced most educational institutions to shift to distance learning. Teachers can perceive various non-verbal cues in face-to-face classrooms and thus notice when students are distracted, confused, or tired. However, the students’ non-verbal cues are not observable in online classrooms. The lack of these cues poses a challenge for the teachers and hinders them in giving adequate, timely feedback in online educational settings. This can lead to learners not receiving proper guidance and may cause them to be demotivated. This paper proposes a pragmatic approach to detecting student affect in online synchronized learning classrooms. Our approach consists of a method and a privacy-preserving prototype that only collects data that is absolutely necessary to compute action units and is highly scalable by design to run on multiple devices without specialized hardware. We evaluated our prototype using a benchmark for the system performance. Our results confirm the feasibility and the applicability of the proposed approach.
Keynote@QUATIC - Recognizing Developer's Emotions: Advances and Open Challenges
Software development is an intellectual activity requiring creativity and problem-solving skills, which are known to be influenced by emotions. Developers experience a wide range of affective states during programming tasks, which may have an impact on their job performance and wellbeing. Early recognition of negative emotions, such as stress or frustration can enable just-in-time intervention for developers and team managers, in order to prevent burnout and undesired turnover. In this talk, I will provide an overview of recent research findings of sentiment analysis in software engineering (SE), address the open challenges, and provide empirically-based guidelines for safe (re)use of SE-specific tools in order to obtain meaningful results.
Recommended
Towards Supporting Emotion Awareness of Software Developers
My talk @Shonan Meeting on Human Aspects in Software Engineering (March, 2023)
Abstract - Software development is an intellectual activity requiring creativity and problem-solving skills, which are known to be influenced by emotions. Developers experience a wide range of affective states during programming tasks, which may have an impact on their job performance and well-being. Early recognition of negative emotions, such as stress or frustration can enable just-in-time intervention for developers and team managers, in order to prevent burnout and undesired turnover. In this talk, I will present an overview of recent research findings of our empirical studies aimed at investigating the link between emotion and productivity, understanding the triggers for developers’ emotions, and the strategies they implement to deal with negative ones and restore positive feelings. Furthermore, I will present the results of a field study involving software developers from five different companies investigating the feasibility of emotion recognition using a minimal set of non-invasive biometric sensors i.e. a wristband capturing the electrodermal activity and heart-related metrics. To conclude, I will be discussing open challenges and presenting early results of ongoing empirical studies.
Interaction between abstract agents: Increasing the readability of causal e...
Muhammet Ramoğlu; İdil Bostan, Koç University
Mohammad Obaid, Uppsala University
Tilbe Göksun; Oğuzhan Özcan, Koç University
A Journey Into the Emotions of Software Developers
Emotions are part of our everyday life and are known to impact cognitive skills, thus influencing job performance. This is true also for software development, an intellectual activity requiring creativity and problem-solving skills that are known to be influenced by affective states. In particular, early recognition of negative emotions, such as stress or frustration can enable just-in-time intervention for developers and team managers, in order to prevent burnout and undesired turnover. In this talk, I will provide an overview of recent research findings on developers’ emotions and their relationship with self-assessed productivity. Next, I will argue in favor of the emergence of tools to support developers’ emotion awareness at the individual and team level to improve productivity, resilience to failures and wellbeing.
SenseTheClassroom Live at EC-TEL 2022
Privacy-Preserving and Scalable Affect Detection in Online Synchronous Learning
written by Felix Böttger, Ufuk Cetinkaya, Daniele Di Mitri, Sebastian Gombert, Krist Shingjergji, Deniz Iren & Roland Klemke was accepted at the Seventeenth European Conference on Technology Enhanced Learning (EC-TEL 2022) Educating for a new future: Making sense of technology-enhanced learning adoption – Toulouse, France, 12-16 September 2022
The paper reports on a research prototype which stems from the cooperation between DIPF and the Open University of the Netherlands.
Abstract
The recent pandemic has forced most educational institutions to shift to distance learning. Teachers can perceive various non-verbal cues in face-to-face classrooms and thus notice when students are distracted, confused, or tired. However, the students’ non-verbal cues are not observable in online classrooms. The lack of these cues poses a challenge for the teachers and hinders them in giving adequate, timely feedback in online educational settings. This can lead to learners not receiving proper guidance and may cause them to be demotivated. This paper proposes a pragmatic approach to detecting student affect in online synchronized learning classrooms. Our approach consists of a method and a privacy-preserving prototype that only collects data that is absolutely necessary to compute action units and is highly scalable by design to run on multiple devices without specialized hardware. We evaluated our prototype using a benchmark for the system performance. Our results confirm the feasibility and the applicability of the proposed approach.
Keynote@QUATIC - Recognizing Developer's Emotions: Advances and Open Challenges
Software development is an intellectual activity requiring creativity and problem-solving skills, which are known to be influenced by emotions. Developers experience a wide range of affective states during programming tasks, which may have an impact on their job performance and wellbeing. Early recognition of negative emotions, such as stress or frustration can enable just-in-time intervention for developers and team managers, in order to prevent burnout and undesired turnover. In this talk, I will provide an overview of recent research findings of sentiment analysis in software engineering (SE), address the open challenges, and provide empirically-based guidelines for safe (re)use of SE-specific tools in order to obtain meaningful results.
Software development is a human activity: understanding software requires und...
Software development is a human activity: understanding software requires und...Alexander Serebrenik
Talk given at the Software Center of Chalmers, Sweden.
https://www.software-center.se/event/rws-dec2023/
Towards Continuous Performance Assessment of Java Applications With PerfBot
Bots for continuous performance assessment are gaining use as a productivity tool. We discuss how and why open source projects use them and present an in-depth case study of the Nanosoldier bot used by the team behind the Julia programming language. Based on analysing the history of bot usage and interviews with developers we identify lack of a shared platform for performance measurement as an obstacle to wider adoption of performance measurement bots. To address this, we propose a prototype implementation of such a platform called PerfBot.
Joint work with Florian Markusse and Philipp Leitner, presented at 5th International Workshop on
Bots in Software Engineering, collocated with ICSE 2023, Melbourne Australia.
“STILL AROUND”: Experiences and Survival Strategies of Veteran Women Software...
“STILL AROUND”: Experiences and Survival Strategies of Veteran Women Software...Alexander Serebrenik
The intersection of ageism and sexism can create a hostile environment for veteran software developers belonging to marginalized genders. In this study, we conducted 14 interviews to examine the experiences of people at this intersection, primarily women, in order to discover the strategies they employed in order to successfully remain in the field. We identified 283 codes, which fell into three main categories: Strategies, Experiences, and Perception. Several strategies we identified, such as (Deliberately) Not Trying to Look Younger, were not previously described in the software engineering literature. We found that, in some companies, older women developers are recognized as having particular value, further strengthening the known benefits of diversity in the workforce. Based on the experiences and strategies, we suggest organizations employing software developers to consider the benefits of hiring veteran women software developers. For example, companies can draw upon the life experiences of older women developers in order to better understand the needs of customers from a similar demographic. While we recognize that many of the strategies employed by our study participants are a response to systemic issues, we still consider that, in the short-term, there is benefit in describing these strategies for developers who are experiencing such issues today.
This paper is a joint work with Sterre van Breukelen, Ann Barcomb and Sebastian Baltes
Preprint https://arxiv.org/abs/2302.03723A Qualitative Study of Developers’ Discussions of Their Problems and Joys Dur...
A Qualitative Study of Developers’ Discussions of Their Problems and Joys Dur...Alexander Serebrenik
Many software developers started to work from home on a short notice during the early periods of COVID-19. A number of previous papers have studied the wellbeing and productivity of software developers during COVID-19. The studies mainly use surveys based on predefined questionnaires. In this paper, we investigate the problems and joys that software developers experienced during the early months of COVID-19 by analyzing their discussions in online forum devRant, where discussions can be open and not bound by predefined survey questionnaires. The devRant platform is designed for developers to share their joys and frustrations of life. We manually analyze 825 devRant posts between January and April 12, 2020 that developers created to discuss their situation during COVID19. WHO declared COVID-19 as pandemic on March 11, 2020. As such, our data offers us insights in the early months of COVID-19. We manually label each post along two dimensions: the topics of the discussion and the expressed sentiment polarity (positive, negative, neutral). We observed 19 topics that we group into six categories: Workplace & Professional aspects, Personal & Family well-being, Technical Aspects, Lockdown preparedness, Financial concerns, and Societal and Educational concerns. Around 49% of the discussions are negative and 26% are positive. We find evidence of developers’ struggles with lack of documentation to work remotely and with their loneliness while working from home. We find stories of their job loss with little or no savings to fallback to. The analysis of developer discussions in the early months of a pandemic will help various stakeholders (e.g., software companies) make important decision early to alleviate developer problems if such a pandemic or similar emergency situation occurs in near future. Software engineering research can make further efforts to develop automated tools for remote work (e.g., automated documentation).
Empirical Software Engineering 27(5): 117 (2022), presented at ICSE 2023 as part of the Journal First program.Emotion Analysis in Software Ecosystems
Software developers are known to experience a wide range of emotions while performing development tasks. Emotions expressed in developer communication might reflect openness of the ecosystem to newcomers, presence of conflicts, problems in the software development process or source code itself. In this talk, based on a recent work with Nicole Novielli, I present an overview of the state-of-the-art research on analysis of emotions in software engineering focusing on the studies of emotion in context of software ecosystems. To encourage further applications of emotion analysis in the industry and research we also discuss currently available emotion analysis tools and datasets as well as outline directions for future research.
This is a keynote talk given at the 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems (SESoS 2023), collocated with ICSE 2023 in Melbourne, Australia.
Investigating the Resolution of Vulnerable Dependencies with Dependabot Secur...
Investigating the Resolution of Vulnerable Dependencies with Dependabot Secur...Alexander Serebrenik
Modern software development practices increasingly rely on third-party libraries due to the inherent benefits of reuse. However, libraries may contain security vulnerabilities that can propagate to the dependent applications. To counter this, maintainers of dependent projects should monitor their dependencies and security reports to ensure that only patched releases of the upstream applications are in use. As manual maintenance of dependencies has shown to be ineffective, several automated tools (aka bots) have been proposed to assist developers in rapidly identifying and resolving vulnerable dependencies.
In this work, we focus on Dependabot, a popular bot providing security and version updates, and study developers' receptivity to its security updates in engineered and actively maintained JavaScript projects. Moreover, we carry out a fine-grained analysis of the lifecycle of every vulnerability to manifest how they are dealt with in the presence of Dependabot.
Our findings show that the task of fixing vulnerable dependencies is, to a large extent, delegated to Dependabot and that developers merge the majority of security updates within several days. On the other hand, when developers do not merge a security update, they usually address the identified vulnerability manually. This approach, however, often takes up to several months which in turn could expose the projects to security issues.
This paper has won the ACM Distinguished paper award at MSR 2023.Gender and Age in Software Engineering
Overview of our studies of gender and age in software engineering.
Diversity and inclusion in a CS classroom
Diversity and Inclusion in a CS classroom; based on the talk at the University of Twente.
An Empirical Assessment on Merging and Repositioning of Static Analysis Alarms
Static analysis tools generate a large number of
alarms that require manual inspection. In prior work, repositioning of alarms is proposed to (1) merge multiple similar alarms
together and replace them by a fewer alarms, and (2) report
alarms as close as possible to the causes for their generation. The
premise is that the proposed merging and repositioning of alarms
will reduce the manual inspection effort. To evaluate the premise,
this paper presents an empirical study with 249 developers on
the proposed merging and repositioning of static alarms. The
study is conducted using static analysis alarms generated on C
programs, where the alarms are representative of the merging vs.
non-merging and repositioning vs. non-repositioning situations
in real-life code. Developers were asked to manually inspect and
determine whether assertions added corresponding to alarms in
C code hold. Additionally, two spatial cognitive tests are also
done to determine relationship in performance. The empirical
evaluation results indicate that, in contrast to expectations, there
was no evidence that merging and repositioning of alarms reduces
manual inspection effort or improves the inspection accuracy (at
times a negative impact was found). Results on cognitive abilities
correlated with comprehension and alarm inspection accuracy.
Classification and Ranking of Delta Static Analysis Alarms
Static analysis tools help to detect common programming errors but generate a large number of false positives.
Moreover, when applied to evolving software systems, around
95% of alarms generated on a version are repeated, i.e., they
have also been generated on the previous version. Version-aware
static analysis techniques (VSATs) have been proposed to suppress
the repeated alarms that are not impacted by the code changes
between the two versions. The alarms reported by VSATs after
the suppression, called delta alarms, still constitute 63% of the
tool-generated alarms.
We observe that delta alarms can be further postprocessed
using their corresponding code changes: the code changes due
to which VSATs identify them as delta alarms. However, none
of the existing VSATs or alarms postprocessing techniques
postprocesses delta alarms using the corresponding code changes.
Based on this observation, we use the code changes to classify
delta alarms into six classes that have different priorities assigned
to them. The assignment of priorities is based on the type of
code changes and their likelihood of actually impacting the delta
alarms. The ranking of alarms, obtained by prioritizing the
classes, can help suppress alarms that are ranked lower, when
resources to inspect all the tool-generated alarms are limited.
We performed an empirical evaluation using 9789 alarms
generated on 59 versions of seven open source C applications.
The evaluation results indicate that the proposed classification
and ranking of delta alarms help to identify, on average, 53% of
delta alarms as more likely to be false positives than the others.
What Is an AI Engineer? An Empirical Analysis of Job Ads in The Netherlands
Recently, the job market for Artificial Intelligence (AI) engineers
has exploded. Since the role of AI engineer is relatively new, limited
research has been done on the requirements as set by the industry.
Moreover, the definition of an AI engineer is less established than
for a data scientist or a software engineer. In this study we explore,
based on job ads, the requirements from the job market for the
position of AI engineer in The Netherlands. We retrieved job ad
data between April 2018 and April 2021 from a large job ad database,
Jobfeed from TextKernel. The job ads were selected with a process
similar to the selection of primary studies in a literature review. We
characterize the 367 resulting job ads based on meta-data such as
publication date, industry/sector, educational background and job
titles. To answer our research questions we have further coded 125
job ads manually.
The job tasks of AI engineers are concentrated in five categories:
business understanding, data engineering, modeling, software development and operations engineering. Companies ask for AI engineers with different profiles: 1) data science engineer with focus
on modeling, 2) AI software engineer with focus on software development, 3) generalist AI engineer with focus on both models
and software. Furthermore, we present the tools and technologies
mentioned in the selected job ads, and the soft skills.
Our research helps to understand the expectations companies
have for professionals building AI-enabled systems. Understanding
these expectations is crucial both for prospective AI engineers and
educational institutions in charge of training those prospective
engineers. Our research also helps to better define the profession of
AI engineering. We do this by proposing an extended AI engineering life-cycle that includes a business understanding phase.
Joint work with Marcel Meesters and Petra Heck.
Gender and Community Smells
Community smells are patterns indicating suboptimal organization and communication of software development teams that have been shown to be related to suboptimal organisation of the source code. Given a long standing association of women and communication mediation, we have conducted a series of studies relating gender diversity to community smells, as well as comparing the results of the data analysis with developers' perception. To get further insights in the relation bwteen gender and community smells, we replicate our study focusing on the Brazilian software teams; indeed, culture-specific expectations on the behavior of people of different genders might have affected the perception of the importance of gender diversity and refactoring strategies when mitigating community smells. Finally, we extend the prediction model by including variables related to national diversity and see how the interplay between national diversity and gender diversity influences presence of community smells.
This talk is based on a series of papers published in 2019-2022 and co-authored with Gemma Catolino, Filomena Ferrucci, Stefano Lambiase, Tiago Massoni, Fabio Palomba, Camila Sarmento, and Damian Andrew Tamburri.
Bias in MSR Research
In this invited vision talk I am discussing biases in current MSR research related to projects we select, people we talk to and problems we solve.
From team organisation to software quality
Overview of a series of papers published in 2019-2021 on community smells, and their relation to code smells and gender, as well as resolution strategies.
Women in Dutch Computer Science: Best Practices for Recruitment, Onboarding a...
Women in Dutch Computer Science: Best Practices for Recruitment, Onboarding a...Alexander Serebrenik
Women are underrepresented at all levels in computer science (CS) faculties of Dutch
universities. In this report we focus on experiences related to hiring and promoting women as assistant, associate and full professors (or equivalent at NWO-I CWI).My research story (presentation at ICSE 2021 New Faculty Symposium)
Looking back at my academic career so far
Opinion Mining for Software Engineering
In 2003 Dave et al. have coined the term “opinion mining” to refer to “processing a set of search results for a given item, generating a list of product attributes (quality, features, etc.) and aggregating opinions about each of them (poor, mixed, good)”. Nine years later, in 2012 Brooks and Swigger have applied sentiment analysis in the context of software engineering. Today another nine years have passed and it is time to look back: what have we achieved as a research community and where should we go next?
To answer this question we conducted a systematic literature review involving 185 papers. Based on the literature review we present 1) well-defined categories of opinion mining-related software development activities, 2) available opinion mining approaches, whether they are evaluated when adopted in other studies, and how their performance is compared, 3) available datasets for performance evaluation and tool customization, and 4) concerns or limitations SE researchers might need to take into account when applying/customizing these opinion mining techniques. The results of our study serve as references to choose suitable opinion mining tools for SE tasks, and provide critical insights for the further development of opinion mining techniques in the SE domain.
This work has been done together with Bin Lin, Gabriele Bavota and Michele Lanza from Università della Svizzera italiana, Switzerland, Nathan Cassee from Eindhoven University of Technology, The Netherlands and Nicole Novielli from University of Bari, Italy.
Removing Self Admitted Technical Debt
In this talk I will present results obtained on removing self-admitted technical debt. Self-admitted technical debt is an indication in the source code, usually n the source code comments, that the code is not in the right shape yet. Joint work with Emad Shihab, Everton Maldonado, Rabe Abdelkareem, Fiorella Zampetti, Massimiliano Di Penta and Gianmarco Fucci.
Gender Diversity and Inclusion and Software Engineering
In this talk we discuss several issues related to gender diversity and inclusion in software engineering. Based on research 2015-2019.
Earliest Galaxies in the JADES Origins Field: Luminosity Function and Cosmic ...
We characterize the earliest galaxy population in the JADES Origins Field (JOF), the deepest
imaging field observed with JWST. We make use of the ancillary Hubble optical images (5 filters
spanning 0.4−0.9µm) and novel JWST images with 14 filters spanning 0.8−5µm, including 7 mediumband filters, and reaching total exposure times of up to 46 hours per filter. We combine all our data
at > 2.3µm to construct an ultradeep image, reaching as deep as ≈ 31.4 AB mag in the stack and
30.3-31.0 AB mag (5σ, r = 0.1” circular aperture) in individual filters. We measure photometric
redshifts and use robust selection criteria to identify a sample of eight galaxy candidates at redshifts
z = 11.5 − 15. These objects show compact half-light radii of R1/2 ∼ 50 − 200pc, stellar masses of
M⋆ ∼ 107−108M⊙, and star-formation rates of SFR ∼ 0.1−1 M⊙ yr−1
. Our search finds no candidates
at 15 < z < 20, placing upper limits at these redshifts. We develop a forward modeling approach to
infer the properties of the evolving luminosity function without binning in redshift or luminosity that
marginalizes over the photometric redshift uncertainty of our candidate galaxies and incorporates the
impact of non-detections. We find a z = 12 luminosity function in good agreement with prior results,
and that the luminosity function normalization and UV luminosity density decline by a factor of ∼ 2.5
from z = 12 to z = 14. We discuss the possible implications of our results in the context of theoretical
models for evolution of the dark matter halo mass function.
More Related Content
More from Alexander Serebrenik
Software development is a human activity: understanding software requires und...
Software development is a human activity: understanding software requires und...Alexander Serebrenik
Talk given at the Software Center of Chalmers, Sweden.
https://www.software-center.se/event/rws-dec2023/
Towards Continuous Performance Assessment of Java Applications With PerfBot
Bots for continuous performance assessment are gaining use as a productivity tool. We discuss how and why open source projects use them and present an in-depth case study of the Nanosoldier bot used by the team behind the Julia programming language. Based on analysing the history of bot usage and interviews with developers we identify lack of a shared platform for performance measurement as an obstacle to wider adoption of performance measurement bots. To address this, we propose a prototype implementation of such a platform called PerfBot.
Joint work with Florian Markusse and Philipp Leitner, presented at 5th International Workshop on
Bots in Software Engineering, collocated with ICSE 2023, Melbourne Australia.
“STILL AROUND”: Experiences and Survival Strategies of Veteran Women Software...
“STILL AROUND”: Experiences and Survival Strategies of Veteran Women Software...Alexander Serebrenik
The intersection of ageism and sexism can create a hostile environment for veteran software developers belonging to marginalized genders. In this study, we conducted 14 interviews to examine the experiences of people at this intersection, primarily women, in order to discover the strategies they employed in order to successfully remain in the field. We identified 283 codes, which fell into three main categories: Strategies, Experiences, and Perception. Several strategies we identified, such as (Deliberately) Not Trying to Look Younger, were not previously described in the software engineering literature. We found that, in some companies, older women developers are recognized as having particular value, further strengthening the known benefits of diversity in the workforce. Based on the experiences and strategies, we suggest organizations employing software developers to consider the benefits of hiring veteran women software developers. For example, companies can draw upon the life experiences of older women developers in order to better understand the needs of customers from a similar demographic. While we recognize that many of the strategies employed by our study participants are a response to systemic issues, we still consider that, in the short-term, there is benefit in describing these strategies for developers who are experiencing such issues today.
This paper is a joint work with Sterre van Breukelen, Ann Barcomb and Sebastian Baltes
Preprint https://arxiv.org/abs/2302.03723A Qualitative Study of Developers’ Discussions of Their Problems and Joys Dur...
A Qualitative Study of Developers’ Discussions of Their Problems and Joys Dur...Alexander Serebrenik
Many software developers started to work from home on a short notice during the early periods of COVID-19. A number of previous papers have studied the wellbeing and productivity of software developers during COVID-19. The studies mainly use surveys based on predefined questionnaires. In this paper, we investigate the problems and joys that software developers experienced during the early months of COVID-19 by analyzing their discussions in online forum devRant, where discussions can be open and not bound by predefined survey questionnaires. The devRant platform is designed for developers to share their joys and frustrations of life. We manually analyze 825 devRant posts between January and April 12, 2020 that developers created to discuss their situation during COVID19. WHO declared COVID-19 as pandemic on March 11, 2020. As such, our data offers us insights in the early months of COVID-19. We manually label each post along two dimensions: the topics of the discussion and the expressed sentiment polarity (positive, negative, neutral). We observed 19 topics that we group into six categories: Workplace & Professional aspects, Personal & Family well-being, Technical Aspects, Lockdown preparedness, Financial concerns, and Societal and Educational concerns. Around 49% of the discussions are negative and 26% are positive. We find evidence of developers’ struggles with lack of documentation to work remotely and with their loneliness while working from home. We find stories of their job loss with little or no savings to fallback to. The analysis of developer discussions in the early months of a pandemic will help various stakeholders (e.g., software companies) make important decision early to alleviate developer problems if such a pandemic or similar emergency situation occurs in near future. Software engineering research can make further efforts to develop automated tools for remote work (e.g., automated documentation).
Empirical Software Engineering 27(5): 117 (2022), presented at ICSE 2023 as part of the Journal First program.Emotion Analysis in Software Ecosystems
Software developers are known to experience a wide range of emotions while performing development tasks. Emotions expressed in developer communication might reflect openness of the ecosystem to newcomers, presence of conflicts, problems in the software development process or source code itself. In this talk, based on a recent work with Nicole Novielli, I present an overview of the state-of-the-art research on analysis of emotions in software engineering focusing on the studies of emotion in context of software ecosystems. To encourage further applications of emotion analysis in the industry and research we also discuss currently available emotion analysis tools and datasets as well as outline directions for future research.
This is a keynote talk given at the 11th International Workshop on Software Engineering for Systems-of-Systems and Software Ecosystems (SESoS 2023), collocated with ICSE 2023 in Melbourne, Australia.
Investigating the Resolution of Vulnerable Dependencies with Dependabot Secur...
Investigating the Resolution of Vulnerable Dependencies with Dependabot Secur...Alexander Serebrenik
Modern software development practices increasingly rely on third-party libraries due to the inherent benefits of reuse. However, libraries may contain security vulnerabilities that can propagate to the dependent applications. To counter this, maintainers of dependent projects should monitor their dependencies and security reports to ensure that only patched releases of the upstream applications are in use. As manual maintenance of dependencies has shown to be ineffective, several automated tools (aka bots) have been proposed to assist developers in rapidly identifying and resolving vulnerable dependencies.
In this work, we focus on Dependabot, a popular bot providing security and version updates, and study developers' receptivity to its security updates in engineered and actively maintained JavaScript projects. Moreover, we carry out a fine-grained analysis of the lifecycle of every vulnerability to manifest how they are dealt with in the presence of Dependabot.
Our findings show that the task of fixing vulnerable dependencies is, to a large extent, delegated to Dependabot and that developers merge the majority of security updates within several days. On the other hand, when developers do not merge a security update, they usually address the identified vulnerability manually. This approach, however, often takes up to several months which in turn could expose the projects to security issues.
This paper has won the ACM Distinguished paper award at MSR 2023.Gender and Age in Software Engineering
Overview of our studies of gender and age in software engineering.
Diversity and inclusion in a CS classroom
Diversity and Inclusion in a CS classroom; based on the talk at the University of Twente.
An Empirical Assessment on Merging and Repositioning of Static Analysis Alarms
Static analysis tools generate a large number of
alarms that require manual inspection. In prior work, repositioning of alarms is proposed to (1) merge multiple similar alarms
together and replace them by a fewer alarms, and (2) report
alarms as close as possible to the causes for their generation. The
premise is that the proposed merging and repositioning of alarms
will reduce the manual inspection effort. To evaluate the premise,
this paper presents an empirical study with 249 developers on
the proposed merging and repositioning of static alarms. The
study is conducted using static analysis alarms generated on C
programs, where the alarms are representative of the merging vs.
non-merging and repositioning vs. non-repositioning situations
in real-life code. Developers were asked to manually inspect and
determine whether assertions added corresponding to alarms in
C code hold. Additionally, two spatial cognitive tests are also
done to determine relationship in performance. The empirical
evaluation results indicate that, in contrast to expectations, there
was no evidence that merging and repositioning of alarms reduces
manual inspection effort or improves the inspection accuracy (at
times a negative impact was found). Results on cognitive abilities
correlated with comprehension and alarm inspection accuracy.
Classification and Ranking of Delta Static Analysis Alarms
Static analysis tools help to detect common programming errors but generate a large number of false positives.
Moreover, when applied to evolving software systems, around
95% of alarms generated on a version are repeated, i.e., they
have also been generated on the previous version. Version-aware
static analysis techniques (VSATs) have been proposed to suppress
the repeated alarms that are not impacted by the code changes
between the two versions. The alarms reported by VSATs after
the suppression, called delta alarms, still constitute 63% of the
tool-generated alarms.
We observe that delta alarms can be further postprocessed
using their corresponding code changes: the code changes due
to which VSATs identify them as delta alarms. However, none
of the existing VSATs or alarms postprocessing techniques
postprocesses delta alarms using the corresponding code changes.
Based on this observation, we use the code changes to classify
delta alarms into six classes that have different priorities assigned
to them. The assignment of priorities is based on the type of
code changes and their likelihood of actually impacting the delta
alarms. The ranking of alarms, obtained by prioritizing the
classes, can help suppress alarms that are ranked lower, when
resources to inspect all the tool-generated alarms are limited.
We performed an empirical evaluation using 9789 alarms
generated on 59 versions of seven open source C applications.
The evaluation results indicate that the proposed classification
and ranking of delta alarms help to identify, on average, 53% of
delta alarms as more likely to be false positives than the others.
What Is an AI Engineer? An Empirical Analysis of Job Ads in The Netherlands
Recently, the job market for Artificial Intelligence (AI) engineers
has exploded. Since the role of AI engineer is relatively new, limited
research has been done on the requirements as set by the industry.
Moreover, the definition of an AI engineer is less established than
for a data scientist or a software engineer. In this study we explore,
based on job ads, the requirements from the job market for the
position of AI engineer in The Netherlands. We retrieved job ad
data between April 2018 and April 2021 from a large job ad database,
Jobfeed from TextKernel. The job ads were selected with a process
similar to the selection of primary studies in a literature review. We
characterize the 367 resulting job ads based on meta-data such as
publication date, industry/sector, educational background and job
titles. To answer our research questions we have further coded 125
job ads manually.
The job tasks of AI engineers are concentrated in five categories:
business understanding, data engineering, modeling, software development and operations engineering. Companies ask for AI engineers with different profiles: 1) data science engineer with focus
on modeling, 2) AI software engineer with focus on software development, 3) generalist AI engineer with focus on both models
and software. Furthermore, we present the tools and technologies
mentioned in the selected job ads, and the soft skills.
Our research helps to understand the expectations companies
have for professionals building AI-enabled systems. Understanding
these expectations is crucial both for prospective AI engineers and
educational institutions in charge of training those prospective
engineers. Our research also helps to better define the profession of
AI engineering. We do this by proposing an extended AI engineering life-cycle that includes a business understanding phase.
Joint work with Marcel Meesters and Petra Heck.
Gender and Community Smells
Community smells are patterns indicating suboptimal organization and communication of software development teams that have been shown to be related to suboptimal organisation of the source code. Given a long standing association of women and communication mediation, we have conducted a series of studies relating gender diversity to community smells, as well as comparing the results of the data analysis with developers' perception. To get further insights in the relation bwteen gender and community smells, we replicate our study focusing on the Brazilian software teams; indeed, culture-specific expectations on the behavior of people of different genders might have affected the perception of the importance of gender diversity and refactoring strategies when mitigating community smells. Finally, we extend the prediction model by including variables related to national diversity and see how the interplay between national diversity and gender diversity influences presence of community smells.
This talk is based on a series of papers published in 2019-2022 and co-authored with Gemma Catolino, Filomena Ferrucci, Stefano Lambiase, Tiago Massoni, Fabio Palomba, Camila Sarmento, and Damian Andrew Tamburri.
Bias in MSR Research
In this invited vision talk I am discussing biases in current MSR research related to projects we select, people we talk to and problems we solve.
From team organisation to software quality
Overview of a series of papers published in 2019-2021 on community smells, and their relation to code smells and gender, as well as resolution strategies.
Women in Dutch Computer Science: Best Practices for Recruitment, Onboarding a...
Women in Dutch Computer Science: Best Practices for Recruitment, Onboarding a...Alexander Serebrenik
Women are underrepresented at all levels in computer science (CS) faculties of Dutch
universities. In this report we focus on experiences related to hiring and promoting women as assistant, associate and full professors (or equivalent at NWO-I CWI).My research story (presentation at ICSE 2021 New Faculty Symposium)
Looking back at my academic career so far
Opinion Mining for Software Engineering
In 2003 Dave et al. have coined the term “opinion mining” to refer to “processing a set of search results for a given item, generating a list of product attributes (quality, features, etc.) and aggregating opinions about each of them (poor, mixed, good)”. Nine years later, in 2012 Brooks and Swigger have applied sentiment analysis in the context of software engineering. Today another nine years have passed and it is time to look back: what have we achieved as a research community and where should we go next?
To answer this question we conducted a systematic literature review involving 185 papers. Based on the literature review we present 1) well-defined categories of opinion mining-related software development activities, 2) available opinion mining approaches, whether they are evaluated when adopted in other studies, and how their performance is compared, 3) available datasets for performance evaluation and tool customization, and 4) concerns or limitations SE researchers might need to take into account when applying/customizing these opinion mining techniques. The results of our study serve as references to choose suitable opinion mining tools for SE tasks, and provide critical insights for the further development of opinion mining techniques in the SE domain.
This work has been done together with Bin Lin, Gabriele Bavota and Michele Lanza from Università della Svizzera italiana, Switzerland, Nathan Cassee from Eindhoven University of Technology, The Netherlands and Nicole Novielli from University of Bari, Italy.
Removing Self Admitted Technical Debt
In this talk I will present results obtained on removing self-admitted technical debt. Self-admitted technical debt is an indication in the source code, usually n the source code comments, that the code is not in the right shape yet. Joint work with Emad Shihab, Everton Maldonado, Rabe Abdelkareem, Fiorella Zampetti, Massimiliano Di Penta and Gianmarco Fucci.
Gender Diversity and Inclusion and Software Engineering
In this talk we discuss several issues related to gender diversity and inclusion in software engineering. Based on research 2015-2019.
More from Alexander Serebrenik (20)
Software development is a human activity: understanding software requires und...
Software development is a human activity: understanding software requires und...
Towards Continuous Performance Assessment of Java Applications With PerfBot
Towards Continuous Performance Assessment of Java Applications With PerfBot
“STILL AROUND”: Experiences and Survival Strategies of Veteran Women Software...
“STILL AROUND”: Experiences and Survival Strategies of Veteran Women Software...
A Qualitative Study of Developers’ Discussions of Their Problems and Joys Dur...
A Qualitative Study of Developers’ Discussions of Their Problems and Joys Dur...
Investigating the Resolution of Vulnerable Dependencies with Dependabot Secur...
Investigating the Resolution of Vulnerable Dependencies with Dependabot Secur...
An Empirical Assessment on Merging and Repositioning of Static Analysis Alarms
An Empirical Assessment on Merging and Repositioning of Static Analysis Alarms
Classification and Ranking of Delta Static Analysis Alarms
Classification and Ranking of Delta Static Analysis Alarms
What Is an AI Engineer? An Empirical Analysis of Job Ads in The Netherlands
What Is an AI Engineer? An Empirical Analysis of Job Ads in The Netherlands
Women in Dutch Computer Science: Best Practices for Recruitment, Onboarding a...
Women in Dutch Computer Science: Best Practices for Recruitment, Onboarding a...
My research story (presentation at ICSE 2021 New Faculty Symposium)
My research story (presentation at ICSE 2021 New Faculty Symposium)
Gender Diversity and Inclusion and Software Engineering
Gender Diversity and Inclusion and Software Engineering
Recently uploaded
Earliest Galaxies in the JADES Origins Field: Luminosity Function and Cosmic ...
We characterize the earliest galaxy population in the JADES Origins Field (JOF), the deepest
imaging field observed with JWST. We make use of the ancillary Hubble optical images (5 filters
spanning 0.4−0.9µm) and novel JWST images with 14 filters spanning 0.8−5µm, including 7 mediumband filters, and reaching total exposure times of up to 46 hours per filter. We combine all our data
at > 2.3µm to construct an ultradeep image, reaching as deep as ≈ 31.4 AB mag in the stack and
30.3-31.0 AB mag (5σ, r = 0.1” circular aperture) in individual filters. We measure photometric
redshifts and use robust selection criteria to identify a sample of eight galaxy candidates at redshifts
z = 11.5 − 15. These objects show compact half-light radii of R1/2 ∼ 50 − 200pc, stellar masses of
M⋆ ∼ 107−108M⊙, and star-formation rates of SFR ∼ 0.1−1 M⊙ yr−1
. Our search finds no candidates
at 15 < z < 20, placing upper limits at these redshifts. We develop a forward modeling approach to
infer the properties of the evolving luminosity function without binning in redshift or luminosity that
marginalizes over the photometric redshift uncertainty of our candidate galaxies and incorporates the
impact of non-detections. We find a z = 12 luminosity function in good agreement with prior results,
and that the luminosity function normalization and UV luminosity density decline by a factor of ∼ 2.5
from z = 12 to z = 14. We discuss the possible implications of our results in the context of theoretical
models for evolution of the dark matter halo mass function.
Comparative structure of adrenal gland in vertebrates
Adrenal gland comparative structures in vertebrates
Nutraceutical market, scope and growth: Herbal drug technology
As consumer awareness of health and wellness rises, the nutraceutical market—which includes goods like functional meals, drinks, and dietary supplements that provide health advantages beyond basic nutrition—is growing significantly. As healthcare expenses rise, the population ages, and people want natural and preventative health solutions more and more, this industry is increasing quickly. Further driving market expansion are product formulation innovations and the use of cutting-edge technology for customized nutrition. With its worldwide reach, the nutraceutical industry is expected to keep growing and provide significant chances for research and investment in a number of categories, including vitamins, minerals, probiotics, and herbal supplements.
Richard's aventures in two entangled wonderlands
Since the loophole-free Bell experiments of 2020 and the Nobel prizes in physics of 2022, critics of Bell's work have retreated to the fortress of super-determinism. Now, super-determinism is a derogatory word - it just means "determinism". Palmer, Hance and Hossenfelder argue that quantum mechanics and determinism are not incompatible, using a sophisticated mathematical construction based on a subtle thinning of allowed states and measurements in quantum mechanics, such that what is left appears to make Bell's argument fail, without altering the empirical predictions of quantum mechanics. I think however that it is a smoke screen, and the slogan "lost in math" comes to my mind. I will discuss some other recent disproofs of Bell's theorem using the language of causality based on causal graphs. Causal thinking is also central to law and justice. I will mention surprising connections to my work on serial killer nurse cases, in particular the Dutch case of Lucia de Berk and the current UK case of Lucy Letby.
Unveiling the Energy Potential of Marshmallow Deposits.pdf
Unveiling the Energy Potential of Marshmallow Deposits: A Revolutionary
Breakthrough in Sustainable Energy Science
Cancer cell metabolism: special Reference to Lactate Pathway
Normal Cell Metabolism:
Cellular respiration describes the series of steps that cells use to break down sugar and other chemicals to get the energy we need to function.
Energy is stored in the bonds of glucose and when glucose is broken down, much of that energy is released.
Cell utilize energy in the form of ATP.
The first step of respiration is called glycolysis. In a series of steps, glycolysis breaks glucose into two smaller molecules - a chemical called pyruvate. A small amount of ATP is formed during this process.
Most healthy cells continue the breakdown in a second process, called the Kreb's cycle. The Kreb's cycle allows cells to “burn” the pyruvates made in glycolysis to get more ATP.
The last step in the breakdown of glucose is called oxidative phosphorylation (Ox-Phos).
It takes place in specialized cell structures called mitochondria. This process produces a large amount of ATP. Importantly, cells need oxygen to complete oxidative phosphorylation.
If a cell completes only glycolysis, only 2 molecules of ATP are made per glucose. However, if the cell completes the entire respiration process (glycolysis - Kreb's - oxidative phosphorylation), about 36 molecules of ATP are created, giving it much more energy to use.
IN CANCER CELL:
Unlike healthy cells that "burn" the entire molecule of sugar to capture a large amount of energy as ATP, cancer cells are wasteful.
Cancer cells only partially break down sugar molecules. They overuse the first step of respiration, glycolysis. They frequently do not complete the second step, oxidative phosphorylation.
This results in only 2 molecules of ATP per each glucose molecule instead of the 36 or so ATPs healthy cells gain. As a result, cancer cells need to use a lot more sugar molecules to get enough energy to survive.
Unlike healthy cells that "burn" the entire molecule of sugar to capture a large amount of energy as ATP, cancer cells are wasteful.
Cancer cells only partially break down sugar molecules. They overuse the first step of respiration, glycolysis. They frequently do not complete the second step, oxidative phosphorylation.
This results in only 2 molecules of ATP per each glucose molecule instead of the 36 or so ATPs healthy cells gain. As a result, cancer cells need to use a lot more sugar molecules to get enough energy to survive.
introduction to WARBERG PHENOMENA:
WARBURG EFFECT Usually, cancer cells are highly glycolytic (glucose addiction) and take up more glucose than do normal cells from outside.
Otto Heinrich Warburg (; 8 October 1883 – 1 August 1970) In 1931 was awarded the Nobel Prize in Physiology for his "discovery of the nature and mode of action of the respiratory enzyme.
WARNBURG EFFECT : cancer cells under aerobic (well-oxygenated) conditions to metabolize glucose to lactate (aerobic glycolysis) is known as the Warburg effect. Warburg made the observation that tumor slices consume glucose and secrete lactate at a higher rate than normal tissues.
Leaf Initiation, Growth and Differentiation.pdf
Leaf initiation, growth and differentiation, genetic control of leaf development.
THE IMPORTANCE OF MARTIAN ATMOSPHERE SAMPLE RETURN.
The return of a sample of near-surface atmosphere from Mars would facilitate answers to several first-order science questions surrounding the formation and evolution of the planet. One of the important aspects of terrestrial planet formation in general is the role that primary atmospheres played in influencing the chemistry and structure of the planets and their antecedents. Studies of the martian atmosphere can be used to investigate the role of a primary atmosphere in its history. Atmosphere samples would also inform our understanding of the near-surface chemistry of the planet, and ultimately the prospects for life. High-precision isotopic analyses of constituent gases are needed to address these questions, requiring that the analyses are made on returned samples rather than in situ.
Citrus Greening Disease and its Management
Citrus Greening was one of the major causes of decline in the citrus production. So, effective management cultural practices should be incorporated
Deep Behavioral Phenotyping in Systems Neuroscience for Functional Atlasing a...
Functional Magnetic Resonance Imaging (fMRI) provides means to characterize brain activations in response to behavior. However, cognitive neuroscience has been limited to group-level effects referring to the performance of specific tasks. To obtain the functional profile of elementary cognitive mechanisms, the combination of brain responses to many tasks is required. Yet, to date, both structural atlases and parcellation-based activations do not fully account for cognitive function and still present several limitations. Further, they do not adapt overall to individual characteristics. In this talk, I will give an account of deep-behavioral phenotyping strategies, namely data-driven methods in large task-fMRI datasets, to optimize functional brain-data collection and improve inference of effects-of-interest related to mental processes. Key to this approach is the employment of fast multi-functional paradigms rich on features that can be well parametrized and, consequently, facilitate the creation of psycho-physiological constructs to be modelled with imaging data. Particular emphasis will be given to music stimuli when studying high-order cognitive mechanisms, due to their ecological nature and quality to enable complex behavior compounded by discrete entities. I will also discuss how deep-behavioral phenotyping and individualized models applied to neuroimaging data can better account for the subject-specific organization of domain-general cognitive systems in the human brain. Finally, the accumulation of functional brain signatures brings the possibility to clarify relationships among tasks and create a univocal link between brain systems and mental functions through: (1) the development of ontologies proposing an organization of cognitive processes; and (2) brain-network taxonomies describing functional specialization. To this end, tools to improve commensurability in cognitive science are necessary, such as public repositories, ontology-based platforms and automated meta-analysis tools. I will thus discuss some brain-atlasing resources currently under development, and their applicability in cognitive as well as clinical neuroscience.
filosofia boliviana introducción jsjdjd.pptx
La filosofía boliviana y la búsqueda por construir pensamientos propios
SCHIZOPHRENIA Disorder/ Brain Disorder.pdf
This pdf is about the Schizophrenia.
For more details visit on YouTube; @SELF-EXPLANATORY;
https://www.youtube.com/channel/UCAiarMZDNhe1A3Rnpr_WkzA/videos
Thanks...!
Richard's entangled aventures in wonderland
Since the loophole-free Bell experiments of 2020 and the Nobel prizes in physics of 2022, critics of Bell's work have retreated to the fortress of super-determinism. Now, super-determinism is a derogatory word - it just means "determinism". Palmer, Hance and Hossenfelder argue that quantum mechanics and determinism are not incompatible, using a sophisticated mathematical construction based on a subtle thinning of allowed states and measurements in quantum mechanics, such that what is left appears to make Bell's argument fail, without altering the empirical predictions of quantum mechanics. I think however that it is a smoke screen, and the slogan "lost in math" comes to my mind. I will discuss some other recent disproofs of Bell's theorem using the language of causality based on causal graphs. Causal thinking is also central to law and justice. I will mention surprising connections to my work on serial killer nurse cases, in particular the Dutch case of Lucia de Berk and the current UK case of Lucy Letby.
Multi-source connectivity as the driver of solar wind variability in the heli...
The ambient solar wind that flls the heliosphere originates from multiple
sources in the solar corona and is highly structured. It is often described
as high-speed, relatively homogeneous, plasma streams from coronal
holes and slow-speed, highly variable, streams whose source regions are
under debate. A key goal of ESA/NASA’s Solar Orbiter mission is to identify
solar wind sources and understand what drives the complexity seen in the
heliosphere. By combining magnetic feld modelling and spectroscopic
techniques with high-resolution observations and measurements, we show
that the solar wind variability detected in situ by Solar Orbiter in March
2022 is driven by spatio-temporal changes in the magnetic connectivity to
multiple sources in the solar atmosphere. The magnetic feld footpoints
connected to the spacecraft moved from the boundaries of a coronal hole
to one active region (12961) and then across to another region (12957). This
is refected in the in situ measurements, which show the transition from fast
to highly Alfvénic then to slow solar wind that is disrupted by the arrival of
a coronal mass ejection. Our results describe solar wind variability at 0.5 au
but are applicable to near-Earth observatories.
Recently uploaded (20)
Mammalian Pineal Body Structure and Also Functions
Mammalian Pineal Body Structure and Also Functions
Earliest Galaxies in the JADES Origins Field: Luminosity Function and Cosmic ...
Earliest Galaxies in the JADES Origins Field: Luminosity Function and Cosmic ...
Comparative structure of adrenal gland in vertebrates
Comparative structure of adrenal gland in vertebrates
Nutraceutical market, scope and growth: Herbal drug technology
Nutraceutical market, scope and growth: Herbal drug technology
Unveiling the Energy Potential of Marshmallow Deposits.pdf
Unveiling the Energy Potential of Marshmallow Deposits.pdf
Cancer cell metabolism: special Reference to Lactate Pathway
Cancer cell metabolism: special Reference to Lactate Pathway
THE IMPORTANCE OF MARTIAN ATMOSPHERE SAMPLE RETURN.
THE IMPORTANCE OF MARTIAN ATMOSPHERE SAMPLE RETURN.
Deep Behavioral Phenotyping in Systems Neuroscience for Functional Atlasing a...
Deep Behavioral Phenotyping in Systems Neuroscience for Functional Atlasing a...
Circulatory system_ Laplace law. Ohms law.reynaults law,baro-chemo-receptors-...
Circulatory system_ Laplace law. Ohms law.reynaults law,baro-chemo-receptors-...
Multi-source connectivity as the driver of solar wind variability in the heli...
Multi-source connectivity as the driver of solar wind variability in the heli...
Emotional labor of software engineers
- 1. Emotional Labor of Software Engineers © Mardy Bum Alexander Serebrenik Eindhoven University of Technology The Netherlands
- 5. T. R. Riedl, J. S. Weitzenfeld, J. T. Freeman, G. A. Klein, and J. Musa, What we have learned about software engineering expertise. Berlin, Heidelberg: Springer Berlin Heidelberg, 1991, pp. 261–270.
- 8. Understand and address emotional labor of software developers 1. Detect emotions as felt and as expressed 2. Measure emotional labor 3. Understand antecedents & consequents 4. Propose interventions
- 12. J. A. Morris, D. C. Feldman, “The dimensions, antecedents, and consequences of emotional labor,” The Academy of Management Review, vol. 21, no. 4, pp. 986–1010, 1996. Emotional labor Frequency of emotional display Attentiveness to required display rues duration intensity Variety of req emotions Emotional dissonance
- 14. Emotional labor Antecedents Control: • personality • demographics Focus on: • person: • role • frequency • of contribution • task • project: • software quality • perceived • metrics • “code smells” • community • organisational type • “community smells" Consequents Developers: • well-being • job satisfaction • turnover intention • emotional exhaustion • productivity Project: • software quality • perceived • metrics • “code smells” • community • organisational type • “community smells"