Technical Leadership Highlights Summary
Every highlight bullet from the 9 pages in this section, gathered on one page and grouped by the page it came from.
- Technical leadership is a function, not a job title - it can be shared, rotated, or held by one person
- A tech lead trades hands-on coding time for system-level judgment and delegation
- The core job is making decisions that are expensive to reverse, then documenting why
- Authority comes from being right often and visibly, not from a reporting line
- Write options before advocating one
- Time-box spikes; default reversible choices
- Disagree-and-commit after decision record
- Revisit triggers prevent stale decisions
- Score frameworks against squad constraints
- One ADR per significant decision
- Status: Proposed, Accepted, Superseded
- Consequences include negative trade-offs
- Store ADRs in repo docs/adr/
- Link ADRs from service README
- RFC before large PRs land
- Reviewers assigned: owner, skeptic, operator
- Time-box discussion; record decisions
- Spike outcomes linked in RFC
- Async comments before live meeting
- Review for correctness, clarity, and operability
- Nitpicks are optional, not blockers
- Small PRs review faster and better
- Authors summarize intent in PR description
- Rotate reviewers to spread context
- Level expectations written per ladder
- Pair on first production deploy
- Mob for complex refactors
- Growth goals tied to business outcomes
- Feedback weekly, calibration quarterly
- Delegate outcomes, not just tasks
- Document decisions where code lives
- Rotate on-call and release captain
- No single approver on critical modules
- Context summaries in PR and ADR
- Separate people from positions
- Write disagreements before meeting
- Time-box spikes to settle evidence disputes
- Decision maker named upfront
- Disagree and commit after decision
- Decisions written in ADRs, not Slack
- Design review before large Python migrations
- Delegate outcomes with decision authority
- Code review teaches, not gatekeeps
- Disagree and commit after spikes
Revisado por Chris St. John·Última atualização: 31 de jul. de 2026