Skip to content
#Management

Code of Leadership 29 "Think like a CTO" (Category Management)

#Management #Leadership #Strategy #PlatformEngineering #Engineering #Software #Architecture #SelfDevelopment

Another one. podcast Code of Leadership Review: “Think Like A CTO” ("Think like CTO."). In the analysis helps a cool guest, Sasha Shevchenko. Sasha is a colleague of mine who is a technical leader in managing digital ecosystems. Heads up. 10+ mobile bank product teams. He manages the home screen and private profile, UX, ESG and non-customer tracks, and other key products and services. I have already talked about this book in two parts: 1 and 2

Issue available in Youtube, VK, Podster.fm, Ya Music

In an hour, we discussed topics. Role and responsibility of the CTO The life cycle of the company and how the role of the CTO is changing Expectation management and communication

  • Team formation and management Technology strategy and long-term vision
  • Budget and project management Quality of engineering practices: QA, reliability, security, ... Processes and importance of documentation
  • Self-development and successor training

Recommendations for study from Sasha Shevchenko

Management

  • "Ideal Leader" | Adizes Itzhak - more info my post
  • "Career Software Engineering Manager" | Stanier James - I have on my shelf, but haven't read it yet
  • "The Elegant Puzzle" ("Elegant puzzle.") Will Larson - Disassembled with Eugene Sergueev in episodes Code of Leadership 9 and Code of Leadership 10

Leadership

  • "Leadership challenge." Five practices of outstanding leaders" | James Kuzes, Barry Posner
  • "Turn the ship around" (Turn your ship around.) | David Marquet - disassembled together with Ekaterina Shestimerova in Code of Leadership 4
  • "The Five Dysfunctions of a Team" (Five vices of the team.) | Patrick Lencioni - disassembled together with Andrei Sokolov in Code of Leadership 16 Servant Leadership, Situational Leadership, Management 3.0"Management" 3.0I read on 2/3 A couple of years ago, but could not finish because of the enchanting number of references to other books from the author.

Creation of teams "Team Topologies" | Skelton Matthew - dealt with by Stas Halup in Code of Leadership 1

  • "Real powers." Employee independence as the key to success | John Schole
  • The Six Geniuses of the Team | Patrick Lencioni - I have it on my shelf, but haven't read it yet
  • Lessons from Outstanding Leaders | Peter Sims
  • Tuckman's model.
  • Conway's reverse maneuver.

Development

  • "Learning DDD" ("Studying DDD subject-oriented design") | Hononov B - I'm a lot wrote about the book discussed hers
  • "Accelerate" ("Hurry up!") | Forsgren Nicole - disassembled together with Igor Kurochkin in Code of Leadership 13
  • "Site Reliability Engineering" | Beyer B. told book
  • "Building Secure and Reliable Systems" ("Safe and reliable systems") | Adkins H. told book
  • Data Mesh. The new paradigm of working with data | Degani J.

Novels about development Project Phoenix | Jin Kim - discussed the book with Ivan Mikheev Code of Leadership 5

  • Target. Continuous improvement process | Goldratt. Waltzing with Bears: Risk Management in Software Projects | DeMarco Tom

Change management

  • Our iceberg is melting. How to get results in the face of change | Cotter - I'm already told book
  • Spiral climbing. Theory and practice of reforming organizations | Mark Rozin

The book also contains references to

  • Think slowly. Decide quickly | Daniel Kahneman - I'm already told book Unrecoverable costs or the Concorde effect
  • Gartner's curve. told about

#Management #Leadership #Strategy #PlatformEngineering #Engineering #Software #Architecture #SelfDevelopment