Code of Leadership
Topic map
Episodes grouped by subject, connections between topics and ideas for future conversations. Select a topic to find recordings.
Published episodes: 88. Proposals: 4. Ideas for discussion, without a schedule or announced releases.
Show
Green: archive topics. Amber: proposals. Dashed lines connect topics sharing episodes; solid lines link proposals to their starting topics. Connections are shown for the selected topic.
Episodes: 86
Engineering management
Connected topics and proposals
№87 ·
Organizational Redesign of a 1,000-Engineer Division№86 ·
Agents Write Code. Is Development More Effective?№85 ·
FDE: Who Makes AI Work for the Customer?№84 ·
Does AI Turn Developers into Managers? — Andrey Dmitriev№83 ·
How Engineers Learn to Negotiate — Sergey Kiselev№82 ·
Why Leaders Return to Code — Nikita Belokopytov№81 ·
Leading in an Unfamiliar Field — Leonid Chernyy№80 ·
Leading a Team with AI — Dmitry Tverdokhlebov№79 ·
Code, Cars, Insurance: What a CTO Must Relearn — Fyodor Sukharev№78 ·
CTO Freedom in Startups and Corporations with Kirill Evseenko№77 ·
The First 90 Days as CTO№76 ·
Product Engineer: How the Programmer's Role Will Change in the Next Three Years№75 ·
How Can Mid-Sized Businesses Adopt AI Without Big-Business Budgets?№74 ·
The Junior Engineer After Code: Growing Engineers When Agents Do the Implementation№72 ·
What Remains Scarce When Code Becomes Cheap?№70 ·
How to Build Your Own Management System№69 ·
AI Adoption: It's the Protocol, Not the Model№68 ·
PRD == Evals: How AI Blurs the Product–ML Engineer Boundary№66 ·
Multi-Agent: Get the Most Out of One Agent First№67 ·
Digital Team Lead: Can Developer Effectiveness Be Measured from Code?№65 ·
How to Bring GenAI into Operational Work№64 ·
Consulting in the AI Era: Beyond Polished Presentations№63 ·
Harness: A Six-Month Half-Life№62 ·
AI-Native: Understanding Can't Be Delegated№61 ·
AI Products: First Figure Out Whether You Need AI№60 ·
Keep It Simple: Steps Without Principles Are a Cargo Cult№59 ·
AI Impact: 90% per Step, 5% per Cycle№58 ·
Vibe Coding: Know What You Want№57 ·
AI Bubble: It Settles Where Precision Isn't Needed№56 ·
Reliability: Never Roll Out to All of Prod at Once№55 ·
Legacy: Facade First, Storage Later№54 ·
Mobile Banking: A Branch in Your Pocket№53 ·
GenAI Security: 99% Is Not Protection№52 ·
IC Track: Grow by Scope, Not Headcount№51 ·
Conferences: The Talk Is the Product№50 ·
Data Platform: Changing Planes Mid-Flight№49 ·
Car Sharing: Getting Operations in Order№48 ·
Engineering Management: The Bottleneck Is the Organization№47 ·
Architecture: Quality Attributes First, Trade-offs Later№46 ·
Platform: An Engineer with a Product Mindset№45 ·
The Road to CTO: Catch the Window of Opportunity№44 ·
Engineering Management: An Org Structure for the Moment№43 ·
From Physics to Engineering: Curiosity Pays Off Later№42 ·
Engineering Manager Career: Delivering Value Through People№41 ·
T-Investments: Three Years Defending the Broker Idea№40 ·
Media Platforms: Rebuilding Trust with Small Releases№39 ·
Social Platforms: Merging Them into One№38 ·
Origination Platform: Someone Else's Failure Is Your Problem№37 ·
Frontend Reliability: From Alerts to CRO№36 ·
Analytics and DnD: Boredom as a Signal to Grow№35 ·
Engineering Fundamentals: Algorithms Are Money№34 ·
Technology Strategy: Build It Like a Product№33 ·
IDP: Make the Right Path the Easy One№32 ·
X-Sell: Sales Channels Need a Shared Brain№31 ·
Hooked: How a Product Becomes a Habit№30 ·
From Developer to Manager: Don't Judge People by Yourself№29 ·
Think Like a CTO: A Baseline for Small Companies№28 ·
Design in Software Development: It's Not About Graphics№27 ·
T-Bank Web: From a Monolith to Independent Blocks№26 ·
SRE: Hand On-Call to the Developers№25 ·
Group Dynamics: No Authority, Only Approvals№24 ·
Databases and Platforms: Logic in the Database Hits the Hiring Ceiling№23 ·
From Lead Back to Senior: Rebuilding Influence from Zero№22 ·
Data Engineering: From a Rocket Plant to Amazon№21 ·
A Philosophy of Software Design: Deep Modules Hide Complexity№20 ·
Software Architecture: Why We Decided It This Way№19 ·
Education: Teach the Hard Stuff, Not the Job Spec№18 ·
Processes and Tools: Words Fade, Tooling Stays№17 ·
Architecture Review: One Table Instead of Pinball- Subscriber AMA: Books, Daily Routine, Career, and the Path to CTO
№16 ·
The Five Dysfunctions of a Team: No Trust, No Real Debate№15 ·
Security: Vulnerabilities Are Born in Architecture№14 ·
Risk Tech: A Credit Decision in Seconds№13 ·
Accelerate: Measure Delivery, Not Lines of Code№12 ·
Spirit: An Internal Platform Run as a Product№11 ·
Systems Analysts: A 900-Person Profession№10 ·
An Elegant Puzzle, Part 2: Reorganize Only as a Last Resort№9 ·
An Elegant Puzzle, Part 1: Move Domains, Not People№8 ·
Statist: Collecting Events Is Only Half the Job№7 ·
Your Brain at Work: Attention Is a Battery№6 ·
Staff+ Engineers: Growing Without Going into Management№5 ·
The Phoenix Project: When the Hero Is the Bottleneck№4 ·
Turn the Ship Around: Leaders, Not Followers№3 ·
Herding Cats: Delegate, Don't Write More Code№2 ·
Antifragility in IT: Hypotheses Instead of Specs№1 ·
Team Topologies: Teams Built for Flow, Not the Org Chart