The promotion into leadership looks like a scaling event. Leave the codebase, direct the engineering team, and multiply your impact across ten people instead of one. The compiler is traded for the calendar. The assumption is that technical intuition will indefinitely survive the transition.
This is a dangerous illusion. Management does not scale technical impact. It scales administrative friction.
⸻
The Drift
Technical capability is not a static asset. It is a perishable muscle. When you stop writing code, the decay begins immediately.
In the first year, you still understand the architecture. In the second year, you understand the abstractions of the architecture. By the third year, you only understand the PowerPoint diagrams of the architecture. You begin managing the bureaucracy of the technology, not the technology itself.
The organization will encourage this drift. It rewards you for resolving cross-functional disputes and aligning stakeholder timelines. It does not reward you for maintaining ground-truth context.
⸻
The Consequence of Distance
In fair weather, this abstraction holds. You can direct teams based on high-level summaries and status reports.
But when pressure hits, the abstraction fractures. When a critical system degrades or a launch timeline collapses, you can no longer rely on status reports. You must diagnose the reality. If your technical muscle has atrophied, you cannot verify the claims of your engineers. You cannot tell the difference between a minor bug and a structural failure.
You become a host to the bureaucracy, incapable of independent diagnosis.
⸻
The Boundary
You cannot lead what you cannot understand. To survive management without losing coherence, you must aggressively defend your technical context.
Do not accept the organization's default calendar. Block uninterrupted hours to read pull requests. Replicate the production environment locally. Build the deployment pipeline yourself at least once. You do not need to be the fastest engineer on the team. You must be technically capable enough to detect when the team is lying to itself.
Protect the terminal. The calendar will always try to consume it.
End.