u/minkyuthebuilder

Google has the best infra and talent, but internal politics is straight up killing their AI ecosystem.

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.

  1. 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.

  1. 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.

reddit.com
u/minkyuthebuilder — 2 days ago
▲ 12 r/AIcodingProfessionals+1 crossposts

Google has the best infra and talent, but internal politics is straight up killing their AI ecosystem.

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.

reddit.com
u/minkyuthebuilder — 2 days ago
▲ 0 r/DeepSeek+1 crossposts

Silicon Valley veterans (30 yrs combined exp) share the REAL reasons average office workers will get left behind in the AI era

Hey guys, I was chatting with a friend of mine who is an engineer at NVIDIA (between the two of us, we have about 30 years of experience in Silicon Valley), and we hit on some pretty harsh but real insights I wanted to share here.

TL;DR: When it comes to actually using AI, a humanities major and a top-tier Silicon Valley developer are at the exact same starting line. The deciding factor moving forward isn't deep technical knowledge—it's mindset and execution.

Here are the 3 real threats we see for average employees in the AI era, and how to actually survive them.

🚨 3 Reasons Office Workers Are in Danger

1. The corporate environment itself is a massive roadblock

  • Security & Red Tape: Companies often block the most powerful AI tools on company networks out of fear of data leaks.
  • Conservative Systems: The bigger the company, the more terrified they are of adopting disruptive AI that completely flips their existing workflow upside down.
  • Makers vs. Users: This is the core issue. Just because someone is a top-tier engineer building AI doesn't mean they know how to practically use it in their daily work. It's like how a master bicycle builder isn't necessarily a pro cyclist.

2. The classic 9-to-5 "Complacency"

  • Honestly, getting a stable paycheck every month just for doing what you're told completely kills the motivation to learn new things.
  • Who has the desperate urge to study AI when they're dead tired after work? Let's be real, our true enemy isn't AI—it's Netflix (and dopamine). lol.

3. The "It's too technical" excuse and zero execution

  • People from non-tech backgrounds often psych themselves out and don't even try, assuming it's all coding and math.
  • A lot of people just buy an AI course on Udemy, feel a false sense of security like "I'm preparing for the future," and then never actually watch it. (I know some of you are feeling called out right now).
  • What you actually need isn't hardcore technical study. It's the absolute time investment of just playing around with AI to see how it can automate your daily grunt work and annoyances.

💡 So how do we survive? (The 4 core skills you actually need)

Even SV veterans are sitting in cafes after work or on weekends, teaching themselves and testing things out. Technical understanding takes a back seat to these four things:

  1. A Proactive Mindset: When you hit a wall at work, instead of saying "Oh well, nothing I can do" or passing the buck, your first thought should be, "How can I hack this with AI?"
  2. Creativity: The ability to twist the same problem from different angles and ask the right questions (prompting).
  3. A "Positive Bet" Mindset: The firm belief that messing around and struggling with AI for 1-2 hours a day right now will eventually yield massive leverage later.
  4. Execution (★ The Most Important): You can have the other three, but if you don't actually type into the prompt box yourself, you're at zero. You just have to get your hands dirty.

So tonight, before you fire up Netflix, maybe open up ChatGPT or Claude and mess around to see how you can cut down your workload for tomorrow.

How are you guys prepping for the AI era? Let me know your thoughts in the comments!

reddit.com
u/minkyuthebuilder — 5 days ago

They just pushed the DeepSeek-V4-Pro discount to May 31st. Honestly, this perfectly sums up why locking into a long-term commitment with any AI company right now is a terrible idea.

A few thoughts on this endless price war:

  • By the time this "sale" actually ends on May 31, some other company is going to release a significantly better model for even cheaper.
  • Once that happens, DeepSeek will just drop V5 (or whatever) and slap another "unprecedented 75% off" sale on it to stay relevant.
  • Anyone paying for a year up front in this ecosystem is just setting their money on fire.
  • The pace is so ridiculous that you can literally go out for lunch, and by the time you sit back at your desk, a competitor has undercut the entire market again.
  • At this rate of burning cash to undercut each other, it's going to be an absolute bloodbath. Give it a bit, and we'll only have a handful of these AI companies left standing.

