4 ms·
Digging through source was also helpful to me (I still do it quite a bit) GitHub code search was for a time quite useful, especially for somewhat arcane configu
by nyarlathotep_ 2y ago
Digging through source was also helpful to me (I still do it quite a bit) GitHub code search was for a time quite useful, especially for somewhat arcane configuration (over the years, stuff like Cloudformation properties that aren't frequently used, cmake stuff, webpack and others come to mind)
Often grepping through a codebase where I know another example resides of something similar with a vague idea of what i'm looking for helps.
- HappMacDonald 2y agoMan.. there are times when trying to debug some error yields no search results and no leads to follow other than "dig through megabytes of the arcane source code with no context of how it's meant to fit together" and if it were possible to have an LLM be able to RAG an entire git repo online and answer questions about it, that would be pretty choice. I've had basically zero luck with RAG myself so far, especially as I always try to go the local route for better infosec vs relying on cloud solutions like copilot. But trying to tap an LLM to help grok a public github repo wouldn't cover any sensitive data so I wouldn't mind using the cloud for a task like that.
- Aperocky 2y agoThat still works today, LLM tend to almost always hallucinate when you ask it for source details despite it being trained on it. Especially if the behavior is strange enough that trigger the look into the source.
- nyarlathotep_ 2y agoExactly, I never use LLMs for looking up the specific CFN properties for that exact reason. Populating a resource in a template sure, but the code-spelunking is always done to find the arcane property/value for said property.