New ask Hacker News story: Ask HN: Books and Courses for Wannabe CTOs and Heads of Engineering?

Ask HN: Books and Courses for Wannabe CTOs and Heads of Engineering?
2 by iforgotmypass | 0 comments on Hacker News.
I've got a background as a software developer and development team lead. I've filled shoes as an architect, infrastructure expert and an IT project manager. I've got a solid understanding of the business side as well. What books, courses and other "theoretical background" you would recommend to make the jump / transition from a development team lead to a Head of Engineering or CTO at a company with 100-250 employees? This is not a question about career progression as it is more about "growing with the company" (so gaining all the required knowledge in advance before actually gaining that know-how in practice - for example, when you are a "CTO" of small yet fast-growing startup). The recommended literature should contain info on: * scaling the software development team (e.g. if I've lead a team of 8, how do I handle a team of 50-70 engineers? What are the common pitfalls to scaling the engineering team? Some common examples for the organizational structure for handling multiple software development teams?) * defining and measuring KPIs and/or OKRs for technical people in all the levels * project management techniques and tools to gather all the data (and what data and how should I gather?) to be able to make any decisions * talking to the management (reports, bridging the understanding between the business and the IT) * everything else I haven't thought about