Your article matches my own intuition, and there's a case to be made for adjusting our architectural patterns to better compartmentalize those parts of the app we can let an agent go nuts on. For example, could we leave all of the UI to the agent? Or things like the MCP Server implementation of the app? I'm not quite sure where to draw the line yet. I'm quite comfortable leaving unit tests to the agent by now, but if it's user visible behavior, I still find the agent's work to be off somehow. Ymmv, I guess.
Yeah, I guess it is quite hard to tell where the line should be drawn, and we probably need to rely on human intuition and experience. One thing that the article left out that I have thought more of afterwards is that the classification would need to be relative to the enterprise as a whole. So if you are building a gimmick app for a birthday party you might just vibe code the whole thing, including its "core", but if you are a building business-critical sales system for a major company, the impact of something going wrong would rate the core at the upper end of the scale.
