Skip to content

Engineer as Director of Agents

mihail-eric's framing: the modern software engineer's primary skill shifts from writing lines of code to directing agents — planning, delegating, reviewing, resteering.

"When we talk about multi-agent, one of the set of skills that is becoming increasingly more important is the planning and the delegation. Planning and delegation are still undervalued and yet super crucial."

Concrete shifts

  • From writing code → designing systems.
  • From implementing features → reviewing spec docs and injecting taste.
  • From one-at-a-time work → parallel fan-out to agents (explicitly cited by Eric; echoed by Lloyd's laptop-limit).

Tension with junior engineer path

"The seniors are going to keep having jobs because they're seniors… The juniors are now in the workforce and they're like holy crap, what are we going to do?"

Unresolved: how a junior develops the taste required to direct if the path that built that taste (writing code from scratch, debugging line by line) is abbreviated by agents. Eric doesn't answer this — he frames it as the open curriculum question his Stanford course exists to address.

Why this matters

This is the sociological claim that Lloyd's cloud-agent-primitives and Chase/Partee's coding-agent-as-foundation are the technical substrate for. If engineers are becoming directors, they need fleets, tool runtimes, and auth — everything the orchestration talks describe. Eric is the voice that says "the role is already shifting"; the orchestration talks say "here are the tools for the new role."

Connects to