1 engineer + AI agents = a full engineering team. (12-day LMS backend post-mortem)

Reddit r/AI_Agents News

Summary

An engineer built a complete production backend for a university LMS in just 12 days by managing a fleet of AI agents, demonstrating how AI can transform software development by enabling one person to function as a full engineering team.

In Just 12 days, I shipped a complete production backend for a university LMS — by directing a fleet of AI agents instead of writing the code myself. The system: a learning platform for universities. A full GraphQL API over Postgres, ~730 automated tests, 46 schema migrations, and the entire feature set — certificate issuance with PDF generation, a gradebook engine, a digital library with Arabic full-text search, live sessions, discussions, announcements, dashboards, reporting, and role-based access control. Around 40 major work items closed, every one of them landing through a 7-stage automated quality gate. My role wasn't typing code — it was engineering management at machine speed: Setting the constraints. Up to 8 agents worked in parallel, each isolated in its own branch. The rules made that safe: one owner per shared surface per wave (database schema, API definitions), serialized test runs against the shared infrastructure, and hard resource ceilings checked before every new dispatch. Verification discipline. No agent's word counted until the machine confirmed it — commit logs, gate exit codes, disk state. And verification never rested with the same agents who wrote the features: independent agents ran quickstart walkthroughs as real integration tests, security probes proving every access door refuses unauthorized requests identically to nonexistent ones (zero information leakage), and performance measurement with query-plan evidence attached. Judgment calls. When to fix directly versus re-dispatch. When a one-line decision from me beats an hour of agent time. What to verify deeply versus what to accept — and which trade-offs serve the long-lived system. The result: a codebase where every feature is proven by tests its authors never wrote, and every claim carries machine evidence behind it. One engineer plus a managed fleet of AI agents is now a full engineering team. The bottleneck has moved from writing code to directing, verifying, and integrating work at a pace a human team of this size simply could not sustain
Original Article

Similar Articles

How Microsoft Ships Thousands of Production AI Agents (18 minute read)

TLDR AI

Microsoft shares insights from shipping thousands of production AI agents at enterprise scale, covering the engineering challenges of moving from prototype to production, including the agent harness, retrieval-as-a-subagent, agent identity, and rubric-based evaluation loops.