兩種都是有效的原型;正確的類型取決於公司所處的階段。動手型技術CTO深入參與架構,有時也參與代碼工作,而戰略型CTO專注於方向、組織和外部關係,並將執行工作委託給他人。
如何思考這個問題
text
HANDS-ON (often early stage)
- Writes / reviews critical code, owns architecture directly
- Fastest at making technical bets
- Risk: becomes a bottleneck as the team grows
STRATEGIC (often later stage)
- Sets direction, hires leaders, represents tech externally
- Scales through people, not personal output
- Risk: loses technical credibility if too removed
具體例子
一位種子階段的CTO親自構建產品的第一個版本。三年後有80位工程師,這個人現在將時間花在戰略、董事會關係和領導力招聘上;codebase由總監和資深工程師負責。
