What Characterizes a Software Leader? Identifying Leadership Practices from Practitioners Social Media
By analyzing 116 practitioner-authored articles from the Dev.to community, this study identifies and categorizes 103 recommended and discouraged leadership practices into five key areas, revealing that effective software leadership is primarily defined by managerial and interpersonal skills rather than technical expertise.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to figure out what makes a great captain of a ship. Most studies look at the official job descriptions, the rules written in the rulebook, or the titles people hold. But this paper decided to do something different: it went out to the "town square" (a social media site called Dev.to) and listened to the sailors themselves. They read 116 stories written by software developers about what it actually feels like to lead a team in the real world.
Here is what they found, broken down into simple ideas and metaphors.
The Big Picture: It's Not About the Tools, It's About the People
If you think a software leader is just a super-coder who knows the most complex math, this study says you're looking at the wrong part of the ship.
The researchers found that leadership in software is mostly about "soft skills" and managing people, not about writing code.
- The Metaphor: Think of a software team as a garden. The "technical skills" are the seeds and the soil. But the "leader" is the gardener. The gardener doesn't need to be the best at making seeds grow (the plants do that); they need to know how to water them, pull the weeds, protect them from storms, and make sure they get enough sun.
- The Finding: The most praised leaders weren't the ones who wrote the most code; they were the ones who were good at talking, listening, helping others grow, and keeping the team happy.
What Good Leaders Do (The "Recommended" List)
The researchers identified 103 things good leaders do. If you had to pick the top three, they are:
- Being a People Person: Cultivating good relationships and interpersonal skills.
- Delegating: Trusting the team to do the work and letting them shine.
- Growing as a Manager: Constantly learning how to be a better boss.
The "Technical" Part:
Does technical knowledge matter? Yes, but it's like a special tool in the toolbox.
- Leaders need to know enough to check the work (like reviewing code) and make sure the quality is high.
- However, the study found that technical skills are only about 12% of what makes a leader successful in the eyes of the community. The other 88% is about managing people, strategy, and communication.
What Bad Leaders Do (The "Discouraged" List)
The researchers also looked at what leaders shouldn't do. The most hated behavior? Micromanagement.
- The Metaphor: Micromanagement is like a parent who won't let their child tie their own shoes because they think the child will do it wrong. It's hovering over every single move.
- Other Bad Habits: Being arrogant, having a "fixed mindset" (refusing to learn), communicating in a passive-aggressive way, or creating a toxic environment where people are afraid to speak up.
Interestingly, technical mistakes were rarely blamed on leadership.
- If a piece of code broke, the community didn't usually say, "The leader failed because they didn't know enough code."
- Instead, they said, "The leader failed because they didn't listen to the team," or "The leader was too bossy."
- The Metaphor: If a car breaks down, we blame the mechanic for the broken engine. But if the mechanic is a terrible boss who yells at the crew and steals their tools, we blame the boss, not their wrench skills.
The Five "Rooms" of Leadership
The researchers organized all these behaviors into five main categories, like five different rooms in a house:
- People Management & Development: The living room. This is where you grow the team, mentor them, and make them feel safe. (This was the biggest room).
- Processes & Execution: The kitchen. This is where the daily work happens, and where leaders make sure things run smoothly and quality is high. This is the only room where technical skills are heavily used.
- Communication & Articulation: The front door. How the leader talks to the team, the bosses, and the clients.
- Strategic Vision: The map room. Looking at the horizon and deciding where the ship is going.
- Professional & Personal Growth: The gym. The leader working on their own self-improvement.
The "Concept Map"
The paper ends with a visual map (Figure 4). Imagine this as a roadmap for becoming a leader.
- It shows that the path to being a great software leader is paved mostly with interpersonal skills (green circles).
- Technical skills (orange circles) are there, but they are small stepping stones, not the whole road.
- The map also highlights "potholes" (bad behaviors) like micromanagement or arrogance that can crash your journey.
The Bottom Line
This study tells us that to be a great leader in software, you don't need to be the smartest coder in the room. You need to be the best gardener in the room. You need to know how to help your team grow, how to clear the path for them, and how to keep the environment healthy. If you focus on the people and the process, the technical success will follow.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.