The best technical leaders I've worked with rarely held the most senior title in the room. Leadership in software turns out to be far more about mindset and behavior than about authority. You don't need permission to lead; you need a set of habits and the willingness to practice them in front of people. Here's how I think about those habits, grouped by the part of you they draw on.

Leading yourself first#

You can't lead others convincingly until you can lead yourself. That starts with getting comfortable being uncomfortable, because growth and leadership both live just past the edge of what you already know how to do. It means accepting up front that you will make mistakes, and then taking accountability immediately when you do, rather than managing the optics. The leaders people actually trust are the ones willing to be vulnerable, to say "I don't know" or "I got that wrong" out loud.

Underneath all of it is a commitment to keep growing and to stay open to feedback, even when it stings. The moment you decide you've arrived is the moment you stop being worth following.

Leading others#

Once you can hold yourself to that standard, you can turn outward. The foundation is psychological safety — making it safe for people to speak up, disagree, and admit failure without fear. On that foundation you can do the real work of leadership: growing others through mentoring and opportunity, and celebrating others so credit flows generously rather than getting hoarded.

Good leaders give feedback even when it isn't requested, because withholding useful feedback to stay comfortable is a quiet form of selfishness. And throughout, they cultivate a team mindset, so that wins and losses belong to the group rather than to individuals jockeying for position.

Perspective and judgment#

Leadership is also a discipline of attention. It means communicating well, which is more listening than talking. It means knowing how to step back for the big picture when everyone else is buried in the immediate. It means learning to pick your battles, because someone who fights everything teaches people to tune them out. And it means being willing to stand up for ideas you genuinely believe in, even when that's the harder path in the room.

Execution and craft#

None of the above matters if nothing ships. Real leaders carry a bias to action, defaulting to movement over endless deliberation. They keep the team focused on delivery, on getting working software into users' hands. And critically, they protect craftsmanship and quality under the pressure to go faster, because cutting those corners is borrowing against a future the whole team will have to repay.

Serving the people you're building for#

The last piece reframes everything. The work exists to serve the clients and stakeholders who depend on it. A leader keeps the team oriented toward their outcomes, not toward the team's own convenience or cleverness. The point isn't elegant code for its own sake; it's value delivered to people who need it.

A mental model#

If I had to compress all of this into one line, it would be:

Leadership equals communication plus accountability plus safety plus growth plus bias-to-action, anchored by craftsmanship.

Notice that not one of those requires a title. They're all available to anyone willing to practice them. That's the encouraging part and the demanding part at the same time. You can start leading today, and no one is going to hand you the authority to skip the work.