{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Machine Learning Tech Brief By HackerNoon","title":"Agents Are Not the Answer. Engineering Is.","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/994538a1\"></iframe>","width":"100%","height":180,"duration":2351,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/agents-are-not-the-answer-engineering-is.\nI thought the problem was the model. It was the config. How to engineer rules, skills, hooks and subagents around a coding agent, and test them like software.\nCheck more stories related to machine-learning at: https://hackernoon.com/c/machine-learning.\n            You can also check exclusive content about #ai-agents, #rules, #ai-skills, #hooks, #subagents, #claude-code, #ai, #claude-code-rules,  and more.\nThis story was written by: @renanb. Learn more about this writer by checking @renanb's about page,\n            and for more stories, please visit hackernoon.com.\nThe text describes how to build and maintain a coding agent, a language model that runs in a loop, by engineering the context around it. The agent's behavior is defined by a set of files, including permanent instructions, rules, skills, subagents, hooks, permissions, and memory, which can be treated as software with its own architecture, defects, and testing requirements.","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}