Post #3606700
2026-07-05 15:08 UTC
@ramsey@phpc.social As it happens, I came across this article today, and think it makes a similar and relevant point, albeit in a round-about and likely unintentional kind of way.
"Retrieval is the wrong tool for finding code an agent can fetch itself, and the right tool for remembering things an agent has no way to rediscover from the repo as it stands today."
A limited and often lacking ability to curate and navigate memories heavily curtails the usefulness of models.
https://www.qodo.ai/blog/we-built-a-state-of-the-art-rag-system-for-code-review-in-qodo-2-4-we-took-most-of-it-out/
@jrf_nl@phpc.social
Replies (1)
-
@ramsey@phpc.social 2026-07-05 15:12
@elazar@phpc.social @jrf_nl@phpc.social The best way to enforce things, even according to Claude’s docs, is to use static analysis and coding standards tools as part of pre-commit hooks. This will restrict the AI from making the commit until the issues are fixed. It sucks, though, because it’s a waste of tokens for it to churn like that.