Are Googlers themselves happy using Gemini coding agent instead of Claude Code or Codex? (no snark, I'm really asking)
I for one can't tell the difference between Claude and Gemini for coding. And the internal agent tooling is many times faster than Claude Code in my experience.
AlphaEvolve: Gemini-powered coding agent scaling impact across fields
141–150 of 159 posts
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#142Earlier quoted context omitted.
I for one can't tell the difference between Claude and Gemini for coding. And the internal agent tooling is many times faster than Claude Code in my experience.
Lie? Gemini CLI is unuseable. The IF of gemini models is atrocious. Honestly, how often does your gemini CLI go insane in thought loops and you have to stop it?
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#143Are Googlers themselves happy using Gemini coding agent instead of Claude Code or Codex? (no snark, I'm really asking)
Yes. The models are good, the models are fast , and the internal tooling has caught up at this point too. There's a lot of UI/UX/tooling stuff that's still being worked through, integrations with VCS, and solving deeper problems that I probably can't talk about, but I'd say the frustrations of most are about the rate of change much more than the actual abilities. One thing that's interesting is a bunch of internal th…
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#144Earlier quoted context omitted.
No, for clients we use paid Vertex AI accounts. We often need to host workloads in an EU region, which rules out “global” models (and probably better capacity). In the past, we used a wrapper that round-robined across multiple projects to get enough quota. Luckily, many of our workloads are workflow-style tasks, so we can simply keep retrying on 429s. Fun fact: for one of their services, I think it was Stitch, I noti…
I've been seeing the same in my product; 429s in vertex. We generally avoid any Google AI for the most part because it's so unreliable.
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#145The AI CEOs love to pontificate about AI curing cancer, but it seems like DeepMind is the only one actively working on these research problems, while OpenAI/Anthropic largely chase enterprise/coding revenue.
Google can self fund from their war chest while OpenAI and Anthropic are hat in hand.
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#146Earlier quoted context omitted.
The past few years has seen a great rise in casuals reminding us of AIs limitations only to be proven wrong in 6 months. I don't think we're close to AGI, but in 2 years I've gone from AI doubter to AI convert. It's not perfect, but I don't need it to be. The real question to me is if the system can pay for itself. Economics are racing against efficiency gains and it's anyone's guess which wins.
what are those limitations we're talking about? seems most of those the original limitations that people complained about were resolved through workarounds like tools and skills which are more software-engineering than llm advancement.
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#147This reminds me of Antirez's "Don't fall into the anti-AI hype" [0] In a sentence: These foundation models are really good at optimizing these extremely high level, extremely well defined problem spaces (ie multiply matrices faster). In Antirez's case, it's "make Redis faster". There have been two reactions: "Oh it would never work for me" and "I have seen months of my life accomplished in an hour", and I think they'…
sounds like jobs involving legalese, politics, corruption and more generally involving pretending you don't understand something for which your income depends on not openly understanding something...
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#148Earlier quoted context omitted.
He was entirely correct. He made a follow up after the pushback by GDM. Google’s businesses are very broad and durable. But Google being the only company in the world without access (except for GDM+labs) to a competent coding agent will take a toll. We’ll see how long Google can hold out hoping for GDM to create something that is competitive. I’m guess that within 6 months Google will give up on coding and finally le…
> But Google being the only company in the world without access (except for GDM+labs) to a competent coding agent will take a toll. I doubt it. I use Gemini CLI daily because Gemini is what work pays for, and I have a personal Claude account. The difference is not that great, especially if you're not doing full vibe-coding. It's unlikely to have the kind of effect you're describing.
Gemini will conduct seconds to minutes of work before requesting aid. And it will commonly fall over.
Claude/Codex will commonly do minutes to hours of work.
The difference is one to two orders of magnitude. It is immense.
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#149Earlier quoted context omitted.
> Models are starting to get good at ambiguity That's fair, and something I've observed too. I wish I had written "the rest of us shouldn't freak out and quit software today". But here's another data point: At the biotech I work for, writing good code has never been the bottleneck. I actually told my boss that a paid Claude vs free subscription wouldn't be that much value because even if it took every piece of code o…
Ok, but you job is clearly not a good sample for a "job most mortals work on".
Re: AlphaEvolve: Gemini-powered coding agent scaling impact across fields
#150Are Googlers themselves happy using Gemini coding agent instead of Claude Code or Codex? (no snark, I'm really asking)
My experience running Gemma 4 locally has been similar: after maybe one or two tool calls it starts making tool calls however it feels like. Just yesterday, I watched it redefine a tool like read_file(start, end) into read_file(start, number_of_bytes) and it refused to even consider that it was wrong.