# Juozas Kaziukenas - Becoming a CTO (Highlights)

## Metadata
**Cover**:: https://readwise-assets.s3.amazonaws.com/static/images/article4.6bc1851654a0.png
**Source**:: #from/readwise
**Zettel**:: #zettel/fleeting
**Status**:: #x
**Authors**:: [[Juozas Kaziukenas]]
**Full Title**:: Becoming a CTO
**Category**:: #articles #readwise/articles
**Category Icon**:: 📰
**URL**:: [juokaz.com](https://web.archive.org/web/20171128214925/https://juokaz.com/blog/becoming-a-cto)
**Host**:: [[juokaz.com]]
**Highlighted**:: [[2021-09-04]]
**Created**:: [[2022-09-26]]
## Highlights
- In actuality, writing code is probably the last thing you will be doing. Instead it’s a person who is able to communicate the technology to others and lead them through execution of the project. ([View Highlight](https://instapaper.com/read/1441527395/17362325))
- As Camille Fournier puts it in ‘On the role of CTO,’ “The CTO must protect the technology team from becoming a pure execution arm for ideas without tending to its own needs and its own ideas.” ([View Highlight](https://instapaper.com/read/1441527395/17362327))
#quote
- If a company needs a CTO then that person defines the vision for a long-term impact on technology. ([View Highlight](https://instapaper.com/read/1441527395/17362328))
- If a CTO doesn’t have that sort of power for technical decisions, they are not a CTO, but more of a lead engineer, in a suit. Suit being optional. ([View Highlight](https://instapaper.com/read/1441527395/17362329))