Skipped yesterday’s post because I had virtually zero time to read thanks to Google Cloud Next activities. Watch the keynote replay and tell me what you think!
[blog] Day 2 at Google Cloud Next: A marathon developer keynote. This is a super recap of our unique developer keynote yesterday where we stayed with one theme for all the technical demos.
[repo] Race Condition. That gorgeous marathon planning system we showed off on stage yesterday? Yup, we open sourced all of it. Have fun!
[article] Cognitive debt: The hidden risk in AI-driven software development. What is cognitive debt, where does it impact you, and how can you mitigate it? This article goes fairly deep.
[blog] DeepSeek-V4: a million-token context that agents can actually use. Another impressive model family from the DeepSeek team. More here.
[blog] Introducing Gemini Enterprise Agent Platform, powering the next wave of agents. Major advances in multiple directions here. Check out this post for a flyover view.
[article] Google’s Gemma 4 shines on local systems – both big and small. Here’s an assessment of our latest open models and if they perform as advertised.
[article] The modern data stack was built for humans asking questions. Google just rebuilt its for agents taking action. Openness is a differentiator for us, along with our view of semantic context.
[blog] The future of data lakehouse: Open and interoperable for the agentic era. On the topic of openness, here’s more on where we’re taking the lakehouse.
[blog] Introducing the Google Cloud Knowledge Catalog. Does a “universal context engine” sound interesting to you? It does to me.
[article] The Pulse: ‘Tokenmaxxing’ as a weird new trend. You want to gamify token usage, go ahead. It’s great for Google’s revenue. But I wouldn’t suggest it. Focus on desired outcomes, not weak proxy metrics.
[blog] Next-gen FinOps for the AI era. Speaking of cost controls, I’m happy that Spend Caps are coming to services in Google Cloud.
[article] Google splits its TPU line in two for the agentic era. We don’t always share the same opinions as other vendors, and here’s a case of divergence from AWS.
Want to get this update sent to you every day? Subscribe to my RSS feed or subscribe via email below:
Richard Seroter's Architecture Musings 
Leave a comment