What humanistic engineering leadership actually requires in an AI-augmented organization.
It's been a wild six to eight months in software engineering, and I've had the unusual vantage point of watching it from the outside while between roles. Distance has a way of making the shape of things clearer.
Here's the shape I see: the loudest voices in the room right now on agentic implementation belong to Meta, OpenAI, Anthropic, Google, Amazon, Microsoft, Cursor, and xAI. They are producing thought leadership and implementation guides at a remarkable pace. What they are not producing, in any serious quantity, is guidance on how to operate an engineering organization in a world where those tools are in use. That gap is not accidental. Every one of those companies is in a race to capture as much market share as possible before the field consolidates and the winners become clear. The marketing, the thought leadership, and the guides all serve that goal. Operating guides don't.
I want to be honest that I can't prove the causation there. But I've been in enough rooms to recognize when the advice being offered serves the advisor as much as it serves me.
What I can speak to is what's actually changing at the team level. Engineers are shipping features faster. They're doing it with less shared understanding of the code being built, with junior engineers developing fewer of the foundational instincts that used to come from writing the thing yourself, with specifications getting more detailed and front-loaded in ways we spent a decade moving away from, and with QA coming back in some form after years of pretending code review was an adequate substitute for it. Production stability remains exactly as hard as it has always been, if not harder.
