What Characterizes a Software Leader? Identifying Leadership Practices from Practitioners Social Media

• URL: http://arxiv.org/abs/2605.00191v1
• Date: Thu, 30 Apr 2026 20:12:45 GMT
• Title: What Characterizes a Software Leader? Identifying Leadership Practices from Practitioners Social Media
• Abstract summary: We conducted a content analysis of 116 practitioner-authored articles published on the Dev.to online community.<n>We identified 103 practices for software project leaders, distinguished between recommended and discouraged ones.
• Score: 0.0
• License: http://creativecommons.org/licenses/by/4.0/
• Abstract: Context: Leadership has been extensively studied in management and agile software development; however, prior research predominantly focuses on formal roles and predefined leadership models, offering limited insight into how leadership is experienced and demonstrated by software practitioners in everyday practice. Objective: Our goal is to identify and categorize leadership practices as perceived and reported by software development practitioners based on their professional experiences. Method: We conducted a content analysis of 116 practitioner-authored articles published on the Dev.to online community. Articles were systematically collected, screened, and coded, resulting in the extraction, correlation analysis and categorization of leadership practices grounded in practitioners narratives. Results: We identified 103 practices for software project leaders, distinguished between recommended and discouraged ones. These practices were organized into five categories: People Management & Development, Processes & Execution, Professional & Personal Growth, Communication & Articulation and Strategic Vision. The most recurrent recommended practices include Cultivating & Practicing Interpersonal Skills, Managing & Delegating Team Work, and Practicing & Developing Managerial Skills, whereas Micromanagement, Counterproductive Work Patterns, and Counterproductive Communication Styles emerged as the most frequent discouraged practices. We organized all practices into a conceptual map. Conclusion: The findings indicate that software leadership is mainly associated with managerial and interpersonal practices rather than technical expertise. The resulting conceptual map summarizes these practices and can serve as a reference for understanding leadership in software development contexts.

Related papers

• Guidelines to Prompt Large Language Models for Code Generation: An Empirical Characterization [82.29178197694819]
  We derive and evaluate development-specific prompt optimization guidelines.<n>We use an iterative, test-driven approach to automatically refine code generation prompts.<n>We conduct an assessment with 50 practitioners, who report their usage of the elicited prompt improvement patterns.
  arXiv  Detail & Related papers  (2026-01-19T15:01:42Z)
• From Code Foundation Models to Agents and Applications: A Practical Guide to Code Intelligence [150.3696990310269]
  Large language models (LLMs) have transformed automated software development by enabling direct translation of natural language descriptions into functional code.<n>We provide a comprehensive synthesis and practical guide (a series of analytic and probing experiments) about code LLMs.<n>We analyze the code capability of the general LLMs (GPT-4, Claude, LLaMA) and code-specialized LLMs (StarCoder, Code LLaMA, DeepSeek-Coder, and QwenCoder)
  arXiv  Detail & Related papers  (2025-11-23T17:09:34Z)
• Why Does the Engineering Manager Still Exist in Agile Software Development? [0.0]
  Although Agile methodologies emphasize decentralized decision-making and team autonomy, engineering managers continue to be employed in Agile software organizations.<n>This apparent paradox suggests that traditional managerial functions persist despite the theoretical displacement of managerial hierarchy in Agile.<n>We propose a conceptual model that reconciles Agile principles with managerial necessity, offering guidance for practitioners, researchers, and tool designers.
  arXiv  Detail & Related papers  (2025-10-04T19:52:11Z)
• Empathy Guidelines for Improving Practitioner Well-being & Software Engineering Practices [10.307654003138401]
  Empathy is a powerful yet often overlooked element in software engineering (SE)<n>This paper introduces 17 actionable empathy guidelines designed to support practitioners, teams, and organisations.
  arXiv  Detail & Related papers  (2025-08-05T18:44:12Z)
• Alignment and Safety in Large Language Models: Safety Mechanisms, Training Paradigms, and Emerging Challenges [47.14342587731284]
  This survey provides a comprehensive overview of alignment techniques, training protocols, and empirical findings in large language models (LLMs) alignment.<n>We analyze the development of alignment methods across diverse paradigms, characterizing the fundamental trade-offs between core alignment objectives.<n>We discuss state-of-the-art techniques, including Direct Preference Optimization (DPO), Constitutional AI, brain-inspired methods, and alignment uncertainty quantification (AUQ)
  arXiv  Detail & Related papers  (2025-07-25T20:52:58Z)
• Modelling Interrelations Between Agile Practices: The Agile Map [2.2044574002571182]
  The Agile Map is a theoretical model describing relations between agile practices.<n>The model aims to support practitioners in selecting and combining agile practices in a meaningful way.
  arXiv  Detail & Related papers  (2025-07-14T04:28:37Z)
• Fairness-in-the-Workflow: How Machine Learning Practitioners at Big Tech Companies Approach Fairness in Recommender Systems [21.6740215955322]
  We map the RS practitioner workflow within large technology companies.<n>We identify key challenges to incorporating fairness into existing RS.<n>We offer actionable recommendations for the RS community.
  arXiv  Detail & Related papers  (2025-05-26T02:59:57Z)
• Effective Delegation and Leadership in Software Management [0.49478969093606673]
  This study examined the relationship between delegation and leadership in software management and the impact of these factors on project outcomes. Results showed that effective delegation and transformational leadership styles can improve workflow, enhance team motivation and productivity, and lead to successful software development projects.
  arXiv  Detail & Related papers  (2024-05-02T14:16:05Z)
• Use of Agile Practices in Start-ups [5.664445343364966]
  Small, motivated teams and uncertain project scope makes start-ups good candidates for adopting Agile practices. Use of Agile practices is associated with effects on source code and overall product quality. A team's positive or negative attitude towards best engineering practices is a significant indicator for either adoption or rejection of certain Agile practices.
  arXiv  Detail & Related papers  (2024-02-14T20:12:51Z)
• Charting a Path to Efficient Onboarding: The Role of Software Visualization [49.1574468325115]
  The present study aims to explore the familiarity of managers, leaders, and developers with software visualization tools. This approach incorporated quantitative and qualitative analyses of data collected from practitioners using questionnaires and semi-structured interviews.
  arXiv  Detail & Related papers  (2024-01-17T21:30:45Z)
• Experiential Co-Learning of Software-Developing Agents [83.34027623428096]
  Large language models (LLMs) have brought significant changes to various domains, especially in software development. We introduce Experiential Co-Learning, a novel LLM-agent learning framework. Experiments demonstrate that the framework enables agents to tackle unseen software-developing tasks more effectively.
  arXiv  Detail & Related papers  (2023-12-28T13:50:42Z)
• Empowered and Embedded: Ethics and Agile Processes [60.63670249088117]
  We argue that ethical considerations need to be embedded into the (agile) software development process. We put emphasis on the possibility to implement ethical deliberations in already existing and well established agile software development processes.
  arXiv  Detail & Related papers  (2021-07-15T11:14:03Z)

This list is automatically generated from the titles and abstracts of the papers in this site.

This site does not guarantee the quality of this site (including all information) and is not responsible for any consequences.