Is anyone actually buying into long-term commitments right now, or are we all just surfing the discounts?

reddit.com
u/minkyuthebuilder — 22 days ago
▲ 3 r/kimi+3 crossposts

The core problem I was solving: 6 AIs need to review the same answer simultaneously, but each API has different response times, rate limits, and error behaviors. If one fails, the others shouldn't block.

What I ended up with: Promise.allSettled() across all active AI calls, with per-AI timeout handling and a fallback so a slow or failed API doesn't stall the whole review.

The app is called AI Council. One AI drafts an answer, the other five critique it in parallel from assigned roles (logic audit, fact-check, adversarial critic, etc.), then the primary rewrites with all the feedback incorporated.

v1.0.8 also adds Telegram integration — the desktop app long-polls Telegram's API locally, so you can send a question from your phone and get the cross-verified answer back. No server, no cloud.

Free, open source, Windows + Mac. → https://github.com/MinkyuTheBuilder/ai-council

Happy to dig into any of the implementation details.

u/minkyuthebuilder — 20 days ago
▲ 215 r/OpenAI

Seeing some wild rumors circulating today that DeepSeek and Kimi—arguably the two most dominant open-source AI labs in China right now—are preparing to merge.

If this turns out to be true, it’s a massive wake-up call. China is just executing their standard playbook for when an industry becomes a strategic national priority. We saw them do exactly this in 2015 when they merged CNR and CSR into the world’s largest train maker overnight. They did the same thing with steel, telecom, and nuclear power.

Their strategy is brutal but effective: don't let your best labs waste compute and talent competing with each other. Combine them into one state-backed juggernaut and aim it at the rest of the world.

The contrast with the US landscape is pretty jarring right now. OpenAI is suing Elon, Elon is suing OpenAI. Google and Anthropic are aggressively poaching each other's talent. We are burning billions of dollars and engineering hours just fighting internally before anyone even looks East.

Ironically, the US chip sanctions were supposed to slow them down. Instead, it seems like the lack of compute just forced them to stop fragmenting their top talent and start pooling their resources.

If they combine DeepSeek's efficiency with Kimi's massive context windows, how much of a threat is this to OpenAI's current moat?

reddit.com
u/minkyuthebuilder — 23 days ago
▲ 1 r/SaaS

Anthropic is gatekeeping this new version called MYTHOS because they say it's too dangerous for the public. They gave it to 40 groups to play with first.

Usually this feels like a marketing hype train to make the product sound cooler than it's. But if it's really that good at finding zero-days,, why are we trusting one company to decide who gets the keys???

Is this for real a security risk or just "safety" branding to justify a higher enterprise price tag?

reddit.com
u/minkyuthebuilder — 23 days ago

I was chatting with a dev friend recently, and they said something that hasn't left my mind: "All this stuff being built right now with 'vibe coding' is going to blow up in our faces down the line. It’s going to be an absolute dumpster fire."

I couldn't help but nod in agreement.

Even with the side projects I'm testing out right now, which are basically just simple landing pages or basic MVPs... honestly? The thought of actually scaling this AI-generated code or adding complex features is completely daunting. It feels like building a house of cards.

When you look at the flood of AI coding courses and tutorials out there right now, 99% of them focus on the flashy stuff: video, interactions, UI design, and basic frontend coding.

I don't think I've seen a single one that actually covers security, scalable server backends, or how to maintain an AI-generated codebase.

Are we all just building unmaintainable spaghetti code? How are you guys approaching architecture and security when using AI to build your projects? I'd love to hear how you're handling this.

reddit.com
u/minkyuthebuilder — 24 days ago