News for hackers. Stuff that matters.
Re:GitHub cuts AI deals with Google, Anthropic by Yodel0914 on Tuesday October 29, 2024 @06:51PM (#41990245)
I find chatgpt incredibly useful for writing scripts against well-known APIs, or for a "better stackoverflow". Things like "how do I use a cursor in sql" or "in a devops yaml pipeline, I want to trigger another pipeline. How do I do that?".

But working on our actual codebase with copilot in the IDE (Rider, in my case) is a net negative. It usually does OK when it's suggesting the completion of a single line, but when it decides to generate a whole block it invariably misunderstands the point of the code. I could imagine that getting better if I wrote more descriptive method names or comments, but the killer for me is that it just makes up methods and method signatures, even for objects that are part of publicly documented frameworks/APIs.

Re:GitHub cuts AI deals with Google, Anthropic by jmpeax on Tuesday October 29, 2024 @07:16PM (#41990431)
Same here. If you need to lookup how to do something in an api I find it much faster to use chatgpt than to try to search through the janky official docs or in some github examples folder. Chatgpt is basically documentation search 2.0.
Re:GitHub cuts AI deals with Google, Anthropic by deepfriedbits on Tuesday October 29, 2024 @10:44PM (#41991495)
I love your framing of it as a "better stackoverflow." That's so true. However, I feel like some of our complaints about accuracy and hidden bugs are temporary pain (12-36) months before the tools truly become mind-blowing productivity multipliers.
Re:GitHub cuts AI deals with Google, Anthropic by DeathArrow on Wednesday October 30, 2024 @03:52AM (#41992716)
>"better stackoverflow"

I had asked hard questions on SO that only a human with experience can answer. And I found answers on SO that only a human with experience can answer.

Re:GitHub cuts AI deals with Google, Anthropic by vultour on Wednesday October 30, 2024 @08:20AM (#41994054)
The problem with this is that you lose the entire context around the answer you're given. There might be notes about limitations or edge cases in the documentation or on StackOverflow. I already see this with my coworkers who use LLMs, they often have no idea how or why things work and then they're absolutely perplexed when something goes wrong.