Better Programming

Advice for programmers.

Follow publication

Member-only story

5 Things I’ve Learned About Tech Leadership

dreadfullyposh (Jeremy Gimbel)
Better Programming
Published in
5 min readNov 19, 2019
Photo by Kobu Agency on Unsplash

Tech leadership is a mystery to many. As one racks up years of experience as a developer, there’s often an assumption that one must eventually move into tech leadership to continue to grow. And while this may be true, given the structure and hierarchy of the company you work for, the jump from individual contributor to tech leader isn’t always smooth. The two roles have some crossover in skills, but each also requires its own unique set of skills to get the job done as well.

I’ve been a tech lead of sorts for a lot of my career, from my time managing a development team to my side freelance projects, which often involve managing subcontractors. But it’s only in the last two years that I’ve been at Happy Cog, where I’ve been a tech lead in a more official capacity. With that shift came a lot of trial by fire, and I’ve definitely learned a lot along the way.

There are always ways to improve, and I most certainly don’t have all the answers. But here are a few things I’ve learned along my journey into tech leadership.

1. Leadership Isn’t About Control

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

dreadfullyposh (Jeremy Gimbel)
dreadfullyposh (Jeremy Gimbel)

Written by dreadfullyposh (Jeremy Gimbel)

I write about a web development, leadership, management, humor, and LGBTQ+ issues. Find me at https://dreadfullyposh.com.

Write a response