Code of Leadership: How to Lead Engineers by Example When Agents Write the Code

I've started working on my second book, Code of Leadership. Its working subtitle is “How to Lead Engineers by Example When Agents Write the Code.”

There's an interesting tension behind it. A leader needs to delegate and give the team autonomy. Without an engineering practice of your own, it's harder to know what agents can now take on, where their work needs to be double-checked, and what changes to expect from the team. I want to work out how to combine the two without taking all the interesting tasks for myself or becoming a bottleneck :)

The current plan has 20 chapters in five parts:
– A leader's personal practice: what to teach by example and how to stay technically involved without micromanaging.
– Technical fundamentals: going through the engineering cycle with an agent, working with context, verifying results, and handling security and incidents.
– People and teams: delegating to people and agents, hiring and developing engineers, fear of change, and influencing without authority.
– Impact and money: measuring the benefits of AI, discussing expectations with the CEO and board, choosing technology investments, and scaling experiments across the organization.
– Transitions: the first 90 days, working in an unfamiliar domain, handing over responsibility, and a leader's personal system of work.

I'm bringing together my experience, materials from the Code of Leadership, Research Insights, and 3 AImigo podcasts, and conversations with co-hosts and guests. I want every chapter to have a hands-on exercise to help readers test their own assumptions before changing how their teams work.

This is a working plan. Tell me whether you like the idea, or just leave a reaction: 👍 like it, 👌 sounds okay, 👎 don't like it.

#Books #Leadership #Management #AI4SDLC