The impact of stressors on the relationship between personality traits, knowledge collection behaviour and programmer creativity intention in software engineering
Bibliographic record
Abstract
Individual and contextual factors have a profound impact on an individual's creativity. In the first part of this research, we concluded that, for a programmer's creativity intention, individual factors including big 5 personality traits and knowledge collection behaviour play a key role. However, it is important to bring contextual factors into the model to provide a holistic understanding. Hence, the objective of the present research is to expand the earlier work by (i) identifying the software engineering occupational stressors relevant to programmers, and (ii) examining their impact as moderators for the relationship between individual factors (i.e., big five personality traits and knowledge collection behaviour) and the creativity intention of the programmer. To analyse the moderating impact of 6 stressors, the survey questionnaire was used to collect data from 294 programmers working in software companies in Pakistan. The data were analysed using the Structural Equation Modelling (SEM) – Partial Least Square (PLS) technique. The findings revealed that in the presence of a moderate level of stress, the relationship between knowledge collection behaviour and creativity intention was strengthened. Furthermore, stressors interacted differently with different personality traits. An overarching statement could be that most of the stressors positively moderated the relationships between different personality traits and creativity intentions. However, contrary to the prior research, the majority of the stressors negatively affected the impact of the openness to experience trait on creativity intention. The research significantly contributes to the body of knowledge of behavioural software engineering. The findings of this research are novel and intriguing in many aspects and will benefit software organizations to increase innovation, by increasing programmers’ creativity through mitigating stress. The study is also one of the few studies which have attempted to understand the interaction between individual and contextual factors with a programmer's creativity.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.008 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".