How can a software developer be productive?
Answers from top 8 papers
More filters
Papers (8) | Insight |
---|---|
137 Citations | The interaction of the developer and the environment provides explanatory power above and beyond either of the factors separately, suggesting that studies examining strain and performance of developers should explicitly consider and measure the cognitive style fit between the software developer and the software development environment. |
6 Citations | In this paper we argue that software development methods represent theories on how best to engage the impressively complex and inherently socio-technical activity of making software. |
12 Sep 2010 40 Citations | Our findings show that having strong logical reasoning and hypothesis testing skills are differentiating factors in the software developer/tester performance in terms of defect rates. |
We argue that our automated developer expertise ranking can be beneficial in the planning of a software project and is applicable beyond software support in the other phases of the software lifecycle. | |
12 Sep 2010 117 Citations | We conclude that developer metrics are good predictor of faults and we must consider the human factors for improving the software reliability. |
07 Nov 2010 | By studying developer fluency we contribute by determining dimensions along which developer expertise is acquired, finding ways to measure them, and quantifying the trajectories of developer learning. |
30 Jun 2014 12 Citations | These results suggest that developer quality has a strong influence on software quality and should be taken into account when predicting software fault-proneness. |
07 Apr 2014 | Furthermore, we can confirm the need for a method enhancing user–developer-communication in large--scale IT projects. |
Related Questions
What are the factors that affect software developer productivity?5 answersUnderstanding the factors that affect software developer productivity is crucial for organizations to make informed decisions. Several factors have been identified in the research literature. Code quality, technical debt, infrastructure tools and support, team communication, goals and priorities, and organizational change and process have all been found to be causally linked to self-reported developer productivity. Build latency, although a technical problem, can also impact developer behavior and work organization. Additionally, the personality trait of grit has been studied, but it was not found to be positively related to developer performance. Measuring developer productivity is challenging due to the complex nature of their work, which is influenced by both technological and sociological aspects. Emotions also play a role, with positive emotional valence being correlated with perceived productivity in software development.
How can I be more productive in academia?8 answers
How can I be productive when running?15 answers
How can I have a productive retirement?3 answers
How can a programmer be more productive?8 answers
How to increase productivity in software development?6 answers