[2/2] Think Like a CTO (Real CTO: Think like a CTO) (Category Management)

Continuing with the first post I'm going to talk about "Think Like a CTO" in the second part of the book.

7. Annual staff assessment Here the author talks about performance review, promotion and dismissal of employees. I'm separate. told about performance review and about our T-growthwhich we use for employee growth 8. Technology solutions Learn how to make complex technological decisions, such as buy vs build, on-prem vs cloud, reliability vs cost or closed source vs open source, microservices or monoliths. In short, the author considers the pros and cons of each approach. But in general, the overall pattern of consideration should be such that you need to conduct research, compare alternatives, and then make decisions. I'm bigger. 5 years ago told "Architecture at scale or how we at Tinkoff make architectural decisions" 9. Development Here the author tells a couple of pages about project management, then crookedly talks about waterfall and agile. (crooked)And then there's quality assurance. Honestly, it's a very weak chapter, really. For projects and products, I recommend reading my articleI recommend you to read the book “Grokking Continuous Delivery”. told recently 10. Treaty management Here is the hygienic basis for contract work and the importance of attracting lawyers to study contracts:) And the importance of intellectual property licenses in general, and code in particular. 11. Documentation. Here the author tells the database about the documentation. However, here you can see that the author used to work in small offices and, for example, offers to document the release process, and not normally automate it. So, again, a weak chapter. 12. Security Another basic chapter on security. I recommend reading Goolge’s book “Building Secure and Reliable Systems” instead. told. You can also read an old book called Agile Application Security. told earlier 13. Support and maintenance - here the author tells about the operations part, but does it very basic:) I recommend reading my report on how to do this instead. design reliable systems maintain their reliability during operation of the system 14. The growth of the company is a chapter on due diligence, acceptance and transfer of the position of technical director. Normal in principle, but very basic. 15. You, Inc. is a chapter on how to keep up with the times, maintain your technical level as well as the skills of the executive. And in the end, the author gives advice that you should not linger on a job that does not meet your long-term career goals and does not bring satisfaction.

P.S. About the position and responsibility of the CTO I once told in the post about post inflation

#Management #Leadership #Processes #Software #Architecture #Strategy #ChangeManagement