2 ms·
That's funny, there isn't any mandate for using LLMs at my company. Everybody has just quietly added them to their workflows without being told. LLMs are like
by noident 1y ago
That's funny, there isn't any mandate for using LLMs at my company. Everybody has just quietly added them to their workflows without being told.
LLMs are like chainsaws. In the right hands, they can help you do the same job faster. In the wrong hands, it could cut off a limb. If someone drops a thousand line PR of total slop, it's not an AI failure, it's a human failure.
Personally, I use LLMs for fill-in-the-middle jobs and boosting test coverage. It's a modest benefit, but I am definitely shipping higher quality software in a shorter period of time compared to before.
They're not bad as starting points for learning new things, either. I've learned a number of new frameworks and libraries by using LLMs as a "better Google". Now I'm using it to learn Rust.
As long as you use your knowledge and experience to evaluate the output, LLMs can only help. I would posit that people committing garbage from LLMs will have no problem writing insecure and buggy code without assistance.
I caveat all this with the totally valid security and privacy concerns around sending code and data to 3rd parties that haven't been vetted rigorously. That said, local LLMs solve that problem handily and are good enough most of the time.
- tfandango 1y agoI think that's a good analogy. We use on-prem co-pilot and it works pretty good. I find it more useful exploring problems or debugging than I do at using it to make code.