Technical Leader Worries: I Am Not a Born Leader

Table of Contents

Technical Leader Worries: I Am Not a Born Leader

Have you ever heard about Alexander the Great, Napoleon, J. F. Kennedy, Martin Luther King? I bet you have. These are great historical leaders. These names often come to mind when we think about leadership. When coupled with Hollywood movie characters, we imagine leaders as heroes with strong charisma and exceptional talent for public speaking. This stereotype is hard to shake. But wait a minute… Is this what we should adhere to when talking about technical leaders?

I conducted a survey among software developers and technical leaders, asking about the characteristics of a specific technical leader they appreciated and had encountered in their lives. What do you think they listed?

Technical Leader Sample Actions (from Survey Answers):

  • Asking questions to analyze problematic situations
  • Mediating
  • Not forcing a particular solution
  • Isolating the team from external distractions
  • Engaging, especially in critical situations
  • Reminding the team of their goals
  • Encouraging focus on solutions more than the problems themselves

Sample Skills and Attitudes:

  • Knowledge and experience
  • Communication
  • Patience
  • Mediation
  • Risk-taking
  • Negotiation

Sample Values:

  • Openness
  • Relationships
  • Peace
  • Courage
  • Goal orientation

So, there isn’t much about being a brave hero. Instead, technical leaders must be great problem solvers and team supporters. Most great leaders I’ve met are like that. They focus on their team and are committed to doing great work.

As technical leaders, we must ensure things get done, remove impediments, and create environments where team members want to belong. Unlike charisma, these skills can be developed over time—you don’t need to be born with them, and this is good news.

For those who love models, I can tell you that there are different types of leadership (and indeed many different models). The stereotype we are accustomed to is known as charismatic leadership, but it isn’t the only style. There are also transformational, visionary, transactional, and servant leadership styles you can read more about it here. What we need most in our industry is a mix of transformational and servant leadership.

(top image source: dccomics.com)

(Text translated and moved from original old blog automatically by AI. May contain inaccuracies.)

Tags

Related Posts

A Manifesto Against Developers

A Manifesto Against Developers

I hate you because:

  • You focus on the features of your IDE instead of the features your client/user needs.
  • You consider typing at the keyboard as thinking.
  • You waste countless hours manually testing your code.
  • You spend more time struggling with frameworks than delivering value to end users.
  • You code for hours without asking yourself, “What am I really doing?”
  • You naively believe that technologies and tools will solve your problems.
  • You naively believe that a good algorithm is more important than a good understanding of requirements.
  • You naively believe that your intuition is enough for writing good code.
  • You naively believe that you can manage the complexity of the system piece you’re working on.
  • You agree to unrealistic deadlines.
  • You write poor code and rationalize it with various excuses (because there is no time).
  • In your head, you create code snippets without really knowing what needs to be done.
  • You guess what needs to be done rather than clarifying.
  • You mindlessly follow the technology you use.
  • You don’t understand the tools and technologies you use.
  • You isolate yourself in your piece of code, breaking contact with the world.
  • You think it’s all the fault of managers or clients and believe you can’t do anything about it.

… even though I love you because I am a programmer myself.

Read More

The Natural Order of Refactoring - A Conceptual Sketch

The Natural Order of Refactoring

In software development, refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. This process, often visualized in a conceptual sketch, can help developers understand the natural flow and order in which refactoring should occur.

Read More

Building Knowledge in Teams: Main Mistakes and Strategies

Building Knowledge in Teams: Main Mistakes and Strategies

The topic of knowledge management in teams is largely overlooked by IT leaders. There is a silent assumption that it happens automatically. To some extent, it does, as programmers are accustomed to constantly learning to stay ahead. However, this is not sufficient. It’s not enough for everyone (or realistically, half) to learn individually. If the team is to be effective, cohesive and up-to-date knowledge is needed. Knowledge of new technologies or solutions holds limited value compared to this.

Read More