I know, the reason I shared that example is because there is no humanizing the LLM and it’s used exclusively for its ability to pretty effectively parse syntax to find common higher level bugs in specific C frameworks.
For context:
I never use LLMs when programming because I find them to be more of a hassle. They show me down and muddy the water on design principles.
Even a “bad” design pattern that you’re consistent with is 1000x better than a “good” design pattern that is inconsistently applied. LLMs are fantastic at the later. Things that look great in isolation, but begin to fall apart when they come up against the weight of a larger project.
Especially when it’s a new project without a ton of existing code for it to kinda copy/paste.
Using one to find minor use after frees that are almost impossible to hit, or duplicated calls is fine by me though. Those are usually a pain to find anyways, and there’s almost always 100 more important things to spend time on. If someone wants to burn tokens creating a backlog of easily fixed, reproducible errors like that all while disclosing exactly what they’re using to find them sure. That’s not annoying at all, especially when they only open the PRs after discussion with the project maintainers.
I know, the reason I shared that example is because there is no humanizing the LLM and it’s used exclusively for its ability to pretty effectively parse syntax to find common higher level bugs in specific C frameworks.
For context: I never use LLMs when programming because I find them to be more of a hassle. They show me down and muddy the water on design principles.
Even a “bad” design pattern that you’re consistent with is 1000x better than a “good” design pattern that is inconsistently applied. LLMs are fantastic at the later. Things that look great in isolation, but begin to fall apart when they come up against the weight of a larger project.
Especially when it’s a new project without a ton of existing code for it to kinda copy/paste.
Using one to find minor use after frees that are almost impossible to hit, or duplicated calls is fine by me though. Those are usually a pain to find anyways, and there’s almost always 100 more important things to spend time on. If someone wants to burn tokens creating a backlog of easily fixed, reproducible errors like that all while disclosing exactly what they’re using to find them sure. That’s not annoying at all, especially when they only open the PRs after discussion with the project maintainers.