300: The Next Chapter: How Google’s Next-Level Next Event Nexted All Our Next Expectations – and What’s Next Now That Next Is Past

WEBVTT
1
00:00:00.000 --> 00:00:06.000
Foreign.
2
00:00:06.000 --> 00:00:14.000
Welcome to the Cloud Pod, where the forecast is always cloudy. We talk weekly about all things aws, GCP and Azure.
3
00:00:14.000 --> 00:00:18.000
We are your hosts, Justin, Jonathan, Ryan and Matthew.
4
00:00:18.000 --> 00:00:31.000
Episode 300 recorded for April 15, 2025 the Next Chapter How Google's next level Next event nexted all our next expectations and what's next now that next is passed? Yes. I nailed it.
5
00:00:31.000 --> 00:00:32.000
First try.
6
00:00:32.000 --> 00:00:33.000
First try.
7
00:00:33.000 --> 00:00:34.000
Bravo.
8
00:00:34.000 --> 00:00:57.000
I was not sure I could pull it off, but I'm very pleased about it. So, yeah, there we are. We're back. Back from Vegas. My liver has recovered, my sleep schedule has not. Ryan was there. Although if you went to either of my keynotes, he did not make it to either one of them, which I was not. I'm not surprised about, to be honest. I promised the listeners he'd be there and he did not deliver because he was hungover.
9
00:00:57.000 --> 00:00:58.000
It's Ryan.
10
00:00:57.000 --> 00:01:19.000
It's Ryan. It's fine. It's just what we expect. But I was there at both of my talks. That went great. I thought. I did meet a couple listeners who came up and got stickers, so that was great. Good to meet them. And they can write all their complaints to ryan@thecloudpod.net about him not being at the conference. He will gladly ignore all those emails just like he does his work emails.
11
00:01:19.000 --> 00:01:22.000
I was like, does he even have this set up anywhere?
12
00:01:22.000 --> 00:01:25.000
He does. He does have ryan@thecloudpod.net set up. Yeah.
13
00:01:25.000 --> 00:01:28.000
But is it connected to his phone or anywhere he has a potential.
14
00:01:28.000 --> 00:01:34.000
Oh, no. I think it forwards to his real email address because he doesn't log into his CloudPod address ever.
15
00:01:34.000 --> 00:01:36.000
Facts. These are all just facts.
16
00:01:36.000 --> 00:01:41.000
Yeah, we love you, Brian. We just accept these things.
17
00:01:41.000 --> 00:01:44.000
Yeah.
18
00:01:44.000 --> 00:02:12.000
Well, it was a very busy week. There was some stuff that came out before next, so we'll touch on some of those real quickly here and then we can get into the meat of this week's episode. This is not going to have any AWS or Azure news this week. We will save all that for next week. This is officially our 300th episode, which we're very excited about, but to do it truly justice, we need to wait till next week when we're not just coming off of Google Next. So we will Talk all about 300 episodes next week and how it's going, et cetera.
19
00:02:12.000 --> 00:02:13.000
I think it fits well with the Cloud pod.
20
00:02:13.000 --> 00:02:14.000
Right?
21
00:02:14.000 --> 00:02:15.000
We're going to be late.
22
00:02:15.000 --> 00:02:18.000
Yeah. Always the way it is.
23
00:02:18.000 --> 00:02:23.000
Just like the cloud providers. We'll talk about stuff that's going to be released in the next Year.
24
00:02:23.000 --> 00:02:26.000
Yeah, exactly.
25
00:02:26.000 --> 00:02:30.000
Now in preview episode 300.
26
00:02:30.000 --> 00:03:05.000
All right, well, first, before next Google shook up their Gemini leadership team, making the Google Lab head take over all of the Gemini work. This is an effort to continually streamline their AI presence. The DeepMind CEO Demis Hassebas is basically doing this to sharpen their focus on the next evolution of the Gemini app. There's a lot of Gemini news at next. We'll talk about here in a minute. But they're basically trying to get even more focused than they already been focusing. This has been a slow collapsing of multiple AI efforts into one cohesive team and really turning AI into a platform team, which it should be. So makes sense to me that they're doing that.
27
00:03:05.000 --> 00:03:14.000
They didn't really get that as like a combination or like, you know, this is more like a firing, I think.
28
00:03:14.000 --> 00:03:23.000
Like, I mean, you could maybe say that I was trying to be kinder, you know, help the guy out his next job, but, you know, it could be a termination, you know, that's, that's fair.
29
00:03:23.000 --> 00:04:12.000
Well, I mean, it's so, it's interesting because going through the article, a lot of the, you know, the, the new head of AI, which I'm forgetting, the new head of Gemini. There we go. Has, you know, contributed to a lot of the, the major Google AI announcements that have come out recently. And you know, the, the, the outgoing leader, you know, was part of the Bard, you know, debacle. And, and I don't know if it was, you know, obviously don't work for Google. So. Yeah, I don't, you know if there was any other things, but there wasn't the way the article was written, there wasn't a whole lot of other announcements by his out who's outgoing. So, you know.
30
00:04:12.000 --> 00:04:49.000
Yeah, I mean, it's not, it seems to be in rogue. Sorry. In favor this week as Apple Intelligent also fired their head of, you know, the new Siri, which has been a disaster. So makes sense. You know, everyone's holding people accountable for not hitting their roadmaps, apparently. Well, in addition, the filestore instance replication was announced, which helps you meet your business continuity goals and regulatory requirements. Feature offers an efficient replication point objective RPO that can reach 30 minutes for data change rates of 100 megabytes per second, which probably just eliminated a bunch of databases that you would like to have used this tool for. But it's not a database. You now have an option.
31
00:04:49.000 --> 00:04:52.000
It's an impressive feed, 100Mbps with a.
32
00:04:52.000 --> 00:04:56.000
30 until you get to your database and then it's less.
33
00:04:56.000 --> 00:04:58.000
Well yeah, but this is for file share.
34
00:04:58.000 --> 00:04:59.000
True, true.
35
00:04:59.000 --> 00:05:07.000
And if you're running a file share on top of you're running your database on top of the file share, I feel like you're doing your job wrong. Just saying.
36
00:05:07.000 --> 00:05:43.000
Agreed. In a point killer for me, they introduced Multi Cluster Orchestrator to scale your kubernetes workloads across regions. It's announced the public preview of Multi Cluster Orchestrator, a new service designed to streamline and simplify the management overloads across kubernetes clusters. Multicluster Orchestrator lets platform and application teams optimize resource utilization, enhance application resilience and accelerate innovation in complex multi cluster environments. You get intelligent resource optimization, enhanced application resilience and tighter integration with existing tools like Argo, cd, et cetera, which is a nice improvement. Probably wouldn't have taken a point for this just to be honest because it's not that close to what I said but I would have tried.
37
00:05:43.000 --> 00:05:49.000
I actually was trying to remember what you said that was multi clustered and I was like wait, this doesn't really fit.
38
00:05:49.000 --> 00:05:51.000
Well, this wasn't on the keynote, right?
39
00:05:51.000 --> 00:05:56.000
This is a no, this is all pre invent. That's why pre next. There's no, no point for it any regardless.
40
00:05:56.000 --> 00:05:57.000
But I think yeah, it would have.
41
00:05:57.000 --> 00:06:09.000
Counted if it would have been close. I don't know. As I said, unification of major enhancement of Anthos and GKE Enterprise isn't quite that. I would try to argue it for you though. But yeah, and you guys would have rejected my point.
42
00:06:09.000 --> 00:06:14.000
I would have argued against it then if you had gotten the point. But now that you didn't get the point, I think you should have got it.
43
00:06:14.000 --> 00:06:38.000
Yeah, but it wasn't at the keynote so no chance whatsoever for the sadists out there. You can now run 65,000 node clusters up from 15,000 nodes which I think we said you were status last time. This can also include your TPU based clusters for Google's Kubernetes engine. If you need massive massive Kubernetes scale, you can now do that on GKE and I look forward to seeing your therapy bills.
44
00:06:38.000 --> 00:06:41.000
I just want to know what customer requested this.
45
00:06:41.000 --> 00:06:45.000
So this isn't 65,000 nodes in a single cluster.
46
00:06:45.000 --> 00:06:49.000
This is even if it's not in the single cluster, it's too many nodes.
47
00:06:49.000 --> 00:07:30.000
Oh 100%. I was going through the multi cluster orchestrator announcer going why? Oh my God. Because even that I'm like I don't know if we really want to start bridging all these Things, but there's probably enhancements to be had and it looks like they were addressing some of my concerns in that announcement with the regional sort of deployment of applications. So we'll see. But I mean, this seems to go against a lot of things that I've been saying for a while, which is like, you know, consolidate your workloads, manage these things with smaller little pods and distributing globally has very limited return for the amount of operational overhead. If you're at 65,000 nodes. Yeah, I don't even know.
48
00:07:30.000 --> 00:07:40.000
So is it 65,000 nodes per project, per organization? I thought this was my cluster. Maybe I'm wrong.
49
00:07:40.000 --> 00:07:56.000
Oh, it is. It can support a 65,000 node cluster, up from 15,000. So it is a single cluster. Why? No.
50
00:07:56.000 --> 00:07:58.000
Now he's mad.
51
00:07:58.000 --> 00:07:59.000
I am mad.
52
00:07:59.000 --> 00:08:04.000
He went from like, I'm okay with this too. I'm now really mad that you're doing this.
53
00:08:04.000 --> 00:08:05.000
Well, I mean it just enables.
54
00:08:05.000 --> 00:08:12.000
Yeah. If only there was video on this podcast. People have enjoyed that moment of realization on your face that I just saw.
55
00:08:12.000 --> 00:08:14.000
That was fantastic.
56
00:08:14.000 --> 00:08:39.000
I mean in the article there's a lot of like other interesting facts that they work through, like you know, pouring images, pod startup, you know, and like kind of all the other pieces of it. When you have something at this larger scale, which is interesting, but like you're writing something at 65,000 notes, I really want to just go launch In a region 65,000 average just to see what Google does. Also, as long as it's here, is there enough capacity?
57
00:08:39.000 --> 00:08:40.000
Let's start with that.
58
00:08:40.000 --> 00:08:42.000
Well, you're. First of all, you need to make sure you have enough credit.
59
00:08:42.000 --> 00:08:43.000
Right.
60
00:08:43.000 --> 00:08:50.000
Except one, you have to go quotas. Yeah. Then you gotta get the quota big enough and then you can try to make Google pay attention to you.
61
00:08:50.000 --> 00:08:53.000
Yeah, at that point we'll definitely hit a stock outage at that point.
62
00:08:53.000 --> 00:09:25.000
Yeah. Well, if you're. Maybe they're trying to run all these robots on Gemini nodes, GKE nodes, perhaps. The DeepMind team released all a bunch of updates on their new Family of Gemini 2.0 models designed specifically for robots. And now if you are worried about the end times of Terminator, is a good time to read these articles and understand the weaknesses of your robotic companions if you ever need to take them out. I don't really care that much about that, but I think it's cool. They're using AI solve a lot of big problems.
63
00:09:25.000 --> 00:09:29.000
I mean I didn't read the article, but I assume it's like go for the eyes.
64
00:09:29.000 --> 00:09:36.000
I assume so. Go for the sensors. That's what I would recommend. Don't assume they're in the eyes. That's the trick. You got to know where the sensors are.
65
00:09:36.000 --> 00:09:37.000
Yeah.
66
00:09:37.000 --> 00:10:44.000
All right, that gets us through pre next and things get interesting. So first of all, this conference, they decided for some reason that they would run it from Tuesday until Friday. Technically Wednesday through Friday for most people. If you're an executive or you're going to a GCE event or any other of these like long day workshop days, those are all on Tuesday, which meant really weird traffic patterns. So everybody shows up on Tuesday afternoon and then they all leave Thursday night or Friday morning, it doesn't matter. You put the conference till 3 o'clock on Friday, they're going to go. Just how it's going to work. So I don't exactly know why Google decided to do that. I don't actually care for it. I thought I would. When they first announced it and I realized it, I was like, well, that might be nice actually. And then now I've done it, I can tell you I don't like it. Tuesday through Thursday is the epitome of a week long conference. That way you can travel there on Monday and you can travel home on Friday. That's how it should be. I'll debate you on it all day long. But I think that's the right schedule and I'm going to stick to it and I will put it in my feedback to Google when they send out the surveys for the event.
67
00:10:44.000 --> 00:10:49.000
Wait, so AWS is Tuesday, Monday is all day.
68
00:10:49.000 --> 00:10:50.000
Well, Monday, Monday is kind of.
69
00:10:50.000 --> 00:10:51.000
There's Monday Night Live.
70
00:10:51.000 --> 00:10:53.000
Monday Night Live is the beginning of the conference.
71
00:10:53.000 --> 00:10:55.000
No, there's Sunday night. Sunday.
72
00:10:55.000 --> 00:11:00.000
Well, no, no, no, no. Quiet with your partner. Nonsense. No, no, no, no.
73
00:11:00.000 --> 00:11:05.000
It wasn't partners. There was like the like wing eating contest. That was at midnight on Sunday.
74
00:11:05.000 --> 00:11:07.000
No, that was. That's like Monday night or Tuesday night.
75
00:11:07.000 --> 00:11:08.000
Oh, it's on Monday night.
76
00:11:08.000 --> 00:11:09.000
Yeah.
77
00:11:09.000 --> 00:11:13.000
Well, I know on Monday we did like the hackathons and other things.
78
00:11:13.000 --> 00:11:56.000
I mean, it's been a while since I've been to re invent, but I'm not going to fight you on this as hard, but December 1st, December 1st technically was Sunday in 2020. Oh, this is 2025. This is the stream. All right, hold on, wait, sorry. December 1st, we use calendars. Monday Night Live is. Monday is the game of the conference for Amazon, in my opinion. And Monday during the day, you may have partner things, you may have an executive thing, you may have security things, you may have A training, certification thing. They have all that on Monday, which is typical. And then basically, like, Friday, they have, like a bunch of rerun sessions for people who really wanted to get into one that was really full on Tuesday, Wednesday, Thursday, no one goes to the Friday sessions. I've done one one time. I was like, this is laughably silly.
79
00:11:56.000 --> 00:12:02.000
I mean, I agree with you. I like the Amazon. I'm just trying to live up the show.
80
00:12:02.000 --> 00:12:11.000
Sometimes. Playing the active part of Contrarian is Matt. Do we know he's playing Contrarian? No, we don't, but we assume he's not, and then we get mad at him, and that's how that goes down.
81
00:12:11.000 --> 00:12:15.000
Can you adopt a British accent? It'd be really easier if we to tell it apart.
82
00:12:15.000 --> 00:12:17.000
We can definitely tell you being more Contrarian if you're British.
83
00:12:17.000 --> 00:12:18.000
For sure.
84
00:12:18.000 --> 00:12:22.000
I'm not even going to try one. I was thinking about it. I don't think you could do it.
85
00:12:22.000 --> 00:12:39.000
So now let's go back to conference. So Tuesday, if you are a special invited person, you got to go to the Sphere. And I don't know who exactly got invites. I got an invite to it because I was part of the executive groups that were there. Executive talk track. My finops guy was there. I don't know how he got there.
86
00:12:39.000 --> 00:12:46.000
I had an invite, but no one told me. So it was just languishing away in my inbox and it went unnoticed. I was really upset about that. Yeah.
87
00:12:46.000 --> 00:12:48.000
See the beginning part of this podcast about reading your email.
88
00:12:48.000 --> 00:13:12.000
Yeah, yeah. So anyways, for those of you who were, you know, who got this invite, basically they said, come to the Sphere for some mystery event. Now, secretly I was hoping it was the Eagles, just because Ryan loves the Eagles and they do have a residency at Sphere right now. And I thought that'd be kind of fun if Google had a surprise private concert of the Eagles, and if I could get Ryan there, it'd be even better.
89
00:13:12.000 --> 00:13:16.000
Oh, the headlines like, oh, would have been bad. I would have gotten arrested.
90
00:13:16.000 --> 00:17:48.000
Yeah, it would have been bad, but it wasn't that. So I arrived. Yeah, they said to get there at some time, which I don't recall, but my Uber driver took forever to get there. He was very mad at the traffic. He was like, what's going on? I don't understand why all this traffic's here. And we're like, it's a Google thing. And he's like, is it the concert? And I'm like, I don't know what it is. We don't know what it is. We're just showing up at the Sphere. And so I walked in like maybe 15 minutes after it's supposed to start. I got my free soda, I got my popcorn, I sat down and it's just an endless sky in black and white. And I instantly knew we were talking about wizard of Oz. Now, if you haven't paying attention to anything in the media sphere, the week before, there was an announcement that came out from the Sphere that I saw and ignored 100% because I did not care. And that announcement was that the original 1939 classic wizard of Oz movie was going to be presented at the Sphere. And at the time that was announced, I said, oh, okay, cool. It's a movie theater, really. And if you've been to the Sphere, you should have known that Justin didn't control the dots his head at the time. Because the reality is you can't take a movie that's a 4, 3 aspect ratio and put it on a screen that's 16,000 K in resolution. It's not going to work because that's a really big screen. I mean, it's massive. I mean, you literally feel like you're in other places when they do screen stuff on the screen. And so when I walked in, other than I was in black and white, it was in color. I would have thought I was in Nebraska or Kansas or wherever this movie is filmed at in a field of corn with a windmill in the background. So this is pretty impressive already that, you know, they have this big screen and they have wind effects. So as this tornado which, you know is coming, is approaching, and the storm, you know, basically it starts at night and then comes into daytime before it starts. And there's lightning and thunder and you tell there's a storm coming. But that was basically just kind of like. Well, that's just 3D generated AI stuff. It's kind of cool. But then they get into the technical details, what they actually have to do to make the 1939 World wizard of Oz movie work in this projection. And they have to basically create the entire movie all over again, but with AI. And so they partnered with Google's DeepMind to basically create, with VO2, which is their video AI system, basically create this version of wizard of the Oz, which they took all of the source article, all the source material from Warner Brothers, all the, you know, the National Emmy, whatever, whatever. I think Oscar foundation had a bunch of archive footage of it, all the movie, all the cut room, you know, all the stuff on the cutting room floor. They scanned all of that into an AI model. And they basically built out a brand new AI model. And so when you typically will see this movie, they will have upscaled the characters because again, they're filmed in 1939 technology at 4, 3 ratio. So it has to be upscaled to this size. And then they're also adding people into film that did not exist. That film does not exist in any way, shape or form. So there's a scene very early in the movie where one of their. One of the characters comes from off screen, which we consciously know that he's off screen in the movie because he walks into frame and he puts his arm and hand on the shoulder of one of the characters and he comes into frame that way. So they had to basically recreate this actor digitally, give him all the personality traits, the way he walks in the movie, his gait, etc. And then have him literally be standing in the frame before that happens and then walk in and do what he does in the movie. And they had to do this for the entire movie. There's a close up of Dorothy. Well, guess what? If she's dancing in this close up, she's also dancing in real life. But they don't have the footage of lower below her stomach. So they have to basically digitally create her legs and the ruby red slippers on her feet and show her dancing in the scene that was filmed back basically 100 years ago. Amazingly impressive use of AI. I was blown away. And they showed us two scenes of the movie. They didn't show us the whole thing. They showed us over the rainbow, Dorothy singing over the rainbow in the black and white section. And then they showed us the scene where they meet the wizard in the wizard of Oz or in Emerald City. And both were cool. A little uncanny valley. I will say again, it's not going to be out officially until August, so there's a lot of work to be done. They're very busy. They talked about it in the video they presented and they had a whole like, you know, walking you through all this stuff that I hope it put onto YouTube at some point so you can see the technologies, technology involved in making this movie. Or maybe they'll air it before they show the movie so people can really, truly appreciate this thing. It's a technical marvel that I am very excited to go see now in August. And a week ago I would have been like, yeah, yeah, whatever. Wizard of Oz, don't care. And that was a special sneak preview. And then, you know, Sundar kicked it off in that. And then TK at the very End of it. Welcomed us all to next and said, have a great week. That was the beginning of the conference.
91
00:17:48.000 --> 00:17:52.000
And I was already exhausted.
92
00:17:52.000 --> 00:18:04.000
Well, I did drag you to the weekend before when actually we took you out partying all weekend because it was my birthday. And so we celebrated my birthday in style. We had a great time. But we made Ryan and I very tired before the conference even started.
93
00:18:04.000 --> 00:18:08.000
And you dragged me to the compute all day session as well.
94
00:18:08.000 --> 00:18:11.000
I did drag you to that too. It's because you're gonna sit around doing nothing. What are you gonna do?
95
00:18:11.000 --> 00:18:12.000
It's true.
96
00:18:11.000 --> 00:18:13.000
Recover.
97
00:18:13.000 --> 00:18:14.000
Yeah.
98
00:18:13.000 --> 00:18:21.000
Recovery is when you come home, man. Once you're in Vegas, you're in Vegas. You got to do it all. Only one thing can take down Ryan. That happens later.
99
00:18:21.000 --> 00:18:23.000
Yeah.
100
00:18:23.000 --> 00:18:49.000
All right. So that is the beginning of the conference. That is not as. Not as nerdy as. I mean, pretty nerdy. I mean, I think just as nerdy as Monday Night Live, but much more focused. So I don't know how they'll top that next year. Maybe they're converting other movies. But then I was thinking about all the movies. I want to see them convert to the. To the sphere format. Like, I would love to see Jurassic park in this format because a 30 story tall T. Rex running at me sounds awesome with like the wind effect.
101
00:18:49.000 --> 00:18:50.000
Of it running by you and everything else.
102
00:18:50.000 --> 00:19:22.000
Yeah, yeah. Like there's all kinds of cool movies that would be awesome in this format. So I assume this is a success, that we'll see other movies. There are some other things I heard later on through my people. Like, you know, one of the challenges is cuts in that size of the screen make you disorientated. So they do a lot more panning and a lot more digital effects to move you between scenes because it's too jarring. It'll make you not feel good. So lots of things you learn about how the sphere has to be designed and thought through for some of these types of things, but definitely be cool to check out.
103
00:19:22.000 --> 00:19:32.000
It's pretty wild. I mean, it's. Yeah, you'd start talking about some of those things where they have to literally change the way they show you things because of how unique that medium is. Blows my mind.
104
00:19:32.000 --> 00:20:10.000
Yeah. Well, I mean, right now there's only one of these screens in the entire world, and then there is one being built in Dubai, I think is what I heard. And so there's only a few opportunities. Actually, the movie from the thing is available, so you can see it. I will post that in our show notes. The little 30 minute video they showed us of the making of how they're doing it. And it's a partnership between Warner Brothers, the Sphere, some studio I'm apparently neighbor, which is disrespectful to them because they're doing a great job on this. Oh, magna opus. And then Google Cloud to do all this work.
105
00:20:10.000 --> 00:20:17.000
It touches on some of the tech and stuff behind the Sphere as well. Like it was really. I watched it as well, all the way through and so like I like that a whole lot.
106
00:20:17.000 --> 00:20:28.000
Yeah, very, very cool. All right, enough about wizard of Oz because you guys want to talk about Cloud, I'm sure. All right, so getting into day one, keynote. Oops, sorry. Go ahead. Matt. You have something I was going to.
107
00:20:28.000 --> 00:20:31.000
Say we should name this show like off to See the Cloud off to the Next or something.
108
00:20:31.000 --> 00:20:37.000
Where were you at the show note title spot you. I was coming up with ridiculous puns on what we did last week because.
109
00:20:37.000 --> 00:20:39.000
We probably still would have selected that.
110
00:20:39.000 --> 00:24:08.000
Because it was so good nailed on the first take. Just want to point out once again, I'm still proud of myself. It's been however many minutes of recording we've done it, I'm still happy about that. All right, day one, Sundar comes out once again, drops the news that they announced something called Cloud wan. I was like, that's random. And then that they were supporting Metalama 4 and then basically handed it over to TK, who then went through a bunch of announcements with a bunch of guests on stage, including Ironwood. The first Google TPU for the ages of inference. Significant performance improvements over the previous inference chips. We'll talk about that in just a second. Google Workspaces added a ton of new AI tools, the Doc, sheets, chats and more Agent Spaces, which is basically Google's answer to whatever Q does at Amazon and ChatGPT Enterprise, etc. It lets you basically connect to all of your corporate enterprise Systems and use ChatGPT type interfaces to Gemini, of course, to access all those things. New video, image, speech and music generation. AI tools. We're coming to Vertex. We'll talk about those in a second. Hyper Computer updates for Google Cloud Next. So if you want really big expensive boxes, you can get them on Google Cloud Next, the new Agent Development Kit, which is an open source framework simplifying the process of building sophisticated multi agent systems while maintaining precise control over agent behavior. And it supports mcp. And then they created Agent to Agent, which is they say they're the first hyperscaler to create an open agent to agent protocol to help Enterprises support multi agent ecosystems so agents can communicate with each other regardless of the underlying framework or model. This is a combination of MCP plus these connectors through this protocol so agents can talk to each other without having to do special regardless of whatever AI built them to begin with. And then Google Unified Security which is a solution that brings their visibility threat detection, AI powered security operations, continuous virtual red teaming and the most trusted enterprise browser and mandiant in one converged security solution and like I said Metal on four so jumping back up to the Ironwood basically this thing can do when scaled to 9216 chips per pod it could do 42 and a half exaflops which they commented on stage was 24 times the size the world's the computer's world's largest supercomputer El Capitan which offers just 1.7 exaflops per pod. And this is all on a chip like crazy. Each individual chip boasts peak compute of 4614 TJ and is a monumental leap. They show peak performance of larger pocket figures for TPUs basically 1.350x to 3600x in the FP8 Peak Flops Performance Benchmark and they showed quite a few RAM enhancements including including 192 gigabytes of RAM and much more throughput. You get significant performance gains while also focusing on power efficiency allowing AI workloads to run more cost effectively. You get a substantial increase in high memory bandwidth and dramatically improved HBM bandwidth reaching 7.2 terabytes per chip and enhanced interchip interconnect bandwidth which is up to 1.2 terabits per second. So pretty large improvement. 14.6 fleet peak flops for watt was the Trillium CPU. This new Ironwood TPU is 29.3 and they like to poke that one a little bit because Trillium I believe is Amazon's if I correct and they're 5.2 was the V5P which is the fastest TPU before that. So Google is ready for the inference age they're saying basically with this new capability they also highlighted how it's helping Alpha AlphaFold do even more than ever before in their quest to get protein folding to the masses.
111
00:24:08.000 --> 00:24:48.000
So I was sort of surprised because they did spend a lot of time talking about inference and this chip handling inference concerns and I thought that was really I mean it's just not the way that we've been talking about these custom AI chips in the past. Right. It's definitely Been all about model training and building all these things and the inference is more about running these very large models. And so there did seem to be a huge focus on performance and end user experience with AI development all the way through the conference. So I thought it was really interesting. First time I thought of it anyway, of that.
112
00:24:48.000 --> 00:25:06.000
Yeah. Well, they did declare this is the year of inference. In their opinion, this is the year that big workloads are being delivered with AI agents with all kinds of different AI use cases and such, ability to do inference at scale and economically is going to become a big driver of compute. And so that was kind of why I think they went that direction this year.
113
00:25:06.000 --> 00:25:33.000
I mean, I think it also kind of makes sense, right? We have all these models, we have them all now. Yeah, they're going to keep growing, they're going to keep getting better. But at one point we got to leverage them, you know, and you know, we need to have the chips available to leverage them, you know, so it's just a matter of time until they need them. So like you said, this is Google saying we're ready, come actually use our platform for these things.
114
00:25:33.000 --> 00:26:54.000
Yeah. Well, the general availability of Google Agent Spaces, this product, it's the latest Google foundational models. Powerful agents and actionable enterprise knowledge in the hands of employees. Agent Space employees and agents can find information from across the organization, synthesize and understand Gemini's multimodal intelligence and act on it with agents. Lots of partners here, Wells Fargo, KPMG Cohesity, lots of SaaS vendors involved. But basically to do something with Agent Spaces you're going to basically say give employee access to agent space. Unified enterprise search analysis and synthesis capabilities allow you to discover and adopt agents to quickly and correlate data together, especially with agent to agent and deploy. Google's built in agents such as the new Deep research and idea generation agent to help employees generate and validate novel business ideas. Gives you a unified agent search directly from the search box in Chrome. So you can basically just say ask Agent Space and say something like summarize this financial statement and it'll do that for you. You can ask IT to query Jira, you can ask it to go query your SaaS applications, whatever system you want. It'll basically do that, provide you a very simple rundown of what it finds. It can also then create audio podcasts of that content, just like Alum Studio which is probably the predecessor to this. All available to you now in the enterprise grade system with enterprise grade data protection and security available to you. I'm hoping my day job adopts this because this looks really cool.
115
00:26:54.000 --> 00:27:04.000
Well, so this seems really cool until you get through the hard edges on this. This is something that I was looking into before.
116
00:27:04.000 --> 00:27:11.000
I don't know, I think it was early Access in December, GA did the conference. That's a good point.
117
00:27:11.000 --> 00:28:24.000
Well, even now it's still only allow list only. You have to sign up for it and give them special form. So it's, you know, like a lot of it really relies on your utilization of Chrome Enterprise Premium. And so that's a whole workspace ecosystem that if you're not bought into, like you've got a whole lot of heavy lifting to make that work. There's also, you know, a lot of these things. Like it's great to announce an AI agent that can ingest all the data in your enterprise, but the reality is, is that no enterprise is ready for that yet and no one is. I mean, they have figured out how to build like individual maps of access so that in an AI model can return results for only data you have access to. But it is not real likely that you have your data labeled correctly where it can be detected, who has access to what. And so like the controls on this are pretty minimal in terms of like there's PII data and financial data and patterns that they can recognize. But this would be really hard to implement in a way where you're not getting access to, you know, all the financial HR data, how everyone's made, you know, if, if launched without any care.
118
00:28:24.000 --> 00:28:30.000
Well, yeah, like all good tools, you need to be careful how you roll it out.
119
00:28:30.000 --> 00:28:34.000
It's just, it's a big lift to get those in there.
120
00:28:34.000 --> 00:28:50.000
I mean, this is one of the big problems we had originally with Amazon solution, you know, before Q, which I remember the name of it now because they deprecated it in Facebook favorite queues version. But that was one of the problems they had there too was how do you deal with the access model across all these tools and access layers, etc.
121
00:28:50.000 --> 00:29:12.000
And it's, you know, it's not an AI problem, it's a data problem. Right. That's the trick. And you know, if your data isn't labeled or tagged or organized in a way where you can deduce those things, a model isn't going to be able to understand that either. So it's, we're all going to have to go through our enterprise data and care for it, which is going to.
122
00:29:12.000 --> 00:29:19.000
Suc Age of data governance might be a lot right along with the age of data Inference.
123
00:29:19.000 --> 00:29:37.000
Yeah, it's going to happen where somebody just tells one of these tools to run their organization and it ends up spewing out a bunch of internal private information on the Internet. All of a sudden everyone's going to lock down all these systems real fast. So it's just a matter of that first company slipping up and it becoming public. I feel like.
124
00:29:37.000 --> 00:29:46.000
Yeah, I mean, I don't know if this is, you know, an internal tool. The whole thing is geared to be sort of, you know, for employee access.
125
00:29:46.000 --> 00:29:54.000
But you mess up permissions to your, you know, low level employee that gets access to their K1 before it gets.
126
00:29:54.000 --> 00:30:02.000
I would hope that the. All the model. Yeah, all the model and all the execution is completely separate from like any kind of production thing.
127
00:30:02.000 --> 00:30:12.000
What I didn't realize that was Google Chrome Enterprise had like a premium tier that wasn't just the normal like it's its own product line. I never realized that they've been building.
128
00:30:12.000 --> 00:30:52.000
That up and they've been tying a lot of functionality and features into it, especially security tooling where I'm at this point like just resisting because I'm angry about it, because I don't really want to dictate which browser people use for accessing workloads. But Google's sort of forcing it and I think they're going to run into antitrust issues just like Microsoft did back in the day. And I think this is all about to come crumbling down in a bad way because there's features of different access patterns for X and Google Cloud and all these things that you only get if you're managing your browsers using Chrome Enterprise Premium.
129
00:30:52.000 --> 00:31:10.000
Well, Paul, also, I think also released their own web browser for DLP protection, which is like one of the big ones I see here. DLP URL filtering, malware protection, like I think Palo Alto recently released their own product to kind of do the same type of thing.
130
00:31:10.000 --> 00:31:12.000
That's very interesting.
131
00:31:12.000 --> 00:31:13.000
Their own browser.
132
00:31:13.000 --> 00:31:18.000
I thought so. I thought it was like their own browser. Palo Alto, I mean, I'm sure it's.
133
00:31:18.000 --> 00:31:23.000
Yeah, yeah, I think it is their own browser. It's based on Chromium of course, but I assume so.
134
00:31:23.000 --> 00:31:26.000
I assume everything is based on currently. I am at this point.
135
00:31:26.000 --> 00:31:27.000
I think so, yeah.
136
00:31:27.000 --> 00:31:30.000
I think even Firefox has these days. I think so.
137
00:31:30.000 --> 00:31:33.000
Isn't IE now too? Or Edges?
138
00:31:33.000 --> 00:31:34.000
Edge, yeah.
139
00:31:34.000 --> 00:31:36.000
Not the same thing. IE and Edge are different.
140
00:31:36.000 --> 00:31:38.000
Yeah.
141
00:31:38.000 --> 00:31:59.000
All right, well, let's talk about AI. So they have a new video, image, speech and music, generative AI tools. The first one, Lyria which is Google's text to music model is now available in private pre with allow list on vertex AI. This means customers can generate complete production assets starting with a text prompt which like they even did the demo of this in the keynote and I was like, I don't, I don't understand.
142
00:31:59.000 --> 00:32:18.000
Yeah, I always have a hard time with this because it's like music is an art form and it's like if you want, you know, to generate some pretty milk dose music out there that isn't very unique. Yeah, this is your tool.
143
00:32:18.000 --> 00:32:24.000
But they all start sounding like the same, you know, electronica keyboard, you know, with the automatic beat track in the back.
144
00:32:24.000 --> 00:32:47.000
Yeah, well, I mean they're doing a much better job these days with once like, you know, when it was still like the, you know, back in the day with the. What was the AWS music instrument thing. Yeah, but so they're using real instrument sounds and they're the other. So it doesn't really sound all like one type of sound, but it's still sort of like, you know, I don't care what prompt you put in there, it's not going to come up with anything. It's like there's moves.
145
00:32:47.000 --> 00:32:51.000
You all right now? Challenge accepted.
146
00:32:51.000 --> 00:32:52.000
Yeah.
147
00:32:51.000 --> 00:33:46.000
Get to work. VO2 has new editing and camera controls available in preview that allow enterprise customers to refine and repurpose video content with precision. So pretty cool stuff. Like they showed a demo of, you know, person is in this spot in a frame and then another frame later he's in a different position and then it'll basically fill all the frames between those two positions automatically, which is kind of cool. Or they showed, you know, they built, you know, you put a GNX car into a video and they said we want to do a pan shot of it with it doing a donut and basically it generated all of that with a panning camera shot, which is pretty neat. After the wizard of Oz thing, I definitely can play with VO2. I'm curious what can I do with this thing? Chirp 3, which is about to replace Jonathan because it can create instant custom voices with a new 10 second of audio input. So only needs 10 seconds of Jonathan to be able to give us new Jonathan.
148
00:33:46.000 --> 00:33:56.000
Yeah, that's what our listeners don't know. He's not taking some time off from the cloud potty. We're uploading his consciousness into the machine.
149
00:33:56.000 --> 00:34:01.000
That's why there's a lack of AI capacity out in the world right now, because it's all going to Jonathan's brain.
150
00:34:01.000 --> 00:34:03.000
Do you guys Ever watch the show upload?
151
00:34:03.000 --> 00:34:05.000
Yes, of course.
152
00:34:05.000 --> 00:34:09.000
I can't think of what you said. Uploading is bright.
153
00:34:09.000 --> 00:34:17.000
What's that? There's another one too with the stacks. What's that one? That's a Netflix show, but it was a book before that they uploaded.
154
00:34:17.000 --> 00:34:19.000
Oh, Altered Carbon.
155
00:34:19.000 --> 00:34:20.000
Yes, Altered Carbon. That's a good one too.
156
00:34:20.000 --> 00:34:21.000
I haven't seen that.
157
00:34:21.000 --> 00:34:23.000
And the book is fantastic.
158
00:34:23.000 --> 00:34:45.000
The book is so much better than the TV show. Like the TV show's fine, but the book is really, really good. And then finally, the last AI tool is Imagen 3 has improved image generation and inpainting capabilities for reconstructing missing or damaged portions of an image and making object removal edits even higher quality, making it easier for you to hide all those pesky rigs that are holding people in the air in superhero movies.
159
00:34:45.000 --> 00:35:26.000
Yeah, much like the music. Like. Well, I don't want to say that that way because I was pretty down on the music, but I, you know, these are neat little things for like video editing and processing. I do think it's going to bring a whole bunch of capabilities that people who aren't like expert drone pilots or you know, camera rig operators, you wouldn't have otherwise. So it is going to be interesting there. And you can even see the music applications for that too for background music behind the scene or, or you know, that kind of thing. But you know, it is kind of interesting to see how that's it is sort of going to take over and I think we're going to see, we're not going to even know that it's behind like a lot of movie development.
160
00:35:26.000 --> 00:35:42.000
You know, I mean it could also being good for like you know, hey, I have an old couple years, I converted all my family's like VHS to like digital, like even like taking some of those that were like damaged and like kind of filling in those in between gaps too, which would be really nice.
161
00:35:42.000 --> 00:35:44.000
Yeah.
162
00:35:44.000 --> 00:36:26.000
Then if you get into now the AI hypercomputer, this is an AI optimized hardware with their new 7th generation TPU powering it. Of course software advances for inference with their updated AI hyper computer software layer helping developers optimize computer compute resources as well as flexible consumption models from spot to committed usage, et cetera. As well as they also announced an inference gateway which is basically a fancy load balancer for inference to allow you to basically pass the query on to the right type of model. So you might have some queries that you would detect are very easy for a standard LLM to answer versus this one. Which requires more deep thinking or reasoning that one can be answered by different models. So you get best cost optimization in your models.
163
00:36:26.000 --> 00:36:44.000
So I read about that and I was trying to understand that a little bit more. Is it the load balancer does it? Or would you like a traditional load balancer, like a layer 7 load balancer? You know, you'd have to kind of route it based on URL or whatever you pass to it. Or would the load balancer kind of know where it wants to send that data to?
164
00:36:44.000 --> 00:37:02.000
So it's based on the prompt, right? So based on the incoming prompt it's going to be like oh the. There's basically a router agent right at the beginning that's going to look at the prompt and be like, you know, it's best and most efficient based off of this. I'm going to send this to the text bison thing because it's just summarize a blob of text versus creating an.
165
00:37:02.000 --> 00:37:04.000
Image with the load balancer.
166
00:37:04.000 --> 00:37:09.000
Okay. Or allowing you to input the configurations as part of the service.
167
00:37:09.000 --> 00:37:53.000
I should mention this runs on top of gke. It's a GKE inference gateway. It provides inference optimized load balancing based on load metrics, support for dense multi workload serving of LORA adapters and model aware routing for simplified operations. Look into all of that and basically it uses a bunch of calculations in the LORA capability as well as model serving criteria that you define based on certain known patterns that you're looking for to tell it which way to route the particular query. So it's not AI for AI, you got to know a little bit to make it work. But it's pretty nice if you're trying to do this on top of GKE. But maybe it's why you need 65,000 nodes.
168
00:37:53.000 --> 00:38:33.000
There are a lot of cloud cost management tools out there, but only Archera provides cloud commitment insurance. It sounds fancy, but it's really simple. Archera gives you the cost savings of a one or three year AWS savings plan with a commitment as short as 30 days. If you don't use all the cloud resources you've committed to, they will literally put the money back in your bank account to cover the difference. Other cost management tools may say they offer commitment insurance. But remember to ask will you actually give me my money back? Achero will click the link in the Show Notes to check them out on the AWS Marketplace.
169
00:38:33.000 --> 00:39:03.000
Agent Development Kit. This is a Python agent development kit. You can look at sample agents they built for you. Just check it. Look at they have A branch. They have a rag agent, customer service, data science, FOMC research, LLM auditor, personalized shopping helper, and a travel concierge. So you can take a look at the code they built for these. You can see how to build your potential agent in the future. It doesn't look too amazingly complicated, which is either terrifying to me or awesome.
170
00:39:03.000 --> 00:40:45.000
So I haven't quite done like Orion does a thing level, but I did look into this a whole lot in the last few days when I was not sleeping, because at the conference what dawned on me was what an agent actually is and how I could think of it in my mental sort of model of things. And if I think of an agent as like an AI function, then, and I need to, or sorry, not a function, but like a Python class, then I have the ability to now upgrade and manage that class as an individual part of my script and so I don't have to rewrite the entire thing. When you think about all the session state and context that you need to pass around, it becomes super important because now you're externalizing these things into separate little modules of things that you can now manage independently. Going through the development kit. It's really a framework and how you tie that all together. So it's, it's, it's exactly what it sounds like and it's saying in like, you know, just like this serverless framework or some other example that I'm not going to think of in enough time to be interesting. And so it, it, it's actually cool because it really helped me sort of understand a better way of sort of creating an interaction with an AI agent, in my case, you know, by, by simply, simply it out to its components and then giving a very deterministic way of putting it all together. It's kind of cool. And then the fact that they're using all this like kind of open source and unified, you know, protocols and context is like awesome.
171
00:40:45.000 --> 00:40:50.000
I feel like the MCV protocol is really that key to a lot of these things actually being able to.
172
00:40:50.000 --> 00:40:53.000
That's why everyone's rapidly adopting it for that exact reason. Very quickly.
173
00:40:53.000 --> 00:41:26.000
Yeah, I mean the best analogy I read was it's USB C for everything, you know, and it to me really was the first time I read it. But like Ryan was saying, like, I think I'm starting to understand more how to kind of piece meal stuff together to make it be more what I want than like, oh, cool, there's this thing over here, like using it in a particular place versus like, I'm starting To be able to take that step back and be like, okay, I want to achieve X and I can now leverage these things. Like I'm starting to understand what tools are in my tool belt.
174
00:41:26.000 --> 00:42:13.000
Yeah. And how to leverage things that aren't going to be within the model. Right. Like the example of the weather bot that they use. It's calling an API to get the current weather. Right. A model's only going to have data that's not up to date. It's going to only be able to give you a guess on what the current weather is based on patterns. But now with the, because of the framework separating out, at least in my head, you're defining the API call as a tool and you're telling the AI agent as part of your prompt to use tool. Get the results from tool. Answer my question. Like it's, it makes these things really easy to, to manage and you know, so this is the first time I was really able to see sort of a production grade app being possible with these things. So kind of cool.
175
00:42:13.000 --> 00:42:42.000
And it's, I think a long time ago we talked about how we, we were all learning how to write, you know, queries in Google years ago and you know, in order to have effective, you know, results, you know, you've kind of learned how to leverage that tool in that way. And I feel like this is kind of that next evolution of learning how to leverage AI and LLMs in that kind of a manner of, you know, of writing to their core competencies.
176
00:42:42.000 --> 00:43:02.000
Yeah, definitely. I mean for me it was the difference between like writing a Python script that was going and doing a thing and then writing a Python application with, with different classes and components different, maintained in different places. It's really cool and the documentation is spectacular. Probably because it's written by AI or.
177
00:43:02.000 --> 00:43:03.000
At least heavily edited by.
178
00:43:03.000 --> 00:43:11.000
Yeah, hope it gets the other way. Written by humans or written by AI edited by humans.
179
00:43:11.000 --> 00:43:13.000
Hopefully.
180
00:43:13.000 --> 00:45:36.000
The other part is the Agent to Agent which is basically a brand new Internet protocol that Google has created because of course they would. The open protocol called Agent to Agent will support and contribution from more than 50 technology partners like Alagia and Box, Cohere, Intuit, Linkchain, MangoDB and many, many more. I won't answer. Read all of them. Basically it's an open protocol with several design principles including embracing agent capabilities, building on existing standards including HTTP, sse, JSON, rpc, making it easier to integrate into your current IT stack. It's secure by default, it supports long running tasks and it has modality agnostic ness to IT So you can use it with any agent world A two way facilities Communicating A client agent and a remote agent A client agent is responsible for formulating and communicating tasks, while the remote agent is responsible for acting on those tasks in an attempt to provide the correct information or to take the correct action. This action involves several key capabilities including capability discovery Agents can advertise their capabilities using an agent card and JSON format contract, allowing the client agent to identify the best agent that can perform a task and leverage A2A communicate with the Remote Agent Task Management the communication between a client and a remote agent is orientated towards task completion in which agents work to fulfill end user requests. This task object is defined by the protocol and has a lifecycle. It can be completed immediately or for long running tasks. Each of the agents can create to stay in sync with each other or Malaysia status of completing a task and the output of the task is known as an artifact. Collaboration between the agents can send each other messages, communicate context, replies, artifacts or other user instructions. And there's a user experience negotiation which allows each message including parts, which is a formal form fully formed piece of content like a generated image. Each part has a specified content type allowing client and remote agents to negotiate the correct format needed explicitly included negotiations of the user's UI capabilities, for example iFrames, video, web forms and more. And so they basically had a real world example in the blog post around candidate sourcing. Basically they're hiring a software engineer who can significantly simplify with HOA collaboration within the unified interface like agent space, a user AKA the hiring manager and tasks are agent to find candidates matching a job listing location and skillset. The agent then interacts with other specialized agents to source potential candidates and the user receives these suggestions and can then direct the agent to schedule further interviews, streamline the candidate sourcing process and after the interview process completes, another agent can engage to facilitate background checks. Is just one example of how a agents can need to collaborate across systems to source a qualified job candidate.
181
00:45:36.000 --> 00:45:59.000
So it was right at the real world demo where I didn't understand what was going on anymore because I thought it was much more like, you know, a low level protocol. We're talking about how these agents literally like communicate. But then the the real world example is like every other AI agent demo you've ever seen. So I'm really confused.
182
00:45:59.000 --> 00:46:54.000
I think it's the ability to pass information from one to the next. So in their example go hire, you know, get me a people that meet the criteria. Cool. Ryan Lucus is one of them Pass Ryan's name directly to the next one. So it's kind of that, that scripting from level to level that, you know, the agents can, in passing, all you need to say is do a background check or Ryan Lucas and it will pull us information from the prior one, pull us name, date of birth, you know, and everything else that it has and immediately feed it into that other system from the, you know, HR recruiting system to the third party background check system. That's the way I kind of viewed it was like, now the agents are directly communicating and like passing the relevant pieces of information versus you having to say, okay, get me the JSON object that contains all Orion's information. Pull out these three pieces of the dictionary and pass it over to here.
183
00:46:54.000 --> 00:46:59.000
I mean, that's what I think it is too. It's just funny because the real world example was not that. Right?
184
00:46:59.000 --> 00:47:04.000
Yeah, I mean, I think you something simple that your brain would understand because.
185
00:47:04.000 --> 00:47:19.000
It'S like, how do you demo TCP handshake? It is that kind of level. It'd be interesting to see a little bit more details on this. And so I'll dive into the. Or I probably won't. Who am I kidding? No, I'm not. I'm going to use the tools that use this.
186
00:47:19.000 --> 00:47:24.000
I might, I might be playing with these. Cause I'm curious about some of my podcast workflow.
187
00:47:24.000 --> 00:47:27.000
I mean, I'll be playing around with like the tooling on top of it for sure.
188
00:47:27.000 --> 00:48:21.000
Yeah, I mean the ADK for sure I'm going to use. But then I, I think the agent to agent could be interesting because then I could, I could then leverage multiple models and agents to go do different parts of the task that I do when I write show notes. So. And have them edit each other and you know, work on different formats. I think it'd be cool. Yeah, add Jonathan's voice in because we need him now. Anyways, so that's it for day one. I didn't ask you guys what you thought of the keynote because I forgot to ask you in the beginning. So what do you think of the keynote in general, the vibe? I will tell you, I actually got into the arena this year the one time I tried last year, but it was full. I was turned away at the door. So I got up extra early and I was already tired, I was already cranky and I walked there and I got into the thing and I had a good seat and it was very uncomfortable and I will never go back. But it was cool to see it in person once.
189
00:48:21.000 --> 00:48:47.000
Yeah. Pass. I watched Keynote from my hotel room with room service, coffee in a Danish and it was fantastic. I love the ski note. I thought it went and I think there's you know, like time, place and manner I guess. I thought the pacing was good. I thought that the announcements were good. All the customer sort of interactions were video which I really enjoyed because those could be a little slow draw out.
190
00:48:47.000 --> 00:48:59.000
I heard someone else complain about that though. I was, I was blown away because they said I think it was strange they didn't have any customers on stage talking about what they do with it. It's all pre recorded and like if you didn't, if you squinted they could be talking about any cloud, not just Google.
191
00:48:59.000 --> 00:49:02.000
And I was like, I guess you can't win it.
192
00:49:02.000 --> 00:49:16.000
Sort of hear what you're saying. But you can't win on these things. Either you get a customer who goes way too long and puts you to sleep like at Re Invent or you get this, which was really tight 30 to 60 second clips. I much preferred them.
193
00:49:16.000 --> 00:49:21.000
I feel like I just fast forward through the, you know, partner talk the customers talking about them.
194
00:49:21.000 --> 00:49:25.000
That's what I do when I watch the recordings and from Re Invent it's like, yep, Skip.
195
00:49:25.000 --> 00:49:35.000
Yeah, absolutely. So, you know, I really liked it. I thought that the length was good and so. Yeah. But again for my hotel room comfort, I think it was in a robe.
196
00:49:35.000 --> 00:50:42.000
Yeah, my knee, my knee was very jealous of your bed because it was being jammed by the chair in front of me. Yeah, long legs and conference and arenas are never fun, but it is a nice space. I kind of like the open cavernous nature of it versus the, you know, we converted a conference center into a keynote. That's all one level. This is nice that has multiple levels. The production quality is quite nice too. Not as cool of, you know, lighting rigs that. I know you love Ryan, but yeah, you know, I was definitely the ins and you know, watching them come on and off the stage, the stage direction they were doing, it was, it's well put together, it's well paced. I didn't think it dragged on. I wish they were just like two extra bullets on each slide because I was looking at the photos I took of each announcement when I was going through doing show notes and I was like, it's just words like Ironwood and then Agent Space. I'm like, yeah, but what was that like? Unless you. So that's one area I would say they could do with maybe just a slight bit more content on the slides to kind of Anchor what it is. But yeah, there was definitely cool. They did have a sort of awkward moment where they tried to convince us that TK was a Chappelle Roan fan.
197
00:50:42.000 --> 00:50:43.000
That was a bit awkward.
198
00:50:43.000 --> 00:50:50.000
That was a bit awkward. But I'm glad TK is enough on the joke that he's. He's cool them kind of making fun of him on that.
199
00:50:50.000 --> 00:51:00.000
I think that's not a running theme necessarily, but I think that that kind of skit has been in every developer or not Developer. Every keynote I can remember for Google.
200
00:51:00.000 --> 00:51:35.000
Or all keynotes for Google. Yeah, those are kind of have a little bit of like, you know, because I think he's been on the last couple. He's very animated in his approach and so yeah, I think that's just something he does, you know, sort of like the Matthew woods, but more endearing than that Woods. All right, day two. This is my day. I did my session on the show floor. It was fun, had some people show up again. My talk about that went well. It was not recorded so we'll never know if you. Unless you were there, Ryan. So you will never know if it was good or bad.
201
00:51:35.000 --> 00:51:38.000
The I'll have to take your word for it.
202
00:51:38.000 --> 00:53:06.000
Yeah, there's not a lot of announcements in the developer conference, a lot of just expanding on what was talked about the day before. So they gave you a lot more examples of using the S SDKs, using the agent to agent. They did show and announce the Vertex AI Agent, which is a fully managed Google Cloud service enabling developers to deploy, manage and scale AI agents in production. Agent Engine handles the infrastructure to scale agents in production so you can focus on creating intelligent and impactful apps. It's fully managed, has quality and evaluation capabilities, has a simplified development process and it's framework agnostic allowing you to use Agent Development Kit, lane graph, LangChain, AG2 and Llama index all available for you. During that keynote there was also a bunch of other talks happening all over the place where they were doing smaller announcements including I Lost my Spot data analytics for Spark Serverless Spark Engine, the IDE enhancements for Gemini Code Assist. So lots of improvements there including ability Gemini Code Assist Troubleshooter to help you with your incidents. It'll actually look at your Google infrastructure and the logs it's producing and and your code and potentially make recommendations to you on things you can do to fix your application and get out of outage. A time series based foundational model, which is interesting. I don't really know why you need a specific model for time series Data, but they built one, so there's got to be a reason. And then several software engineering agents. All you talked about in that keynote or mentioned off stage, I look for one of the other rooms.
203
00:53:06.000 --> 00:53:37.000
I mean, I don't, I don't think there's so much troubleshooting incidents versus just troubleshooting development process. But, you know, it was pretty cool to see them sort of tie it all together. And you know, I was trying to struggle to understand what that time series model was all about. And then I remember they did mention like it's, it helps specifically for forecasting. So I think that that's. It understands your current time series data set and then can apply the time horizon, apply it for forecasting.
204
00:53:37.000 --> 00:53:38.000
That makes more sense.
205
00:53:38.000 --> 00:54:51.000
So like that took a while, this whole show for drag up in my brain, but because we were discussing it before we started recording, so that's one down. I still don't, I still don't know the details on what serverless Spark engine is. I assume that it's, you know, it's Spark jobs, so I assume it's just, you know, ways to query your larger data set quickly. Not sure, but the Gemini Code Assistant, the IDE is like, I love because this is a thing that me and Jonathan have sort of as we're integrating AI more into our development practice. Like they're addressing our problems that we were having, which is how do you coordinate different things? You want AI to write this and AI to write this, and then you have to tie it together. The human's gonna do that and how are you planning and coordinating all of that happening? And so they're their code assist improvements are. You know, there's literally like a Kanban board where you're, you're using your, your prompts for AI generation are happening directly within that Kanban board and it's breaking it up into tasks that can be tracked just much like, you know, any kind of Kanban issue through different stages and, and have the visualization there. So it's a really kind of neat way that they're building these things out. Yeah, I was pretty stoked by that one.
206
00:54:51.000 --> 00:56:33.000
That was pretty cool. Yeah, definitely. The Kanban board was a unique idea. I really enjoyed that as a concept, so I'll play with that one. They did add a code assist also to Android Studio. So if you're an Android developer, you get that now. They also have Gemini Codesys tools, which is in preview, which helps you access information from Google Apps and tools from partners including at Lesion, Sentry, Snyk, and more. The Gemini Cloud Assist, which is integrated with Application Design center, which basically helps you write infrastructure as code and accelerate application infrastructure design deployment. And then the Gemini Cloud Assist Investigations which leverages data in your cloud environment to accelerate troubleshooting of issues and resolution. As well as Google Cloud Assist is now integrated across Google Cloud service including Storage Insights, Cloud Observability, Firebase Database Center, Flow Analyzer, FinOps Hub, as well as security and compliance related services like sce, all in that product. So yeah, quite a bit of Cloud Assist stuff. And then we were talking about how previously Copilot was feeling a little dated. It's feeling real dated today, real dated after these came out. So I expect we're going to see something big coming from those guys very, very soon. Oh, one of the things we didn't talk about from the keynote, I just saw it as I was scrolling through the 229 announcements. Google distributed Cloud is basically making offer with Nvidia to bring Gemini to Nvidia Blackwell Systems on premise via Dell hardware. So you can basically run Google Distributed Cloud in your data center with Gemini running on that. So you can do locally air gapped and connected environments with Gemini, which is a pretty nice, that's kind of cool feature. It's the first cloud provider to provide that for you. It's also a great way to potentially get Nvidia chips that you maybe were struggling with before if they're helping you do that.
207
00:56:33.000 --> 00:56:35.000
So it's like an outpost for Gemini.
208
00:56:35.000 --> 00:56:57.000
Yeah, outpost for Gemini essentially or whatever Google calls theirs. Yeah. One of the other keynote things I saw that we didn't mention was customer Engagement Suite. Lots of enhancements for that product. If you care about it, you're excited. If you don't care about it, like my two co hosts, they don't care about it, which is fine. Scrolling through. See there's anything else we want to talk about. Anything you guys want to talk about. I didn't cover. I mean we covered a lot.
209
00:56:57.000 --> 00:57:06.000
Like already I'm realizing we didn't really go over Cloud WAN after the initial announcement too, but because I did deep dive into that to understand what that was.
210
00:57:06.000 --> 00:57:13.000
Cross Cloud network solution, a fully managed, reliable and secure enterprise backbone that makes global private network available to all Google Cloud customers.
211
00:57:13.000 --> 00:58:36.000
Cloud wan, which is why you have to do the deep dive because none of that is really helpful at all. And so it really is like a, it's a branding of a bunch of little things. And so they've really taken the sort of cloud interconnect model of like this is a specific tab in your dashboard where you're here's your cloud interconnect and you go off and you configure that out with the link that you sourced and provided. And now they're really taking that whole process and controlling all of it and making it software driven. So even down to provisioning the link. And so you can do cloud interconnects, you can do site interconnects, you can do all kinds of different things and you can do it on demand, you can scale up capacity on demand. It is kind of like I think they announced the announcement. It wasn't, didn't do it a service that's not the right way, let's say that. But like, because it is actually I think more neat than people realize. But other than the product people which all their videos look like they have a gun pointed at them behind camera, they look terrified and frozen. So I think it is a much bigger announcement than people realize yet. And I think it's going to change sort of the way that we're using, you know, multi cloud network setups. That's kind of pretty cool.
212
00:58:36.000 --> 00:58:44.000
Well, there's a couple things about it that I think are important to know. One is that you're getting access to basically Google's global network including all the fiber we love to talk about, which.
213
00:58:44.000 --> 00:59:00.000
In one of the articles they went, they deep dove into all the different like fibers and like how many miles of fiber that they manage and they run and, and all the stats were astounding. I tried to find it. Right now I can't seem to find it again. But it was a detailed list of everything.
214
00:59:00.000 --> 00:59:20.000
It was remarkably impressive including a 400 gigabyte cloud interconnect and cross cloud interconnect capabilities available later this year which was 4x more bandwidth than the current 100 gigabit cloud interconnects and cross cloud interconnects you had before. So yeah, you're getting massive throughput between cloud providers through this stuff which is pretty interesting and you could scale it.
215
00:59:20.000 --> 00:59:22.000
Down to 1 gigabit.
216
00:59:22.000 --> 00:59:26.000
But what do you need 400 for.
217
00:59:26.000 --> 00:59:30.000
AI models of course. Same reason you need anything right now.
218
00:59:30.000 --> 00:59:36.000
I need to move a lot of data out of Google into AWS into GCP so I can.
219
00:59:36.000 --> 00:59:41.000
That's how this became an AI announcement for move your AI data.
220
00:59:41.000 --> 00:59:57.000
Sorry, sorry guys. Yeah, well at least like 190 maybe chuckle a little bit because they didn't mention AI in any way possible, which I can't believe they didn't shove it in there which was Cloud City ends fast cache invalidation. Delivers static and content at global scale with improved performance. Now in preview I'm like oh thanks, that's nice.
221
00:59:57.000 --> 00:59:58.000
But.
222
00:59:58.000 --> 01:00:17.000
And then they also. I don't know, it was kind of funny to me that because. Mostly because I met with a VPC product manager and they didn't mention anything about this and I'm annoyed. You'll be able to use private Service Connects to publish multiple services within a single GK cluster, making them natively accessible from non peer GK clusters. Cloud Runner or Service Mesh. Thank you.
223
01:00:17.000 --> 01:00:19.000
Yeah, it's going to make my life so much easier.
224
01:00:19.000 --> 01:00:22.000
Like if he had just said that at the beginning of our meeting, we would have had a whole different meeting.
225
01:00:22.000 --> 01:00:24.000
It would have been a different meeting. I know.
226
01:00:24.000 --> 01:00:25.000
What is that?
227
01:00:25.000 --> 01:00:39.000
So Private Service Connect is like private endpoints, what do they call that on AWS where you connect manage their nats basically to your network so you don't have to use your IP space for managed services. PSC is based.
228
01:00:39.000 --> 01:00:42.000
Yeah, it's just like Private connector. Yeah, it's Private Link. Private Link.
229
01:00:42.000 --> 01:00:53.000
Private Link. Yeah, it's actually their version of Private Link. But instead of each product needing its own Private Link, you can now basically put a bunch of products into the same private Service Connect. Oh yeah.
230
01:00:53.000 --> 01:00:54.000
Oh.
231
01:00:54.000 --> 01:01:10.000
And so it's. And it's not only Google Services, it's your own services. You can put your own services behind a private Service Connect and hopefully this works in the same way for those services as well. Where I don't have to for every single internal application in every environment have to be develop my own private service.
232
01:01:10.000 --> 01:01:17.000
I have. There's a pay that I was dealing with at my day job all recently.
233
01:01:17.000 --> 01:01:23.000
They also. They're also adding layer 7 domain filtering finally to cloud next gen firewall coming.
234
01:01:23.000 --> 01:01:24.000
Later this year finally.
235
01:01:24.000 --> 01:02:02.000
And then Also inline network DLP for secure web proxy also finally powered by Symantec's DLP which Symantec as one of the best third party DLPs out there. So that's good. But yeah, lots of good stuff in security realm they had Google Unified Security or gus which we talked a little bit in the keynote thing. The alert triage agent. So you get agents for security folks as well. I saw a demo of this in a session video I was watching earlier today. Looked pretty nice. New phishing protection inside of Chrome Enterprise. I like the malware mandate retainer so you can pay them in advance. So when you get hacked you already have a retainer in place.
236
01:02:02.000 --> 01:02:04.000
Then malware analysis agent I thought was kind of cool.
237
01:02:04.000 --> 01:02:11.000
Yeah, the malware analysis agent was definitely neat. Or it basically will help you do all the investigation without having to log into the box directly.
238
01:02:11.000 --> 01:02:13.000
I missed that one. I'll have to go.
239
01:02:13.000 --> 01:02:47.000
Yeah, that's a good one. Lots of stuff in storage Hybridisk storage pools finally released which gives you up to 5 petabytes of data in a single pool with 5x increase from what you cover for Hyper disk exit pools is the biggest and fastest block storage any public cloud. Of course it doesn't work with any of the features you really want to use like Multiwriter or ha, which I complained about to someone anywhere cache available to you. Rapid storage, Google Cloud Managed Lustre for whoever wants that. And Storage Intelligence which gives you storage insights using of course LLMs.
240
01:02:47.000 --> 01:02:48.000
I like that one.
241
01:02:48.000 --> 01:02:49.000
I like that one.
242
01:02:49.000 --> 01:02:54.000
So we have intelligent tiering now that AWS said for years but we use LLM so it's better.
243
01:02:54.000 --> 01:02:55.000
It's better.
244
01:02:55.000 --> 01:02:56.000
Yeah.
245
01:02:56.000 --> 01:03:01.000
That's what I read when I read that article. I was like cool, good chat.
246
01:03:01.000 --> 01:03:24.000
Let's see anything else that we missed that we should talk about going through my thing BigTable SQL. You can run SQL on BigTable. You're welcome. A bunch of talk about this migrating SQL server databases using Gemini if you would like to do the lift and shift from Microsoft SQL Server to PostgreSQL. Does Google have the tool for you?
247
01:03:24.000 --> 01:03:26.000
Oh, do they?
248
01:03:26.000 --> 01:04:20.000
DMS now has built into it AI capabilities that will help analyze your T SQL syntax and built in functions and provide translation directly to PostgreSQL and PG SQL. The data mappings will be done as well and then also we'll look at all the connection strings inside your application code that are pointing to SQL Server and update them to be postgres as well. So they said that this can do majority of the work. You should still need to audit IT and QA it, et cetera. But that this can can provide a heavy automated migration process and then combined with DMS ability to do slow migrations, you can basically set this translation layer up in between. You could be working on the conversion for months with your active real time data. It's not an offline operation. You can do it online, which is kind of nice. My point to them was I don't really want to move my bad server procedures from SQL Server to postgres. I'd rather move them somewhere else. And they said that's a great idea so and thought of it clearly.
249
01:04:20.000 --> 01:04:42.000
I yeah, I wish they didn't make this announcement because then I Could still live in the happy land I was before where I didn't realize that you could write the same sort of level of complex stored procedures in Postgres. And so I wish I didn't know that information. I didn't. I didn't need to. Doesn't help anyone now. I'm just sad.
250
01:04:42.000 --> 01:04:53.000
Well, it's good now that you know it. So that when someone, you have to do a migration in the future of postgres to, you know, somewhere else, you know, to look for the terrible life choices that somebody else has made that they have pawned off on.
251
01:04:53.000 --> 01:05:04.000
Oh, you'll find them both. I don't have to go looking for that. It'll be like, oh, why didn't this work? I'm like, what is this? Yeah, this is application logic in, in your database. Stop doing that.
252
01:05:04.000 --> 01:05:07.000
It's the best place to put it, Ryan. Where else would you put it?
253
01:05:07.000 --> 01:05:14.000
I mean, it gets you a licensing save, but it does give you a tech debt. Doesn't fix that problem.
254
01:05:14.000 --> 01:05:27.000
And you know, I really wonder about performance because there's a reason why people use, you know, the Oracle and Microsoft SQL Server for those large computational sets. Like, it's because it's way performant. That's why they spend all the money.
255
01:05:27.000 --> 01:05:31.000
I mean, Postgres can do it too. I mean, Postgres is very performant at server procedure logic.
256
01:05:31.000 --> 01:05:32.000
It can.
257
01:05:31.000 --> 01:05:33.000
It can. Yeah.
258
01:05:33.000 --> 01:05:35.000
I've never heard of that.
259
01:05:35.000 --> 01:06:00.000
Most people don't do it, but it definitely can. I mean, back in the day when it was competing directly with SQL Server and Oracle, many, many, many, many, many, many years ago, lots of startups ran very large postgres workloads, including heavy store procedures, because that's the only way we had to do it at the time. But then they all realized that with Java they can move it out and they all stopped doing it very quickly. So it didn't last as long as it did in the. Net world, but it did exist.
260
01:06:00.000 --> 01:06:04.000
All right, I'm glad I missed that phase of computing.
261
01:06:04.000 --> 01:06:05.000
Yeah, yeah, you're welcome.
262
01:06:05.000 --> 01:06:11.000
All I just heard, once we move stored procedures into Java, my parade just got painfully hurt.
263
01:06:11.000 --> 01:06:15.000
So you didn't move the store procedure as is. You rewrote the business logic.
264
01:06:15.000 --> 01:06:16.000
Yeah, yeah, yeah.
265
01:06:16.000 --> 01:06:21.000
But Java, I. I got stuck on Java and then I just got upset.
266
01:06:21.000 --> 01:06:29.000
Sorry. I mean, I know that's what we used to do back in the day. We use Java, or it was. Or if you're at places like I was at, we use Ruby, which you guys loved.
267
01:06:29.000 --> 01:06:31.000
And, and you see what that did to him.
268
01:06:31.000 --> 01:06:33.000
Yeah, so I don't have any hair.
269
01:06:33.000 --> 01:06:39.000
Because I have video once we were discussing this.
270
01:06:39.000 --> 01:06:51.000
So that's, you know, that's sort of the gist of it there. Well, let's get on to the most important area of discussion and that is who won the Google Next predictions?
271
01:06:51.000 --> 01:06:54.000
I don't know. I don't think it's all that important. I think we just give it.
272
01:06:54.000 --> 01:06:57.000
I think it's Jonathan. I think Jonathan won. Yes.
273
01:06:57.000 --> 01:07:32.000
Well, I was very pleased that Ryan did not win, won't be announcing anything new service announcements, just enhancements for AI and Gemini, et cetera. So that would have been a really boring show today. We would have been done about 45 minutes ago if they had announced anything. So I was really glad that Ryan was wrong on that one. Quite the contrarian position there on that one. Ryan also guessed incorrectly on responsible AI and console services SDK to enable or visualize your responsible AI creation or usage and he was also wrong on endpoint security tools like CrowdStrike, patch management, vulnerability type tooling. So that's a bummer, Ryan. I'm sorry, zero points.
274
01:07:32.000 --> 01:07:34.000
Yeah.
275
01:07:34.000 --> 01:07:36.000
Would you like to defend any of these and argue?
276
01:07:36.000 --> 01:07:52.000
Oh yeah, no, there was. There's definitely hidden in most of these announcements is, you know, the increased safety that you get in AI by, you know, the pre model callbacks and the post model callbacks is definitely ways to be much safer and responsible with your AIs.
277
01:07:52.000 --> 01:08:24.000
I would like to know, you know that and making sure that I was being as fair as possible with this. In the videos that are on YouTube you have access to Gemini. And so I asked Gemini for both a developer conference and that if it could give me any place where responsible AI was mentioned and the only place it gave me was in the one keynote, which I think was the developer keynote. They talked about being responsible with the transition of the wizard of Oz movie and that was the only place that even the word responsible was mentioned.
278
01:08:24.000 --> 01:08:29.000
So close.
279
01:08:29.000 --> 01:08:33.000
I'll give you a quarter of a point, maybe a 10.
280
01:08:33.000 --> 01:08:37.000
No, I mean it's. Yeah, I. Yeah, I mean I have very.
281
01:08:37.000 --> 01:08:43.000
I'm sort of sad you didn't get Endpoint security tool like a crowd strike or something to replace Qualys. But I mean, so this is.
282
01:08:43.000 --> 01:08:48.000
I knew that was a throwaway one because I. With the whiz announcement that everything's gonna go.
283
01:08:48.000 --> 01:08:53.000
You already had a throwaway one with the. With the there won't be anything announced. That's a throwaway too.
284
01:08:53.000 --> 01:08:58.000
That wasn't a throwaway. I'M serious. We should have been a throwaway, but I'm bad at this.
285
01:08:58.000 --> 01:09:06.000
All right, so we definitely shouldn't play golf score when we do this because ride will win.
286
01:09:06.000 --> 01:09:19.000
Lowest number of swings. So then that brought up me. I missed on AI agents specialized for DevOps Kubernetes or DevOps capability, which I realized after the fact when I was reading through this like oh yeah, that cloud assist thing that already existed.
287
01:09:19.000 --> 01:09:20.000
Forgotten about it. So.
288
01:09:20.000 --> 01:09:25.000
And you had none of you guys mentioned to me like well that kind of exists already. And then I'd be like oh yeah, I guess it does.
289
01:09:25.000 --> 01:09:29.000
But you guys, I thought of it but I, you know, you didn't pause long enough for me to mention it.
290
01:09:29.000 --> 01:10:42.000
Yeah, it's fine. I did get next generation of TPU GPUs optimized because I was a gimme. I knew that was going to happen so I was very pleased that one came out and it was optimized for multimodal. Let me tell you because they mentioned it a thousand times and then unification or major enhancement of Anthos and GK Enterprise. I got nothing on that. Like I said earlier in the show, the pre index there was something kind of close ish, but not exactly what I said so I wouldn't have counted it anyways. But I might have made the argument if we were all tied. But Matt crushed us all. Congratulations Matt. You missed on green AI. There's nothing green about it. And I also googled this one too. There was no mention of sustainability in either of the keynotes and being more energy efficient. So I'm not going to give you green AI. But I gave you three not AI specific keynotes and I stopped counting at three because there was a lot more after this. But cloud wan nailed it. Out of the park. I was like oh no. And then Hyper Disk Asset pools got announced on stage and next gen customer engagement suite which that just crushed it. And even the next one also would have been a non AI specific item for you as well. And that third item was AI security thing. That is not endpoint. More guardrails, et cetera. And that would be Google Unified Security or our new best friend Gus. So congratulations Matt.
291
01:10:42.000 --> 01:10:44.000
The first.
292
01:10:44.000 --> 01:10:46.000
I think this might be your second, is it not?
293
01:10:46.000 --> 01:10:47.000
I think I won Google last year also.
294
01:10:47.000 --> 01:10:51.000
I think you did, which is so ironic because you don't do anything in Google.
295
01:10:51.000 --> 01:10:54.000
Maybe that's why we have to play.
296
01:10:54.000 --> 01:10:56.000
Figure out how to play so I can win Azure.
297
01:10:56.000 --> 01:11:01.000
So there's the Azure Build conference we want in May.
298
01:11:01.000 --> 01:11:03.000
Ignite's the One that we would do.
299
01:11:03.000 --> 01:11:08.000
No, it literally is split across Build and Ignite. I went researching this after.
300
01:11:08.000 --> 01:11:25.000
Yeah, it doesn't make sense. They do Azure Build is obviously more developer focused, but they do general Azure announcements in there of things like app services and stuff like that. So think Less Beanstalk, App Runner, those types of services. Cloud run.
301
01:11:25.000 --> 01:11:30.000
I mean, you couldn't pay me to go to Ignite. I might go to Build.
302
01:11:30.000 --> 01:11:31.000
Yeah.
303
01:11:30.000 --> 01:11:35.000
Would I take the bullet for going to Ignite?
304
01:11:35.000 --> 01:11:39.000
Know it's in Seattle, so I would go visit friends, you know.
305
01:11:39.000 --> 01:11:41.000
And where is Ignite? Is it in Seattle?
306
01:11:41.000 --> 01:11:43.000
I thought Build is in Seattle.
307
01:11:43.000 --> 01:11:48.000
Oh, I thought Ignite was in Orlando.
308
01:11:48.000 --> 01:11:52.000
Oh, you might be right. I thought it was in Chicago last year for some reason.
309
01:11:52.000 --> 01:12:04.000
Ignite, when they do. The only thing about Microsoft is they rent out like whole parts of amusement parks for their parties, which is kind of cool. In Orlando. So that's worth almost going to just for that. Not really, but it's almost worth it.
310
01:12:04.000 --> 01:12:06.000
Ignite. Looks like they haven't.
311
01:12:06.000 --> 01:12:09.000
They haven't posted anything, but where was it last year? Chicago?
312
01:12:09.000 --> 01:12:13.000
I don't know. In San Francisco. Looks like you guys are going suckers.
313
01:12:13.000 --> 01:12:27.000
I can tell you the one way to make sure I never go to a conference is put in Moscone. And I'm like, I'm out there. I'm just saying, like, are you going to rsa? And I was like, nope, nope. Yeah, sorry. Nor will I ever go back to Dreamworks Dreamforce again, because that was also terrible. What?
314
01:12:27.000 --> 01:12:29.000
It's.
315
01:12:29.000 --> 01:12:32.000
Oh, the whole city is a disaster. During Dreamforce, I used to just hide at home.
316
01:12:32.000 --> 01:12:42.000
Oh, yeah. Dreamforce is a nightmare. You don't even go near the city if you can help it. I mean, like, they do a really good job making Moscone look like the best part of San Francisco. They clean the streets. They get rid of all the. All the homeless people.
317
01:12:42.000 --> 01:12:50.000
It's just so expensive. And I live close enough where I feel bad spending that kind of money, but it's not practical for me to commute two hours.
318
01:12:50.000 --> 01:12:51.000
It really isn't.
319
01:12:51.000 --> 01:12:59.000
It's like you're in that range where you're like, it's not. It's not worth the 600 a day for a hotel. But yeah, it's four.
320
01:12:59.000 --> 01:13:02.000
I can't spend four hours a day. Yeah.
321
01:13:02.000 --> 01:13:39.000
Even. Even taking the BART. It's like an hour to an hour and a half. And you're like, that's. That's too. You know, then you lose kind of the whole part of the conferences of the, you know, into the dinners and the parties and having the informal conversations. And those things have value, too. And you lose all that when you commute back and forth from a offerance. Honorable mentions. We suck this year. Honorable mentions. We didn't get a single honorable mention, which is unusual for us because normally we nail at least a couple of those. And we kick ourselves because we should have put that in our main prediction, but we didn't. That would not be the case this year. So we all did well enough that we didn't screw that up, other than Ryan, who had neither.
322
01:13:39.000 --> 01:13:45.000
And I was, well, oh, wait. Oh, wait, because I've lost more, if you could believe it or not.
323
01:13:45.000 --> 01:13:47.000
Have you won yet, Ryan?
324
01:13:47.000 --> 01:13:51.000
No. All right, I think I got a point once, but it wasn't enough to win.
325
01:13:51.000 --> 01:13:59.000
It's like one of those weird times. Somebody got like two points or two and a half. There's one of them. I remember it was like, we're like, why you call this 1.5?
326
01:13:59.000 --> 01:15:27.000
Yeah, there was one. I remember I had to go back and look at it on the tiebreakers. So again, thank you to Gemini. In YouTube. I was able to ask it the questions, the tiebreaker. Basically. I asked Gemini the first time. I said, how many times was AI, ML, artificial intelligence, machine learning? Said in this presentation, it came back and it said, 118 times. And I said, that seems excessive. I mean, I was there, but I would have noticed 118 times. It was mentioned several times. I did not feel it was that high whatsoever. Then I asked it again, hey, why don't you give me the timestamps and what the topic was? And so then it came back and it only gave me 38. And I said to it, Google, that's only 38. Are you missing the other 90? Or. They came out and said, I'm sorry, Justin, I lied to you. I was incorrect in my data, but I was able to verify the timestamps and the subjects of those. And so I can tell you, the opening keynote, those four words were said 38 times. And in the developer keynote, they were said 63 times using the same prompt. And that means the total was 101. Now, Ryan felt pretty confident at one, and he's not gonna miss on that one. Matt felt pretty good 52. And I felt pretty good for Matt, too, at 52, because I felt my guess at 97 was probably a little high. But no, no, it was four off. I almost hit that on the money, which I would have been pretty proud, even though I lost the competition. I would have been pretty happy if I hit it on the money, but I'm still pretty proud that I was only far off.
327
01:15:27.000 --> 01:15:32.000
If you get on the money, that's like, you know, you know, like you automatically win that show. Like, doesn't matter.
328
01:15:32.000 --> 01:15:47.000
I, I don't know if that's fair, but I definitely think it's worth a point, maybe in the main game. So if there was, you know, if it wasn't tied already, you know, like, it'd be an extra point to gloat about later. But if that happens ever, which I. The odds of that are probably impossible.
329
01:15:47.000 --> 01:15:53.000
Well, one of, one of these days we're going to load up all the show notes into some giant AI thing that can build us a dashboard.
330
01:15:53.000 --> 01:16:45.000
That's sort of what I'm working on for the 300 episode next week. Whoops. Working on some stuff. Working on some stuff. This is why it's not ready today, because I was busy last week. All right, gentlemen. It was a fantastic Google Next, I think second Year two, a lot of the kinks were gotten out of the system by Google. People realized that taking lifts and Ubers was a bad idea unless they planned more ahead. I also learned all the shortcuts, which I will not share because I will use them in the future if I don't stay at the hotel. There are some key secrets you should know if you are taking Ubers to the conference facility. But yeah, overall I was. I think Year two in Vegas was a tremendous success. I'm very pleased with how it turned out. And again, I, I got a lot of value out of the conference, which I was pleased to be. Not enough that I go back to Reinvent, but definitely enough for this particular conference.
331
01:16:45.000 --> 01:16:54.000
I'd probably go back to Reinvent just to see if I still think it's too big and I don't want to, but you know, you have to try every once in a while.
332
01:16:54.000 --> 01:16:55.000
Yeah, makes sense.
333
01:16:55.000 --> 01:16:58.000
I think I can answer that question already.
334
01:16:58.000 --> 01:17:44.000
It's already. It's too big. I'm sure it's too big. I mean, I, I think I, I had heard, you know, and again, don't. I'm not, I'm not official statement or official person, I think even. But I heard rumblings like friend of a friend of a friend kind of thing, that they had done a three year deal at Mandalay. So I'm curious if after next year, which they already announced the dates for next year. April 22 through the something, which again is a Wednesday through a Thursday, April 22nd through the 24th. I'm hoping when they get all the feedback that Tuesday through, or, sorry, Wednesday through Friday sucks, that that'll get shifted to the 21st. They have time still to do that, but we'll see all those people back in Vegas. But I'm sort of sad it's not on top of my birthday next year, so your liver will not get as much damage this time around, Ryan. I'm unfortunately sorry to tell you, Bobber.
335
01:17:44.000 --> 01:17:45.000
Yeah.
336
01:17:45.000 --> 01:17:47.000
But again, I mean, we can still go on Monday. We still have fun on Monday night.
337
01:17:47.000 --> 01:17:49.000
That's right. Yeah.
338
01:17:49.000 --> 01:18:00.000
We can still have a mini party. How's that? It just won't be the big weekend extravaganza. Matt, we did miss you, but I know you're on watch and so you can't.
339
01:18:00.000 --> 01:18:02.000
I am my watch. Yep.
340
01:18:02.000 --> 01:18:08.000
And Jonathan hopefully be back soon. We will share updates on that later.
341
01:18:08.000 --> 01:18:09.000
Once he's fully uploaded.
342
01:18:09.000 --> 01:18:18.000
Once he's fully uploaded to the AI cloud, actually. Ooh, that's a good segue. Black Mirror is back. Have you guys watched the new season of Black Mirror?
343
01:18:18.000 --> 01:18:21.000
But I plan to shortly.
344
01:18:21.000 --> 01:18:33.000
So the first. The first Black Mirror is right back into the depression that I appreciate for Black Mirror. Like the. Oh, yeah, I could see how this technology went wrong real bad, real fast, real quick.
345
01:18:33.000 --> 01:18:34.000
Oh, no.
346
01:18:34.000 --> 01:19:11.000
And I left the first episode sort of depressed for life. And, you know, it's. It's sort of one of these. Like the last season just didn't cut as deep after the previous administration that's now the new current administration. So I was a little worried that this would not have the right satire necessary of what I was looking for. Because House of Cards is great until Kevin Spacey decided to get me to because he's a terrible person. And then the last season was in the middle of the Trump administration. It just didn't quite have the same bite when it was happening in real life. So that show really fell apart very quickly. I was worried it wouldn't come back. But the first episode.
347
01:19:11.000 --> 01:19:12.000
It's all the way back.
348
01:19:12.000 --> 01:19:29.000
Huh? It's all the way back. I was depressed and was, you know, like, oh, God, I couldn't imagine going through what that poor man went through in that story. And the second episode was pretty good. Not quite as depressing as the first one. And then I'm on the third episode right now and I'll report back. But yeah, so good, so good right now. If you're a Black Mirror fan, it's back.
349
01:19:29.000 --> 01:19:30.000
Check it out.
350
01:19:30.000 --> 01:19:39.000
Mostly because I want them to keep renewing that series forever. So all right, guys, have a great night, and we'll see you next week in the Cloud.
351
01:19:39.000 --> 01:19:41.000
All right, bye, everybody.
352
01:19:41.000 --> 01:19:45.000
Bye, everyone.
353
01:19:45.000 --> 01:20:18.000
And that's all for this week in Cloud. We'd like to thank our sponsor, Archera. Be sure to click the link in our show notes to learn more about their services. While you're at it, head over to our website@thecloudpod.net where you can subscribe to our newsletter, join our Slack community, send us your feedback, and ask any questions you might have. Thanks for listening, and we'll catch you on the next episode.