Posts
Start with Your Feet and Look to the Horizon
Having mentored and managed numerous Engineering Managers, I’ve often seen them navigating new, sometimes overwhelming, leadership challenges. Whether they’re onboarding onto an unfamiliar team, building a new team from scratch, or leading through significant changes like a shift in scope or a key team member leaving, the uncertainty can be daunting.
Push vs Pull Learning
As a software engineer, you’re always in learning mode—whether it’s a new tech stack, a fresh codebase, or an unfamiliar domain. When someone on my team is onboarding to something new, they often ask me, “What’s the best way to get up to speed?” The answer varies, but I find it helpful to discuss two key approaches to learning: push learning and pull learning.
A Portfolio of Work
At any level of engineering, you are responsible for some work. Early in your career, it’s a ticket, a task. The work is narrow but likely deep. As you grow in your engineering leadership career, your purview becomes broader. And at some point, you’re no longer responsible for one thing. You become responsible for a collection of work. We call this a portfolio of work. Your portfolio of work and how you manage it constitute the impact you can make. And the further along you get in your career, the more nuance exists in how you can manage it.
Stop Repeating Yourself with the Rule of Three
It’s Monday. You organize your day, and you double-check your calendar. You go to your first 1:1. Your team member asks why the team is changing your product’s strategy. You share your thoughts. Now it’s Tuesday. You have a 1:1 with your designer who asks the same question. You share your thoughts. Now it’s Wednesday, you meet with your TL who asks about the changes in product strategy. Congrats! You’ve just hit the Rule of Three.
As We Know It
The value of software is largely driven be two factors: productivity gained and distribution. These can be considered as depth and reach. Over the years, distribution has shifted from on site to box to over the wire. And each has led to incentive shifts as the benefits of software became democratized through these increasingly pervasive distribution channels