Google has the same AI adoption curve as John Deere

Fans gasp, skeptics scoff: did hiring freezes make Google mid

TLDR: A viral post claims Google’s AI use is average due to a hiring freeze and reliance on its own tools, not rivals. Commenters fire back, calling it smug and oversimplified, asking why internal experts can’t train peers, and noting Google already shipped a Claude-like tool—proof this fight matters for who wins the AI race.

A spicy post says Google’s AI habits look like a tractor company’s: about 20% power users, 20% refusers, and everyone else poking at chat tools. The author blames an 18‑month hiring freeze and the company’s inability to use rival tools like Claude Code, claiming Google’s own Gemini never captured coder workflows. Cue the Great Siloing drama—and the comments went nuclear.

Top heat: one user slapped on an “AI bias disclaimer” for the author, calling the whole thing fandom disguised as facts. Another called it a “very smug post,” while a confused chorus asked: if 1 in 5 Googlers are AI power users, why can’t they teach the rest? The biggest counterpunch: a commenter pointed out Google basically built a Claude Code clone and shipped it—so how is Big G lagging behind John Deere?

The thread turned into a meme machine: “tractor vs spaceship” jokes, La Brea Tar Pits throwbacks (“just climb out!”), and the “we turned on Copilot like SOC2” dunk became the day’s catchphrase. Some cheered bold moves elsewhere—like a company canceling IntelliJ for 1,000 engineers—as the kind of wild bets Google won’t make. Others argued the post is just a plausible-sounding story for a messy reality. Verdict from the crowd: dramatic claim, thin receipts, great popcorn.

Key Points

  • A Google tech director reportedly says Google’s AI adoption matches a common 20/60/20 pattern: 20% agentic power users, 60% chat-tool users, 20% refusers.
  • The article attributes Google’s limited agentic adoption to an 18+ month industry hiring freeze and internal tool constraints.
  • Claude Code is reportedly discouraged at Google, while Gemini is described as insufficient to anchor developer workflows.
  • The author claims conversations with dozens of companies show wide variance: some have near-zero AI adoption; a few are aggressively adopting.
  • One unnamed company reportedly canceled IntelliJ for about 1,000 engineers to push agentic AI workflows; many others conflate tool enablement (e.g., Copilot/Cursor) with true adoption.

Hottest takes

AI bias disclaimer now — code51
Can’t they teach the others? — pingou
wrote the equivalent to Claude Code — stanfordkid
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.