{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Machine Learning Tech Brief By HackerNoon","title":"Your Architecture Is Why Your Coding Agent Keeps Writing Bad Code","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/93c13037\"></iframe>","width":"100%","height":180,"duration":477,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/your-architecture-is-why-your-coding-agent-keeps-writing-bad-code.\nStop blaming LLMs for bad PRs. Learn how monorepo isolation and tiered AGENTS.md rules eliminate context drift and double your AI coding agent productivity.\nCheck more stories related to machine-learning at: https://hackernoon.com/c/machine-learning.\n            You can also check exclusive content about #ai-coding-agents, #frontend-architecture, #agent-native-architecture, #monorepo, #turborepo, #pnpm-workspaces, #ai-assisted-development, #context-management,  and more.\nThis story was written by: @kayra. Learn more about this writer by checking @kayra's about page,\n            and for more stories, please visit hackernoon.com.\nAI coding agents produce poor code not because of model limitations, but due to chaotic architectures and context bloat. By structuring our frontend into an isolated micro frontend monorepo and replacing monolithic prompt files with a tiered rules system (AGENTS.md), we eliminated cross-module pollution, kept token overhead minimal, and doubled developer productivity.","thumbnail_url":"https://img.transistorcdn.com/KyA01h2FD2insgk-wX_xzV6vbJnTNl2BvPYVL-XaI9A/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMjcyLzE2ODM1/ODI0ODgtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}