Re:AI in software engineering at Google: Progress and the pa...
by runlevel1 on Friday June 07, 2024 @02:31AM
(#40605860)
That comment was solely about AI code suggestions.
Generative AI still has a ways to go for other forms of research, and it will never fully replace the utility of a search engine. They're two different tools for different but overlapping tasks.
Re:AI in software engineering at Google: Progress and the pa...
by mrslave on Friday June 07, 2024 @03:58AM
(#40606338)
Just to be charitable to GP and not to enter the debate, many of my colleagues have replaced Google with ChatGPT as their first port of call.
Re:AI in software engineering at Google: Progress and the pa...
by darby_nine on Friday June 07, 2024 @09:40PM
(#40614622)
> That comment was solely about AI code suggestions.
Even AI code suggestions seem to be only a minor improvement over basic LSP integration. One major exception is tedious formatting of the text—say you want to copy over a table by hand to a domain value, copilot is really good at recognizing values and situating them appropriately in the parent l-value.
If chatbots could serve as my RAM, surely they'd be able to generate code relevant to the rest of the codebase or at the very least not require deep scrutiny to ensure their RAM matches mine (it most often does not).
I have no idea how I could even integrate AI into my workflow so that it's useful. It's even less reliable than search is for basic research and can't even cite its sources....
This argument held a lot more weight when it was a search engine playing the role of our memory.