Google's Gemini delay: Coding stumbles, clashing teams and frustrated engineers

Discussion (5 Comments)Read Original on HackerNews

gnabgib•about 11 hours ago

Bloomberg (28 points, 2 days ago, 5 comments) https://news.ycombinator.com/item?id=48938111

Reuters (7+5 points, 2 days ago, +2 comments) https://news.ycombinator.com/item?id=48938835 https://news.ycombinator.com/item?id=48958489

CNBC (7 points, 2 days ago) https://news.ycombinator.com/item?id=48941902

9to5goog (2 points) https://news.ycombinator.com/item?id=48944680

mgh2•about 6 hours ago

https://archive.ph/5R0Hv

pingou•about 9 hours ago

"Early in the rollout of the technology, employees also faced restrictions on using Gemini to write or analyze software over concerns that proprietary code could leak into the AI model’s training data, they said"

Wait, what?

Grimblewald•about 8 hours ago

right? alarming to me since if they have clearly scoped and working "dont train my this data" flags, this shouldnt be a concern at all. If they're concerned, we should _all_ be concerned about any google ai product.

watwut•about 4 hours ago

Well, yes. And the same issue exists for OpenAI and the rest. They have no motivation to make this work right, no audit, nothing. It is all pinky promis in situation with adverse motivations.

Google's Gemini delay: Coding stumbles, clashing teams and frustrated engineers

⚡ Community Insights

Discussion (5 Comments)Read Original on HackerNews