AI in software engineering at Google: Progress and the path ahead
1–10 of 245 posts
Re: AI in software engineering at Google: Progress and the path ahead
#2From the blog post:
> We observe that with AI-based suggestions, the code author increasingly becomes a reviewer, and it is important to find a balance between the cost of review and added value. We typically address the tradeoff with acceptance rate targets.
In the past year since GPT-4 came out, I've also found this to be the case. I'm an ML/backend engineer with little experience in frontend development. Yet, I've been able to generate React UIs and Python UIs with GPT-4 in a matter of minutes and simply review the code to understand how it works. I find this to be very useful!
Re: AI in software engineering at Google: Progress and the path ahead
#3The most interesting chart is the "fraction of code created with AI assistance via code completion" trending up to 50%
Re: AI in software engineering at Google: Progress and the path ahead
#4The most interesting chart is the "fraction of code created with AI assistance via code completion" trending up to 50%
Yes. Although I’d like to see a deeper investigation. Of course, quality of completions have improved. But there could be a confounding phenomenon where newer folks might just be accepting a lot of suggestions without scrutiny.
Re: AI in software engineering at Google: Progress and the path ahead
#5If there's anything in this press release to justify how "characters added by AI" is more true a reflection of quality than commit count is of productivity, I didn't see it.
It's a short release and I read it twice, so if it was there I feel like I'd have noticed.
Re: AI in software engineering at Google: Progress and the path ahead
#6From the blog post: > We observe that with AI-based suggestions, the code author increasingly becomes a reviewer, and it is important to find a balance between the cost of review and added value. We typically address the tradeoff with acceptance rate targets. In the past year since GPT-4 came out, I've also found this to be the case. I'm an ML/backend engineer with little experience in frontend development. Yet, I've…
This isn't a good trend. Reviewers never have the depth of knowledge or understanding of authors.
Re: AI in software engineering at Google: Progress and the path ahead
#7Anyone who works at Google knows they are force feeding the employees with this stuff.
Same thing they’re doing with the general public and search.
Anyone who worked at google during + can see this is the same half hearted type of force feeding that will fail, with the rationalizations to boot.
Disclaimer: I hold google stock but don’t work at google
Re: AI in software engineering at Google: Progress and the path ahead
#8Anyone who works at Google knows they are force feeding the employees with this stuff. Same thing they’re doing with the general public and search. Anyone who worked at google during + can see this is the same half hearted type of force feeding that will fail, with the rationalizations to boot. Disclaimer: I hold google stock but don’t work at google
[deleted]
Re: AI in software engineering at Google: Progress and the path ahead
#9If there's anything in this press release to justify how "characters added by AI" is more true a reflection of quality than commit count is of productivity, I didn't see it. It's a short release and I read it twice, so if it was there I feel like I'd have noticed.
[deleted]
Re: AI in software engineering at Google: Progress and the path ahead
#10Path ahead is to test you stuff before releasing