Inefficient codebase searching and indexing leading to wasted time and resources

Signals over time

2 observed signals across 1 sources, tracked for 3 days. Confidence: low.

What people are saying Observed

• “Time wasting is a definite concern - especially when vibe coding doesn't see the impeding brick wall(s) it's about to hit. Vibe coding can be kind of a new type of cowboy coding. It could can be harnessed productively if done mindfully. Interviewing users is critical, more importantly solving problems worth that people are lining up to pay to have solved before writing a line of code is critical. Trialing solutions is always worth learning from, I usually ask about the problem that lead to building it. Sometimes that can be too narrow or vague of a story and you can learn how much of it is a solution looking for a problem, or vice versa.”

  Hacker News · frustration

• “This started by watching the built-in tool calls in Claude code. We noticed that a LOT of the time was being spent searching for lines of code with regex. This approach makes sense when you are working in an unknown environment, but we all work inside of some codebase structure and tracking. This took us down the rabbit hole of codebase indexing and led to us building Indexio. Indexio was built to eliminate the time and tokens agents waste rediscovering a codebase. Regex calls return lots of data each time to the context window which causes bloat over time with items that don't really matter. Since codebase work container mostly static files indexing them and quickly getting to data for discovery is what we were trying to solve. Indexio index's the codebase to its internal DB and then returns what is needed via MCP when asked. We ran into some fun issues when trying to force the session to use a tool call for lookups so there is some aggressive tool call logic which attempts to override built-in lookup tools. If something isn't in the index it will just fallback to regex lookups. The whole system is a single binary written in Rust for performance. In our real world t”

  Hacker News · complaint

• “This started by watching the built-in tool calls in Claude code. We noticed that a LOT of the time was being spent searching for lines of code with regex. This approach makes sense when you are working in an unknown environment, but we all work inside of some codebase structure and tracking. This took us down the rabbit hole of codebase indexing and led to us building Indexio. Indexio was built to eliminate the time and tokens agents waste rediscovering a codebase. Regex calls return lots of data each time to the context window which causes bloat over time with items that don't really matter. Since codebase work container mostly static files indexing them and quickly getting to data for discovery is what we were trying to solve. Indexio index's the codebase to its internal DB and then returns what is needed via MCP when asked. We ran into some fun issues when trying to force the session to use a tool call for lookups so there is some aggressive tool call logic which attempts to override built-in lookup tools. If something isn't in the index it will just fallback to regex lookups. The whole system is a single binary written in Rust for performance. In our real world t”

  Hacker News · complaint