Software developers are not automatically people managers—but coding agents can make management-like work a larger part of building software. In a September 16, 2026, InfoWorld opinion article, Nick Hodges argues that developers increasingly assign work to agents, supply context, monitor progress, review output, and decide when it is ready. That is a useful analogy for a shift in day-to-day work, not evidence that every developer’s job has changed or that agent supervision is the same as managing people.
Why coding agents make the “manager” analogy plausible
Hodges’s argument starts with a familiar career tension: advancement in software has often been associated with moving away from individual coding. Developers could reach a ceiling on a conventional individual-contributor ladder and feel pressure to pursue management for greater pay or advancement. Technical paths such as architect, staff developer, or chief scientist offered alternatives, but those jobs could also mean less programming and more meetings.
Senior technical work has never been only about writing code. Experienced developers coordinate with colleagues, guide technical decisions, lead work, and review others’ contributions. A tech lead, for example, may assess code quality and oversee work without taking responsibility for a colleague’s performance reviews or career. Hodges’s point is that coding agents add another recipient of this direction and review: software that carries out assigned work.
What managing a coding agent involves
In Hodges’s account, working effectively with an agent involves a sequence of supervisory tasks, rather than simply prompting it and accepting whatever it produces.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
- Assign a bounded task. State what the agent should accomplish, so its output can be judged against a defined objective.
- Supply context. Provide the relevant requirements, codebase information, and constraints the agent needs to work usefully.
- Choose the working environment. Give the agent an appropriate place to do the work, with suitable boundaries.
- Monitor progress. Check how the work is going rather than assuming that a plausible start will lead to a correct result.
- Review the code. Evaluate the output before it is accepted; delegated work still requires technical judgment.
- Decide when it is ready. Determine whether the result is fit to check in, or whether it needs revision or should not be used.
Jim Bourke, identified by InfoWorld as founder and CEO of Zide Software, describes his view this way: “A coding agent is most useful when you treat it more like an employee than an autocomplete tool,” and “It needs a clear assignment, the right context, a safe place to work, checkpoints, and a way to evaluate the result.” These are Bourke’s remarks as quoted in Hodges’s opinion article, not independent evidence that all developers work this way.
Agent supervision is not people management
The comparison is useful because both kinds of work involve direction, context, progress checks, and evaluation. But the responsibilities diverge where human accountability begins. A developer reviewing an agent’s output is not, by that act alone, responsible for an employee’s career, wellbeing, or performance evaluation.
| Responsibility | Working with a coding agent | Managing a human colleague |
|---|---|---|
| Assign work and provide context | Part of the supervisory practices Hodges describes. | Comparable coordination may be involved. |
| Monitor progress and review output | Part of deciding whether agent-produced work is usable. | May also involve guidance and evaluating work. |
| Career and performance responsibility | Not established as part of supervising an agent in the article. | Can be part of formal people-management responsibilities. |
Hodges explicitly cautions that the skills involved overlap but are not congruent. Calling developers “managers” captures a change in the shape of some technical work; it should not erase the distinction between directing a tool and being accountable for a person.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What this could mean for developer career paths
The article raises, but does not answer, whether agent supervision will reshape advancement. If more development work involves setting direction and evaluating delegated output, those abilities may become more visible alongside technical expertise. But Hodges does not establish which skills employers will reward, how career ladders will change, or whether this will create a new route for developers who want to advance without becoming people managers.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThere are no adoption, productivity, displacement, or workforce-share statistics in the article. Its headline is an opinion thesis, not a measured claim that all developers have become managers. The defensible takeaway is narrower: coding agents make supervisory tasks more prominent in the work Hodges describes, while the scale and career consequences remain unsettled.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
