Skip to content
RCreddit.com·

Is it just me, or did everyone quietly stop being a "developer" and become an "operator"?

AI summary

A developer humorously describes a shift in their role from coding to "operating" AI agents. They detail a daily routine of interacting with multiple AI sessions like Claude Code and Codex, approving commands, and orchestrating their outputs. This evolution is framed as a career path from developer to operator, and eventually to a supervisor of AI agents, likening it to a lighthouse keeper overseeing operations.

Why this one

This post offers a first-person account of how AI tools are changing the daily work of developers, unlike more abstract discussions of AI's impact.

Time & source

Times shown in UTC

Display time zone: UTC

Local time zone unavailable; showing UTC.

PublishedOffset at this time: UTC+0Oct 9, 2026, 21:20 UTC

IngestedOffset at this time: UTC+0Oct 10, 2026, 02:00 UTC

Published
Oct 9, 2026, 21:20
Ingested
Oct 10, 2026, 02:00
Source type
Dev community
Tier
Community
Source status
Healthy

Tier is a per-source editorial setting, not a per-item score.

Discussion trend

No comparison yet
Latest 24h versus previous 24h snapshot means · 7-day curve

The percentage is based on collected discussion signal, not new comments or independent people. The curve only compares the same topic across time.

A year ago I wrote code. Now I "operate" agents. I have a terminal with four Claude Code sessions, a review bot, and a job title I gave myself.

My actual day:

- Type "continue"

- Approve a bash command I didn't read

- Tell Codex to check what Claude did

- Tell Claude what Codex said

- Refer to this as "orchestration" in standup

Career path as I understand it: developer → operator → supervisor of operators → person who watches the agents through a window, like a lighthouse keeper.

What are you calling yourself these days?

Source·reddit.com