{"slug": "engineers-don-t-want-to-push-more-slop", "title": "Engineers Don't Want to Push More Slop", "summary": "OliverGraph is developing a tool to reduce AI coding agent errors by capturing the history behind code changes, not just the final diff. The company aims to let agents retrieve context from past debugging sessions, Slack threads, and PRs to avoid producing 'slop' diffs that break existing functionality. This approach contrasts with adding more guardrails or restricting agent output.", "body_md": "One thing I keep hearing around AI coding tools is that engineering leaders want more velocity, while engineers are increasingly worried about what that velocity actually looks like.\n\nNobody wants to spend their day pushing slop.\n\nA team can open more PRs than ever and still end up spending a surprising amount of time reviewing weird diffs or asking why the agent changed something that seemed fine before.\n\nAnd if enough of those changes make it through, customers eventually notice. Bugs show up and small behaviors change. Things feel a little less reliable for everyone.\n\nWhen that starts happening, the obvious reaction is to add more guardrails. Catch the bad diffs before they merge. Or pull back and let agents write less code.\n\nThere's another option we're more interested in: make the agent less likely to produce the bad diff in the first place.\n\nThe model can often write perfectly reasonable code. The problem is that it has no idea what happened six months ago at your company.\n\nSay there's some ugly authentication code. An agent looks at it, sees an obvious cleanup, runs the tests, and opens a PR. Looks good.\n\nExcept six months earlier, an engineer spent an afternoon debugging an auth issue that only happened for one customer with a strange SAML setup. They tried the cleaner approach already and eventually landed on the ugly workaround.\n\nNone of that is obvious from the code.\n\nMaybe pieces of the story are in a PR, Slack thread, or an old agent session. More likely, some of it was just typed into the agent's prompt while the engineer was debugging.\n\nThe next agent doesn't know any of that. This is something we're working on with [OliverGraph](https://olivergraph.com).\n\nWe're trying to save what happened during the work, not just the final diff. If another agent touches that part of the codebase later, it should know what the previous engineer and agent already learned.\n\nWhen an agent starts working on something, it shouldn't just retrieve relevant code. It should be able to retrieve some of the history behind that code too.\n\nSomething as simple as:\n\nThis workaround came from an incident three months ago. Someone already tried removing it and hit a race condition.\n\nThat's the direction we're betting on.\n\nTeams are going to keep using agents to ship more code. I'd rather help make those diffs better than build increasingly large filters to catch the bad ones afterward.", "url": "https://wpnews.pro/news/engineers-don-t-want-to-push-more-slop", "canonical_source": "https://dev.to/zhan1234/engineers-dont-want-to-push-more-slop-7l4", "published_at": "2026-08-18 20:34:27+00:00", "updated_at": "2026-08-18 21:14:21.981135+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "machine-learning"], "entities": ["OliverGraph"], "alternates": {"html": "https://wpnews.pro/news/engineers-don-t-want-to-push-more-slop", "markdown": "https://wpnews.pro/news/engineers-don-t-want-to-push-more-slop.md", "text": "https://wpnews.pro/news/engineers-don-t-want-to-push-more-slop.txt", "jsonld": "https://wpnews.pro/news/engineers-don-t-want-to-push-more-slop.jsonld"}}