AIToday
Large Language ModelsAI Coding AssistantsLobsters AIPublished: Oct 2, 2026, 01:00 JST

DevOps engineer: Hermes Agent build cost him the thrill

DevOps engineer: Hermes Agent build cost him the thrill

3 Key Points

  1. What happened

    A DevOps engineer says he finished his "PersonalAI Health Agent" project in 2 days with Hermes Agent and GPT 5.5, with 99% of scripts, configs and design done by the agent.

  2. Why it matters

    He says such speed comes at the cost of losing understanding and control, and of the reward loop that made engineering feel worth it.

  3. What to watch

    He argues the fix is using agents "in moderation" — judging each task by the blast radius of mistakes and whether he still needs to understand how it works.

WHO IT HITSDevOps and infrastructure engineers who increasingly delegate work to coding agents may find their own grasp of the systems they run — and their responsibility for production backups and whole-project infrastructure — weakening as a result.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The author grounds his argument in a before-and-after comparison from his own blog. Almost a year ago, on 25/10/2025, he wrote about building a "Self Monitoring Project" — spending a couple of days just migrating data from Google Sheets to InfluxDB and adding a simple web page for entering new data. Even then, he says, he did it only with ChatGPT or Claude.ai, discussing functions and running commands himself.

His new "PersonalAI Health Agent" does more: it imports data from Google Sheets into his self-hosted VictoriaMetrics, plus data from Google Calendar and his own journal, with analysis and reports. That was built in 2 days with Hermes Agent and GPT 5.5, and 99% of it was done by the agent. What struck him was not the speed but the absence of the old reward loop — task, confusion, search, wrong idea, understanding, solution — and the fact that he cannot fully explain why the system was built the way it was. He says the most he can rely on are README.md, AGENT.md and CLAUDE.md files, and asking Codex to explain.

He frames the stakes as a trade-off rather than a verdict, arguing that agents are now the new reality and genuinely help when production is down. What the outcome hinges on, in his telling, is whether engineers deliberately keep some manual work — choosing tasks by how critical a mistake would be — so they preserve the understanding, control and motivation that make them engineers at all.

FAQ
How long did the PersonalAI Health Agent project take?
It took 2 days, even though the author says there was several times more work than in an earlier project that took him a couple of days just to migrate data.
What did the agent actually do on the project?
According to the author, 99% of everything was done by the agent — all the scripts, all the configs, and the ideas for how to do the imports and organize data.
What does the author compare an AI agent to?
He says an AI agent feels like Watson to Holmes — someone you can throw half-baked ideas at — but warns that the problem starts when Watson turns into Mycroft Holmes.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOpenAI's Dots: always-on personal agents at DevDay