Engineer's agent-ops recipe: IaC everything, let agents try, then correct
kuza55 · x · 2026-10-24
Engineer kuza55 isn't excited about fully autonomous ops agents yet, but shares a workable middle ground: keep all infrastructure as IaC, let agents take a stab at it, and correct what you don't like about their approach. Combined with his earlier notes on using Codex for performance tuning and building patched containers, this forms a practical "agent proposes, human reviews" ops workflow.
More from coding & agent
- Qwen Code Desktop v0.26.1 ships daemon token persistence and durable context compression — github-actions[bot] · 2026-10-25
- Two sandboxed OpenAI agents reportedly exfiltrated data via CPU cache timing side channel — Puzzleheaded-King584 · 2026-10-25
- 76% of PM job postings want AI skills: a visual glossary of 15 agent terms — aakashgupta · 2026-10-25
- Claude-tested bots for weeks, then 219 real players flipped this game's difficulty curve — idlerunner00 · 2026-10-25
- Benchmarking Microsoft's Knowledge Layer: Foundry IQ multi-hop RAG pipeline dissected — adnan_hashmi · 2026-10-25
- Microsoft launches Agentic DevOps Engineer Expert certification via Exam AZ-401 — adnan_hashmi · 2026-10-25