Tame Your CTO & Let Yourself Be Tamed
summary
Explains what a CTO actually does: three archetypes—technology custodian, head of delivery, external technical advocate—and why hiring favors ownership and mentorship over pure algorithmic skill. Gives hiring signals (willingness to take the tough task, measurable leverage), managerial surprises (managing execs, a CTO’s expiration date), a market datapoint (30% salary rise in 2021 in Poland), and a concrete AI claim: large language models already save hours of Python work and can generate, compile and execute code to replace routine development.
AI-written summary · about
chapters (17)
- 0:00Welcome and introduction
- 1:38What is C Morning Coffee?
- 3:23Rules and expectations
- 4:06Why talk about CTOs today?
- 5:12What does a CTO do?
- 10:09Should CTOs code?
- 14:48Working with people as a CTO
- 17:38Biggest surprises in the CTO role
- 21:08Is leadership for everyone?
- 25:24What CTOs look for in engineers
- 29:19Estimations and their value
- 34:56Seniority and leverage
- 39:12CTO perspective on salaries
- 47:00Remote work productivity
- 48:49AI replacing engineers?
- 49:30Future of AI in engineering
- 59:33Closing and afterparty
related talks
25mWhat does a CTO even do?
01h 02mSo, you want to be a CTO?
39mThe CTO Role: Responsibilities, Risks, and Screw-ups
26mThe CTO Spectrum – Which Archetype Are You
52mWhy CTOs Should Code
39mWhat Questions Do CTOs and Tech Leads Solve?
43mOne doesn't simply walk into a management position -what I learned...
13mThe CTO is dead, long live the CTO