Fact-check note (2026-10-28):
1. Author, title, and date checked against the original (Better Programming, June 7, 2021). Source:
https://betterprogramming.pub/10-admirable-attributes-of-a-great-technical-lead-251d13a8843b
Translation note: The original is a member-only Medium article we couldn’t access, so the text below is translated from the Chinese version and is not Elye’s exact wording. The well-known quotes (Jobs, Edison, Torvalds, Rothman, Cloud, Eisenhower) are given in their commonly cited English form.
----
By Elye. The original, 10 Admirable Attributes of a Great Technical Lead, is linked in the first comment.
Here are 10 traits of a great technical lead.
1. Has opinions, but isn’t opinionated about everything
No tech lead is without opinions. They got promoted to tech lead because they have core technical strength and can lead a team.
Their opinions shape how the team moves forward. That’s a great thing; at least the team has a direction.
A smart tech lead has opinions but knows when to hold them back and just listen. They know when to draw on the team’s knowledge and pull it together into a better solution before deciding which way to go.
Even Steve Jobs, seen as a dictator who mostly followed his gut, said:
“It doesn’t make sense to hire smart people and then tell them what to do; we hire smart people so they can tell us what to do.” —Steve Jobs
2. Full of energy, but calm in any situation
Some tech leads are bursting with energy. They push the team forward, and their presence energizes everyone. That energy is positive and contagious.
But a great tech lead’s energy isn’t the uncontrolled kind. The point of the energy is to move the team in a positive direction.
In a crisis, an energetic leader doesn’t give off anxious energy. On the surface, they stay calm, because they know that keeps the team from panicking. They’re composed and focused, and they know bad days don’t last forever.
Even when there’s no solution to the problem, a great tech lead will calmly find something positive to build on.
As Thomas Edison said when his factory burned down:
“Although I am over 67 years old, I’ll start all over again tomorrow.” —Thomas Edison
The morning after the fire, he started rebuilding, and he didn’t lay off a single employee.
3. Credits the team for wins, owns the team’s problems
A teacher once told his students:
If my students get an A, that’s the reward for their effort. If my students fail, then I’ve failed as a teacher.
In the same way, a great tech lead always lifts up the team’s accomplishments. When the team ships, the lead praises the team and shares the good news with everyone, talking about how well the team did, not how well they did.
When something goes wrong and needs fixing, though, the tech lead takes the lead in fixing it. The problem may have come from a team member’s mistake, but there’s no time for blame. What matters is finding the problem and fixing it.
4. Manages well, and keeps getting better at coding
“If you’re a tech lead, you need to write code.”
As a senior developer, you have lots of time to write code and become an expert. Once you’re promoted to dev lead or tech lead, that time shifts to meetings, management, discussions, planning, and so on. Coding time shrinks to almost nothing or disappears.
A lot of engineers run into this when they move into leadership. But good tech leads, despite juggling a lot at once, keep their technical skills strong and growing. They still find time to code.
That isn’t easy. It takes a drive to keep learning and to keep improving how you learn. Smart tech leads teach themselves, but they also learn from their team.
Of course, with the right support from the organization, tech leads should still get time to focus on sharpening their technical skills instead of drowning in admin and management. The payoff is huge: the tech lead not only keeps their technical edge but stays closely connected to the team’s technical progress.
Linus Torvalds, creator of Linux and Git, is a great example of a technical leader in this industry.
“Talk is cheap. Show me the code.” —Linus Torvalds
He’s hugely well known in tech, and his technical network is enormous.
5. Appreciates old tech, embraces new tech
There was once a very experienced developer, A. He was a pure vi coder, and a vi-only coder can be extremely efficient. To him, people who used IDEs were lazy modern developers who never bothered to learn shortcuts or improve their efficiency.
There was also a sharp new developer, B, who knew almost every feature and trick in the IDE and was proud of it. To him, people still using vi or Emacs were dinosaurs who’d never made it into the modern world.
Both views are biased. It’s not wrong to like what you like, but you shouldn’t look down on other people’s preferences. A good tech lead has enough experience to see the value of vi and also appreciates the convenience of modern IDEs.
Talking with a tech lead like that is a treat. You get a deep look at the past and how it shaped today’s tech, along with how things have moved forward and how we can combine the two to do better work.
6. Communicates well, and often
What leader doesn’t communicate? They all do. The more senior the leader, the better their communication skills. People who communicate well have more influence and attract more followers.
But some people communicate and influence to get tasks and goals done, for the team or for themselves. Once that’s done, they move on to the next task and goal.
A good leader cares about the people on the team. Beyond communicating and leading, they connect with each team member and understand their needs as a person. They care not only about hitting shared project goals but, more importantly, about helping team members grow.
Someone once asked a group of new leaders: “Why do you train your people?”
The first answered: “So we can standardize the work and not depend on any one person.”
The second answered: “So our team members grow their skills and become more capable.”
Both answers describe results of training. The first focuses on the work; the second focuses on the people.
7. Works hard to give smart answers, dares to ask dumb questions
Tech leads usually mentor their team. They’re typically more experienced in certain areas and stronger technically, so they can guide their team members.
But as mentors, they don’t know everything either. That doesn’t mean a tech lead should ignore or fail to support team members when facing something unknown. The tech lead can still try to give good direction and coach team members on how to find a solution. A tech lead should always try to give the best guidance possible.
On the flip side, team members will sometimes be better than the tech lead in certain areas. In fact, that’s how it should be, since the team’s combined knowledge should exceed the lead’s.
Good tech leads aren’t embarrassed to admit what they don’t know, and they’ll even ask questions that seem dumb. For a leader, it’s better to look dumb now and learn it well than to stay ignorant for the rest of your career. Unanswered questions only compound over time.
“If you ask a stupid question, you may feel stupid. If you don’t ask a stupid question, you remain stupid.” —Tony Rothman
8. Firm when needed, flexible otherwise
Some leaders see everything as a 1 or a 0, with nothing in between. Right or wrong, everything by the book, and if you don’t follow it, there are known consequences.
That rigidity kills creativity. The team’s daily work becomes predictable. On a factory floor that’s fine, because every action has to follow procedure exactly. But eventually all that kind of work will be automated and done by robots.
Other leaders are too accommodating. Nothing matters to them; they just want to please everyone. The team quickly gets chaotic, with no proper workflow or standards. Everyone does what they like, and the team won’t last, because it has no focus or direction.
A great leader knows when to be firm and when to be flexible, and sets clear boundaries. They know what matters and what doesn’t. They know where the bottom line is and stay flexible about how to get there.
“Boundaries are basically about providing structure, and structure is important in building anything that thrives.” —Henry Cloud
That lets team members be creative. They can define sub-boundaries and have some decision-making power.
Boundaries aren’t fixed; they change over time. Great leaders reassess them now and then and shift them where they can to open up new possibilities.
9. Leads, doesn’t force
A shepherd leads sheep by calling out, and the sheep come and gather, no beating or chasing needed. A cowboy drives cattle with a whip to push them where he wants them to go.
Team members aren’t sheep or cattle. We’re civilized people who respond to reasonable direction, and we’re willing to follow direction that fits our values.
A great tech lead shows technical maturity and always gives sound reasons for their decisions. They never force people to “just do it my way.” They may have veto power over the team’s technical direction, but they rarely use it.
At certain critical moments, a tech lead has to make unpopular calls and challenge the status quo. Convincing the team is hard work, but it has to be done. Unless the team comes along, it’s hard to move forward.
“You do not lead by hitting people over the head—that’s assault, not leadership.” —Dwight D. Eisenhower
10. Thinks with the head, acts with the heart
A great technical leader is great not just technically but as a leader.
Technology requires the brain to think logically, drawing on past experience and acquired skills. Leadership requires the ability to connect with people and touch their hearts—a sixth sense you can’t reason your way into. A tech lead needs both.
The stakes for a tech lead are high. The demands from both sides are heavy: it’s the bridge between senior management and the engineers on the ground. Balancing the two abilities is what matters most.
In reality, there’s no single formula for being a great tech lead. It’s a demanding role that takes both heart and head. Sometimes one matters more, sometimes the other. It depends on the situation and on the person.
That may sound impossible, but I’ve seen many great tech leads who, while not perfect, strive to be. They’re smart and kind, knowledgeable yet humble, busy yet approachable. Hats off to them!
Chinese translation: Jane
Comments
What do you think? Share your experience or questions.
Sign in to comment, reply or like. Sign in / Sign up
Loading comments…