11–16 of 16 posts
git.exe can't tell you things like how many references a specific type has. It can get close with grep and friends, but it's not very precise. Preprocessing the codebase into various SQL tables using compiler tools can provide these insights in a much more stable way.
I’m confused: is it just markdown files in git? Or does the hybrid graph+semantic layer matter? If the latter is true, the title is just clickbait right
How does git replace a vector db search exactly? They are orthogonal. Are you gonna burn a million tokens every time you wanna find some relevant files?
I personally turned of indexing feature in Cursor and I use it without it - I haven't noticed any accuracy drop, though my codebase is not enterprise-size one.
Seeing the confusion this article caused maybe someone will find it useful.
How does git replace a vector db search exactly? They are orthogonal. Are you gonna burn a million tokens every time you wanna find some relevant files?
I see the authors don't argue it well enough, but one could use AI agents with simple grep and that proved to be efficient enough to be the default in Claude Code. I personally turned of indexing feature in Cursor and I use it without it - I haven't noticed any accuracy drop, though my codebase is not enterprise-size one.