I started reading it as an e-book, then ordered a print copy, read it in bits and pieces, and eventually read it cover to cover. The book gives a general overview of what a CTO does. Senior leaders at that level probably won't find anything new here, but it's a well-written set of reminders.
Some highlights
✨ The idea of the first hundred days in a new role is explained really well (see "The First 90 Days" by M. Watkins - a whole book on that topic). It's mostly about getting to know your team, processes, and existing practices.
✨ The author shares useful tips on building a 1-on-1 culture with your team members - including what NOT to talk about in those meetings. I actually put these tips to use at KP Tech.
✨ Most of the book is about working with people - building and managing a team. This shows the author as a real team player who values team results over personal status. I liked that.
On the technical side, the author keeps things high-level rather than going deep. But he still offers a few solid recommendations. For example, on page 256 (in the Russian edition) he briefly covers one of the trickiest parts of an app release cycle - handling database schema changes.
It's not a complete guide, but it works well for getting into the role or understanding it from the outside. For that purpose, I'd recommend it 👍
Top comments (0)