Really interesting idea, thanks for sharing. When working on new projects, a lot of my learning comes from studying what others have already built so I can reuse patterns around architecture, UX, and product decisions. Those learnings tend to be transferable across tech stacks, so they’re not tightly bound to a specific programming language. Could you share the thinking behind using programming language as the primary way to organize or distill these examples?
The main reason is that most real blockers are tied to a specific language ecosystem. Even if the high-level ideas transfer across languages, the actual fix usually depends on the language’s APIs, tooling, and conventions. When someone is searching, they typically need something that fits the environment they are working in at the moment.
So the language choice in GitHits mainly steers the system toward code that is immediately usable.
Another part of the story is that finding patterns across languages is a much harder problem. It requires a level of semantic, cross-language search that does not really exist yet in a reliable way. I would love to reach that point, but today the best results come from staying within one ecosystem at a time.
Under the hood, there are several search modes, and not all of them are strictly language specific. The language selection guides the search, but it does not fully constrain it. And at some point, there might be a more generic search mode that is not tied to any single language at all, but that will take more research and iteration.
The MCP is great! Whenever I don’t like a solution, or my agent is stuck, I say use GitHits and it synthesizes a better solution based on real projects. I’ve had good results with frontend (html, css) and Golang, too.
Thanks! While those languages are not yet "officially" supported, GitHits works with them as well. The results might not be that good as with the ones I have enabled officially since the search and final output is partially steered by the selected language.
Really interesting idea, thanks for sharing. When working on new projects, a lot of my learning comes from studying what others have already built so I can reuse patterns around architecture, UX, and product decisions. Those learnings tend to be transferable across tech stacks, so they’re not tightly bound to a specific programming language. Could you share the thinking behind using programming language as the primary way to organize or distill these examples?
The main reason is that most real blockers are tied to a specific language ecosystem. Even if the high-level ideas transfer across languages, the actual fix usually depends on the language’s APIs, tooling, and conventions. When someone is searching, they typically need something that fits the environment they are working in at the moment.
So the language choice in GitHits mainly steers the system toward code that is immediately usable.
Another part of the story is that finding patterns across languages is a much harder problem. It requires a level of semantic, cross-language search that does not really exist yet in a reliable way. I would love to reach that point, but today the best results come from staying within one ecosystem at a time.
Under the hood, there are several search modes, and not all of them are strictly language specific. The language selection guides the search, but it does not fully constrain it. And at some point, there might be a more generic search mode that is not tied to any single language at all, but that will take more research and iteration.
The MCP is great! Whenever I don’t like a solution, or my agent is stuck, I say use GitHits and it synthesizes a better solution based on real projects. I’ve had good results with frontend (html, css) and Golang, too.
Thanks! While those languages are not yet "officially" supported, GitHits works with them as well. The results might not be that good as with the ones I have enabled officially since the search and final output is partially steered by the selected language.