#engineering-leadership
12 notes
-
Are We Romanticizing Code?
If agents write the code and we stop reading it, are we romanticizing understanding or losing something we actually need?
-
Attention Follows Accountability
When we promote people, we add accountability without checking if we've removed anything else.
-
Protecting Understanding
What I found when I asked a team about their own code, and what it revealed about technical leadership.
-
I Already Knew
What I learned about distance, delayed escalations, and my own role in both.
-
AI Will Not Fire You. It Will Just Stop Promoting You.
On career transitions, technology shifts, and the AI ceiling that comes down quietly.
-
Credibility Isn't Stored
When influence shifts in the room, knowledge alone does not hold credibility.
-
Avoidance, Disguised as Kindness
When fairness turns into avoidance and decisions get delayed.
-
The Issue Was Raised. The Risk Wasn't.
Why raising the issue and communicating the risk are two different things.
-
Decision Making in Teams: Context vs Command
Why context, not just decisions, shapes ownership and trust in teams.
-
What I Forgot About Building
Rediscovering what it feels like to be fully immersed in one problem.
-
Learning to Let Go of What Made Me Valuable
From being the go-to engineer to building scalable impact.
-
Performance is a People Problem
How unclear ownership quietly kills team performance.