Technical leadership is guiding the technical direction of a team or a company without necessarily managing people. A tech lead or architect chooses boundaries, records decisions, grows other engineers and keeps the system understandable as it changes. Influence comes from clarity and judgment, not from rank.
Key concepts
- Design documents: write the problem, the options and the trade-offs before building, so others can challenge them.
- Architecture decision records: short notes saying what was decided, why, and what was rejected.
- Trade-offs: every choice buys one quality, such as speed or simplicity, at the cost of another.
- Technical debt: shortcuts that speed today and slow tomorrow; track it and pay it on purpose.
- Mentoring and review: raising the team's level is the leverage that scales.
Vocabulary
- Tech lead: the engineer who guides a team's technical choices while still building.
- RFC: request for comments, a proposal circulated for feedback before a decision.
- Bus factor: how many people could vanish before knowledge is lost.
- Evolutionary architecture: a design that expects change and keeps it cheap.
What to study, in order
- Write a design document for a real change: goals, non-goals, options, risks.
- Keep a log of architecture decisions for one project for a month.
- Review a system's architecture by drawing its components, data flows and failure points.
- Study how coupling and cohesion shape the cost of change.
- Mentor someone through a design from first idea to release, and ask what they would change.
Related tags
#architecture #engineering-management #code-review #design-patterns #documentation