Engineering Leadership
Practical leadership for software teams, legacy systems, risk, and results.
← All writingYour Team Is Fast. Can It Turn?
A top-fuel dragster is faster than a Ferrari until the road turns. Engineering teams make the same mistake when they optimize for feature output and lose the ability to maneuver.
Constantia: Principles Under Pressure
Standards matter most when following them feels unnecessary. Constantia is the discipline to preserve the controls that protect the team, even when the work is already good.
Virtus: Courage as Managerial Action
Courage in engineering leadership is not bravado. It is saying what is true, advocating for what is right, and accepting the consequences of doing so.
Results Are the Only Thing That Matters
Clean code matters because results matter. Working software deserves respect, but respect is not immunity from change.
Gravitas: Be the Calm
When pressure hits, the engineering leader's job is not just to avoid panic. The job is to project enough calm that the team can think, diagnose, and move.
Pietas: Duty Is Not Always Gentle (Or Easy)
A manager has a duty to the struggling employee. That duty does not erase the duty to the team, the business, the customers, and everyone else absorbing the cost.
You're Accountable for the Team. You're Not in Charge of It.
Tech leads are accountable for team outcomes they can influence, but cannot command. That is the job.
High Performers vs Good Managers: Lessons from the Hardwood
The best contributor succeeds through personal output. The manager succeeds by creating the conditions for other people to produce excellent work.
Managing vs Orchestration and Enablement for Software Development Teams
A development manager is accountable for the performance, but does not produce it alone. The job is to understand the product, draw out each developer's strengths, and shape their work toward the result users need.