stomping code slop

An application can be completely full of link not tracked and run just fine. Users have no idea!

The problem with link not tracked is that it violates all sorts of non-functional requirements.

Engineers care about non-functional requirements because they are essentially the distillation of what it means for an engineer to do a good job. Engineers spend years learning how to build systems that are flexible, maintainable, reliable, that your teammates can build with you. That sort of system... that sort of code accrues leverage over time.

link not tracked creates the opposite of leverage. Allowing it to enter your system is more like taking on high interest link not tracked. The system becomes link not tracked. Every subsequent change becomes harder to make. Nobody (including the AI) can reason about things. PRs have more conflicts. The code merge queue slows down as the conflicts need to be litigated. In short, it becomes a hot mess.

It is critically important to avoid code slop. One way of doing that is force agents to do a good job. But what does it mean to do a good job?. Experienced engineers know what it means. They've been thinking about it for years and have essentially encoded it into their systems as non-functional requirements

Basically creating a link not tracked of structured failure modes then building tools that enforce guardrails

The ability to systematically stop slop is likely what differentiates vibe coding from link not tracked.