# Your CTO Should Actually Be Technical

<https://blog.southparkcommons.com/your-cto-should-actually-be-technical/>

- Host: [blog.southparkcommons.com](https://links.thingelstad.xyz/hosts/blog.southparkcommons.com/)
- Saved: September 27, 2022 (2022-09-27T22:48:59Z)
- Record: https://links.thingelstad.xyz/links/1f2ec91ee8a3/
- JSON: https://links.thingelstad.xyz/links/1f2ec91ee8a3.json

## What Jamie wrote

I think it is strange that this is even a question, but it is. Consider other domains for a moment. Would you ask someone that doesn't know finance to be a CFO? Would a company have a head of sales that doesn't know how to sell? The answer is a solid no to both. Yet there is active debate on wether technology leaders, particularly CIO and CTO, need to be technical. **Unequivocally the answer is yes.** You cannot lead a function that you don't understand, and even more importantly, love and have passion for!

Agarwal highlights 5 distinct reasons why you need highly technical leaders in technology. I would agree with all of them, and maybe add some color.

1. Know the difference between good and great is important not just to build good solutions, but also for the team. Technologists don't value praise that is unqualified. (Nobody does really.)
2. Tradeoffs need to be made all the time, and having technical depth results in better tradeoffs.
3. I totally agree with Agarwal's point on commanding respect, but I disagree with his example. Respect comes from depth of experience and breadth of understanding, it is less often from being the best coder.
4. I totally agree with his passion point, and there is absolutely a viral aspect of that passion in teams.
5. Recruiting I agree a thousand percent. Technology is about learning, and great talent wants to be some place where they can learn with others.

My only disagreement with this essay is his assertion that a CTO should pass the coding interview. I disagree. He even suggests they should excel at it. I think this is where Agarwal falls into the trap of equating being a technologist with being a coder. I just don't see that as the case. Look at other fields for examples. Are all great architects also great carpenters? No. Are all great tennis coaches the best tennis players? No. Are all great conductors the best violinists? No. 

Being a great coder is a specific, highly respected and revered skill. Your best coders had better be way better coders than your CTO.

## Facts

- Kind: [Page](https://links.thingelstad.xyz/kinds/page/)

## Appears in

- [WT228: Weekly Thing #228 / Technical, Adversarial, Overcomplicating](https://weekly.thingelstad.com/archive/228/), Featured

## Saved the same week

- [ENS, POAP, and IYK Devcon Bogotá Swag](https://links.thingelstad.xyz/links/67e3bc1fe2c1/) (twitter.com, September 28, 2022)
- [Stop Overcomplicating It: The Simple Guidebook to Upping Your Management Game | First Round Review](https://links.thingelstad.xyz/links/258a0366f0fe/) (review.firstround.com, September 28, 2022)
- [The Hierarchy Is Bullshit (And Bad For Business) – charity.wtf](https://links.thingelstad.xyz/links/1262dba43004/) (charity.wtf, September 28, 2022)
- [Learning is Remembering](https://links.thingelstad.xyz/links/78a46d076060/) (saveall.ai, September 28, 2022)
- [Adversarial Collaboration: An EDGE Lecture by Daniel Kahneman | Edge.org](https://links.thingelstad.xyz/links/0bd0d0a5f1cc/) (edge.org, September 28, 2022)

## Elsewhere

- Wayback Machine: https://web.archive.org/web/*/https://blog.southparkcommons.com/your-cto-should-actually-be-technical/