r/AIcodingProfessionals

I’ve been following Theo’s (t3.gg) recent breakdown on Google’s current state, and honestly, he hit the nail on the head. His TL;DR summary pretty much sums it up: "Google has the infrastructure, the talent, and the ecosystem, but internal politics ensures they never actually finish anything."
If you look at what's happening right now, Google's AI strategy is crumbling from the inside due to three major red flags:

1. The Gemini 3.5 Flash Pricing Trap
   On paper, the benchmarks look insane. It's supposed to rival GPT-5.5 and Opus 47 on Terminal Bench and SWB Pro, pushing around 300 tokens/sec.
   But look closer at the launch details. They completely hid the dollar signs. The actual price? $9 per million output tokens. That’s 3x more expensive than Flash 3 and over 20x more than Gemini 2.0 Flash.
   To make it worse, its token efficiency is absolute garbage. In the exact same benchmark where GPT-5.5 Medium uses 22 million tokens, Gemini 3.5 Flash burns through 72-73 million tokens. That’s a 3.3x inflation. As the saying goes: "If it’s twice as fast but uses 4x more tokens, it’s actually twice as slow." Plus, in actual coding tests, it was the only model that couldn't even output working code, while GPT-5.5 spat out a fully functioning 3D version on the first try.

2. The Anti-gravity CLI Open Source Betrayal
   The original Gemini CLI was a beloved open-source project with 100K GitHub stars and 6,000 merged PRs. The original devs (Dmitri, Jack, and Gal) built massive trust with the community.
   Then Google acquired the Windsurf founders, handed them the reins, and immediately replaced the original trio. They rebranded it to "Anti-gravity CLI," locked it behind a closed-source wall, and announced that starting June 18th, it's exclusive to Google AI Pro/Ultra subscribers.
   The new CLI is a buggy mess—no scrolling, exposed emails, Ctrl+C broken, and forced re-logins every single run. Even their official promo video accidentally showed a folder named “Codeex,” proving they're just lazily trying to copycat Cursor. The community trust Dmitri and his team built over a year of direct DMs and feedback just vanished overnight because of a corporate reshuffle.

3. Google Cloud is Unreliable (The Railway Shutdown)
   Railway spends over $2M a month on GCP. Guess what Google did? They nuked Railway’s account without warning, throwing railway.app and all its hosted services offline.
   This is UniSuper all over again. Remember when Google Cloud "accidentally" deleted a $135B Australian pension fund’s entire account? If UniSuper didn’t have external backups, they would've been wiped out.

The contrast with competitors is stark. Azure might be clunky, but if you page them, they answer. AWS is #1 for a reason. Google Cloud’s lack of reliability at this scale is just baffling.

The Moat is Evaporating
This isn’t just typical vendor bashing. Google literally has everything—the best infra, top-tier research, TPUs, and a massive ecosystem. But their internal politics are murdering the product.
Trust is built person-by-person and destroyed by a single corporate reorg. Last month, people were complaining about Claude Code's billing routing, but Google just pulled a trifecta: hiding prices, betraying open source, and nuking a major customer’s cloud account.

A lot of people still blindly believe Google will win the AI race because they have the most resources. But tech history shows that more resources don't guarantee a win when your internal culture is rotted.
If you are currently building anything critical on top of Google’s ecosystem, get out. You can't trust them.

So I have been recently coding a bunch with the following setup:

I am launching Claude Code CLI inside of my repo
(a complete shopify theme; if you are unfamiliar it is 3-8mb of source code, structurally something like this:

layout/ 2–3 files (theme.liquid = root shell)
templates/ 15–25 files (one per page type, JSON or liquid)
sections/ 30–50 files (reusable page blocks)
snippets/ 20–40 files (sub-components, like partials)
assets/ 30–60 files (css, js, svgs)
locales/ 5–10 files (i18n JSON)
config/ 2 files (settings_schema.json = theme editor config)

)

I also have an app set up that shows, what the current usage of the models context windows is currently at in %.

Recently I have been wondering: say I give claude quite a heavy task that involves the typical stack of 3 files (1 .js, 1 .liquid and 1 .css) and this instantly bumps up the context window from 0% to 10%, is there a golden rule that one should always do /clear after such an extensive task or does it depend if say, the next task depends on the same 3 files?

Do you guys have any advice on when the perfect time is to /clear? What are your experiences with this? Do you know of any addons that could facilitate this decision making to get the most out of ones usage?