Agentic Engineering is just software engineering best practices
rseroter · x · 2026-08-15
Matthew Brunelle argues that the hype around Agentic Engineering is simply forcing teams to adopt software engineering practices they should have been doing all along.
- Core Idea: Adopting AI tools ironically enforces better discipline because Agents require clear context, docs, and tests to function.
- Examples:
- Using Issue Trackers to define tasks for agents.
- Writing descriptive PRs and docstrings.
- Maintaining meaningful tests and linting standards.
- Planning architecture before coding.
- Public, searchable communication channels.
The author laments that it took the rise of bots to make people excited about basic engineering hygiene.
More from coding & agent
- GitHub workflows show cracks under heavy AI workloads — talkaboutdesign · 2026-08-15
- Deconstructing the AI Agent: Loops, Memory, and MCP — noninertialframe96 · 2026-08-15
- AI coding agent adds workspaces with automatic hinting — zeeg · 2026-08-15
- Deep dive: How Claude Desktop handles MCP resource links and embedded data — SnooDoubts8106 · 2026-08-15
- MongoDB: Small retrieval errors compound significantly in autonomous agent workflows — schwentker · 2026-08-15
- MongoDB.local demo: agent places a PO but only writes a record — no funds move — schwentker · 2026-08-15