1
00:00:00,000 --> 00:00:05,280
Now, I've got a few, I think throughout my two-year term here, I'm going to have a few highlights.

2
00:00:05,400 --> 00:00:12,120
The first thing I want to talk about is there are two things that are longer than we have in the U.S.

3
00:00:12,120 --> 00:00:15,180
Now, most people are like, you know, everything's small in Europe.

4
00:00:15,180 --> 00:00:19,320
You know, I think, first of all, you know, I kid.

5
00:00:19,600 --> 00:00:21,720
I'm not being vicious about any of this.

6
00:00:21,940 --> 00:00:28,740
But, you know, I think there's a symbiotic relationship between the fact that it's really hard to find a bathroom

7
00:00:28,740 --> 00:00:36,620
and that people don't seem to drink very much water, judging on the availability of it and the size of cups that people use.

8
00:00:36,760 --> 00:00:38,120
So I think that probably works out well.

9
00:00:38,120 --> 00:00:41,460
Now, that's a good example of things people think are small.

10
00:00:41,600 --> 00:00:43,060
But there's two things that are longer.

11
00:00:43,240 --> 00:00:46,540
One, beds are much longer lengthwise.

12
00:00:46,940 --> 00:00:47,040
Yeah.

13
00:00:47,280 --> 00:00:50,200
I don't know if they're narrower, but they're very long lengthwise.

14
00:00:50,460 --> 00:00:56,580
And also, each individual piece of toilet paper is about a fourth longer than our American toilet paper.

15
00:00:57,120 --> 00:01:02,780
I don't know what to make out of both of those if they're related, but they got lengthy things.

16
00:01:03,740 --> 00:01:05,780
I love your attempt at correlation there.

17
00:01:05,860 --> 00:01:06,740
That was unexpected.

18
00:01:07,500 --> 00:01:09,980
I mean, there must be some relation, right?

19
00:01:10,780 --> 00:01:12,020
There must be a reason.

20
00:01:12,680 --> 00:01:17,960
I mean, these seem like good icebreaker questions in a team meeting to see what people come up with.

21
00:01:18,020 --> 00:01:18,200
Yeah.

22
00:01:18,240 --> 00:01:27,180
Well, you know, I have learned when you ask these kind of things, you know, globally to people, it takes a little while to – I think you have to switch people's minds.

23
00:01:27,720 --> 00:01:35,860
You've got to switch their mode or their register out of, like, serious business, business stuff into, like, everyday things they've never really thought of.

24
00:01:36,020 --> 00:01:38,820
Like, I ask these questions a lot and people are a little confused.

25
00:01:38,880 --> 00:01:41,680
And then I explain to them, like, what I'm getting at.

26
00:01:41,760 --> 00:01:43,240
And I think they end up answering it.

27
00:01:43,300 --> 00:01:45,820
Like, a lot of times I ask, like, how do you operate this food?

28
00:01:46,340 --> 00:01:57,400
And it takes people some time to figure out that – I'm asking in this – if someone, like, was given a fork, you know, and they're like, I don't know what to do with this, I think we would be kind of flummoxed.

29
00:01:57,700 --> 00:02:00,920
But they – I really mean, like, what do I do with this fork?

30
00:02:01,060 --> 00:02:02,200
Which end do I eat with?

31
00:02:02,620 --> 00:02:07,480
Do I put this into a cork and then put a piece of food on the other end and, like, eat it armless or something?

32
00:02:08,260 --> 00:02:09,820
So, you know, things like that.

33
00:02:10,100 --> 00:02:11,700
So I'll have to find out about the toilet paper.

34
00:02:11,960 --> 00:02:12,660
I'll report back.

35
00:02:12,660 --> 00:02:14,220
Yeah, no, inquiring minds want to know.

36
00:02:14,660 --> 00:02:22,160
Also, closing out that topic, in the hotel room I stayed in temporarily, the toilet paper was provided by the Kleenex company.

37
00:02:22,640 --> 00:02:30,940
And you knew that because every third or fourth sheet had the word Kleenex printed on it or Kleenex, if you will, which is kind of an odd choice.

38
00:02:31,260 --> 00:02:34,760
I don't think people normally want to put their brand on toilet paper.

39
00:02:35,300 --> 00:02:39,400
Yeah, I guess that – we're not using that for the SpringOne platform giveaway this year.

40
00:02:39,500 --> 00:02:40,460
You've spoiled it for me.

41
00:02:40,460 --> 00:02:41,800
It's too late, isn't it?

42
00:02:42,080 --> 00:02:43,380
Otherwise, we could have done that.

43
00:02:43,380 --> 00:02:44,540
A roll of toilet paper.

44
00:02:45,340 --> 00:02:46,200
Yeah, it's practical.

45
00:02:46,640 --> 00:02:46,800
Sure.

46
00:02:48,260 --> 00:02:51,300
Well, I think it's been several weeks since we recorded.

47
00:02:51,440 --> 00:02:54,180
Google Next was – that was last week, right?

48
00:02:54,240 --> 00:02:54,960
Or the week before?

49
00:02:55,160 --> 00:02:56,800
I've been moving, so I've lost track.

50
00:02:57,800 --> 00:02:59,140
Yeah, two weeks ago.

51
00:02:59,180 --> 00:02:59,800
Two weeks ago.

52
00:03:00,060 --> 00:03:00,420
That's right.

53
00:03:00,480 --> 00:03:00,880
That's right.

54
00:03:01,100 --> 00:03:03,240
What are significant things that happened last week?

55
00:03:03,440 --> 00:03:06,460
You know, there's a time zone difference here, so I've lost track of what's happening.

56
00:03:07,100 --> 00:03:11,820
Yeah, there's still a lot of good fallout in a good way of people kind of digesting Google Cloud stuff.

57
00:03:11,940 --> 00:03:23,620
So last week, you know, there were still some good blog posts on some of the machine learning stuff they shipped and some of the new cloud server types and obviously stuff like we'll talk about with Knative, things like that that came out.

58
00:03:23,740 --> 00:03:29,180
So a lot of good stuff from the last week, kind of people digesting what came out of the show.

59
00:03:29,180 --> 00:03:36,220
So, yeah, last week itself, though, you know, I like the news for Cloud Native Computing Foundation adding Harbor to their sandbox.

60
00:03:36,480 --> 00:03:40,700
This is that open source container registry that VMware started years ago.

61
00:03:40,780 --> 00:03:43,260
I think it's actually their most popular open source product.

62
00:03:43,500 --> 00:03:47,220
And so it's the only container registry in the CNCF, which is interesting.

63
00:03:47,460 --> 00:03:50,520
And this is part of Pivotal Container Service today.

64
00:03:50,720 --> 00:03:54,920
So this is already something you get, but this kind of opens up more people being able to use it.

65
00:03:54,920 --> 00:04:04,340
And it's not just, you know, hey, it stores images, does things like security scanning and LDAP and Active Directory integration and kind of enterprise-y things for a container registry.

66
00:04:04,500 --> 00:04:07,240
So I think it'll get a nicer profile now, which is pretty cool.

67
00:04:07,580 --> 00:04:08,640
You probably know better than I do.

68
00:04:08,720 --> 00:04:12,520
How many registries do you think are container registries are out there now?

69
00:04:12,600 --> 00:04:18,680
There's at least like, if you don't count, I guess you would count public cloud ones, but there must be like way over five, right?

70
00:04:18,960 --> 00:04:20,940
Yeah, I was wondering what number you were going to choose there.

71
00:04:21,160 --> 00:04:23,680
Yeah, so it was way over a thousand.

72
00:04:24,160 --> 00:04:27,980
Yeah, there's, you know, obviously people use Docker Hub, at least for messing around.

73
00:04:28,100 --> 00:04:29,460
Google's got a popular one.

74
00:04:29,940 --> 00:04:33,040
You know, Red Hat's got one they acquired through one of their acquisitions.

75
00:04:33,140 --> 00:04:36,780
And now there's Harbor and some other ones that at least expose some of the Docker API.

76
00:04:37,000 --> 00:04:40,300
So it seems like there's at least a handful of ones that people use.

77
00:04:40,400 --> 00:04:42,040
But yeah, it hasn't exploded to like dozens.

78
00:04:42,700 --> 00:04:45,000
But it does seem like this will be interesting.

79
00:04:45,080 --> 00:04:51,260
Because arguably this is one area where maybe when you're getting started with Kubernetes or containers, you don't pay immediate attention to.

80
00:04:51,260 --> 00:04:55,140
It's just, yeah, let's just build some containers and push them up to Docker Hub or whatever.

81
00:04:55,660 --> 00:05:00,440
But I think as people start getting serious, they realize they want to have a lot more curation and control over base images.

82
00:05:00,440 --> 00:05:01,920
They want to make sure they're patched.

83
00:05:01,980 --> 00:05:04,360
They don't want to introduce accidental vulnerability.

84
00:05:04,720 --> 00:05:09,660
So it seems like as you mature, if you don't already do this up front, you pay a lot more attention to the registry.

85
00:05:10,100 --> 00:05:16,860
Yeah, I remember as perhaps you do back in the WS star era, there were there were many registries.

86
00:05:17,240 --> 00:05:26,660
And I mean, this is slightly different, but there was registries and direct I guess they were directories, not registries, but a similar sort of you've got a centralized thing that is key to your whole system.

87
00:05:26,820 --> 00:05:39,040
Otherwise, it kind of like comes crashing down and back then open source software in that category was not extremely popular like it is now.

88
00:05:39,200 --> 00:05:45,120
And so I wonder how that will play a role in consolidation of registries.

89
00:05:45,220 --> 00:05:51,660
Because it does seem, it would seem weird if you had like 30 of them running around there.

90
00:05:52,080 --> 00:06:03,500
But I don't know, maybe there is, there's ways of validly differentiating between all of the different registries that you would have such that you would have like 50 or 60 or just all sorts of ones of them.

91
00:06:03,500 --> 00:06:04,360
Yeah, it's a good question.

92
00:06:04,480 --> 00:06:15,000
It just seems like as long as they implement the standard API, which they do, so that, you know, in theory, when I can push a Docker image to Pivotal Cloud Foundry today, right, I can push source code or images.

93
00:06:15,220 --> 00:06:19,660
As long as I point it to a valid registry, it's the same API to talk to.

94
00:06:19,780 --> 00:06:25,180
So you're, as always, you're adding features around it to make it more useful, but the core interaction's the same.

95
00:06:25,560 --> 00:06:26,780
So that'll be interesting to see.

96
00:06:27,020 --> 00:06:31,380
Sure, is there an explosion of registries that add new features while keeping compatible interfaces?

97
00:06:32,000 --> 00:06:34,220
You'd suspect so, but I guess we'll see.

98
00:06:34,780 --> 00:06:40,020
Yeah, I mean, that reminds me of another, another, man, I'm trying to think which, which thing this was.

99
00:06:40,060 --> 00:06:45,200
It was probably a Steele or something like that, but, or no, it was the, it was the,

100
00:06:45,220 --> 00:06:48,540
the K-native or the K-native or however you're supposed to say it.

101
00:06:48,680 --> 00:06:52,420
I think, I think there was a video somewhere that K-native is, is, is the right thing.

102
00:06:52,760 --> 00:06:53,200
Is that right?

103
00:06:53,700 --> 00:07:00,940
And, you know, it was, it was, it was, I was watching that, the, the video that had, I only remember,

104
00:07:01,760 --> 00:07:06,360
DeWitt Clinton off the top of my head and, and, and one of our people whose name I should remember.

105
00:07:06,360 --> 00:07:11,260
And then the other guy who was in there and it was interesting the way they were talking

106
00:07:11,260 --> 00:07:17,160
about K-native and it reminded me of the old, you know, JEE stuff where we have basically

107
00:07:17,160 --> 00:07:24,980
like these interfaces and APIs and we may be sort of kind of have some code implementation.

108
00:07:24,980 --> 00:07:30,160
I mean, it's only in like, like alpha-ish at the moment, so it's not finished out, but,

109
00:07:30,660 --> 00:07:34,820
but we didn't, we maybe, or maybe don't provide the whole implementation of things.

110
00:07:34,820 --> 00:07:39,720
And then analogously in the same way that in the I'm, I'm way old.

111
00:07:39,820 --> 00:07:46,960
So I always think J2EE instead of J3EE or whatever, but back in the enterprise Java day,

112
00:07:46,960 --> 00:07:51,240
you would have all these app servers that would basically implement your, your stuff.

113
00:07:51,240 --> 00:07:56,140
And it seems like, uh, analogously, uh, similar to that, at least off the, you know,

114
00:07:56,140 --> 00:08:00,960
the way it was being spoken of as a standard for doing things and specking out the components.

115
00:08:00,960 --> 00:08:07,100
And then it would also be like, uh, insultingly fun to do some like J2EE thing and draw lines

116
00:08:07,100 --> 00:08:10,900
between them of like, you know, here, here's the, the registries and here's how you look

117
00:08:10,900 --> 00:08:12,980
things up and here's how you manage the traffic.

118
00:08:13,140 --> 00:08:14,940
Hopefully there's EJBs in there somewhere.

119
00:08:15,280 --> 00:08:19,240
I think people love EJBs and maybe we can tweak that in somehow.

120
00:08:19,520 --> 00:08:20,120
That's right.

121
00:08:20,240 --> 00:08:20,400
Yeah.

122
00:08:20,400 --> 00:08:23,980
I mean, I know, you know, we glossed over the K native stuff for a moment, but you know,

123
00:08:23,980 --> 00:08:26,140
we did get to work on that for a few months ahead of time.

124
00:08:26,140 --> 00:08:28,380
It was native until like two weeks before.

125
00:08:28,480 --> 00:08:29,700
And then they added the K back in.

126
00:08:29,760 --> 00:08:32,460
It used to be, it used to be silent, which of course made sense.

127
00:08:32,820 --> 00:08:37,040
So trying to get back to calling it K native was difficult, but you know, without being

128
00:08:37,040 --> 00:08:41,140
hyperbolic, this feels like one of the more important things that gets announced in 2018

129
00:08:41,140 --> 00:08:41,940
tech wise.

130
00:08:42,040 --> 00:08:45,840
And I only say that because if you're running Kubernetes, you're probably going to end up putting

131
00:08:45,840 --> 00:08:46,580
this on top.

132
00:08:46,580 --> 00:08:51,500
And just given how ubiquitous Kubernetes has become, this feels like a significant thing.

133
00:08:51,500 --> 00:08:52,520
Now, maybe I'm wrong.

134
00:08:52,580 --> 00:08:53,740
Maybe it crashes and burns.

135
00:08:53,840 --> 00:08:54,240
Who knows?

136
00:08:54,240 --> 00:09:00,060
But K native seems like a nice way to put app centric function centric abstractions on

137
00:09:00,060 --> 00:09:03,120
top of a layer that frankly, most devs shouldn't be messing around with.

138
00:09:03,240 --> 00:09:08,680
Like if I'm trying to focus on software, I don't want to deal with DNS and load balancers and

139
00:09:08,680 --> 00:09:10,180
container orchestrators.

140
00:09:10,240 --> 00:09:13,020
That's not my, that's not where I should be spending my time.

141
00:09:13,120 --> 00:09:17,380
So if I can give me better abstractions and it's a complex abstraction, it's not trivial,

142
00:09:17,900 --> 00:09:22,040
but if it can be run as a service and something like pivotal function service or Google's function

143
00:09:22,040 --> 00:09:25,680
capabilities, it seems like this might be super important.

144
00:09:25,800 --> 00:09:26,800
So I guess we'll go, we'll see.

145
00:09:26,920 --> 00:09:29,300
But this was a surprise announcement for most.

146
00:09:29,360 --> 00:09:34,340
It actually leaked zero leading up to the announcements, which was pretty surprising given how many people

147
00:09:34,340 --> 00:09:35,300
kind of knew about it.

148
00:09:35,680 --> 00:09:37,340
So it seems like a big deal.

149
00:09:37,660 --> 00:09:41,560
I'm glad we're involved in it, I guess, uh, stay tuned for how big of a deal it is.

150
00:09:41,940 --> 00:09:45,780
Now, no, I know you follow all this stuff closely, especially when it comes to words, you know,

151
00:09:45,780 --> 00:09:47,120
this is basically your business, right?

152
00:09:47,200 --> 00:09:52,360
Words, words, words, words, and, and, uh, pictures on PowerPoints.

153
00:09:52,360 --> 00:09:57,900
But, uh, so, so, you know, when they're talking about K native, it was sort of like, this is

154
00:09:57,900 --> 00:10:02,120
a, for serverless serverless, it was like every, every third to 20th word.

155
00:10:02,840 --> 00:10:07,260
And then, and then like, how, how are you thinking through how you would distinguish K native

156
00:10:07,260 --> 00:10:12,180
is for serverless versus like, I use Kubernetes to run applications.

157
00:10:12,580 --> 00:10:17,840
Like what's the, what's the distinction that, but between those two things, if any.

158
00:10:19,120 --> 00:10:19,480
Yeah.

159
00:10:19,500 --> 00:10:21,500
I mean, I think that's going to come out over time.

160
00:10:21,540 --> 00:10:26,040
I mean, in essence, it's taking you up a layer saying, do I want things that are more app aware?

161
00:10:26,340 --> 00:10:28,280
Do I want things that are more functional aware?

162
00:10:28,340 --> 00:10:31,300
Do I want to deal with these primitives, which are just Kubernetes and containers?

163
00:10:31,300 --> 00:10:35,340
And yes, custom resource definitions and all the power that's in an orchestrator.

164
00:10:35,820 --> 00:10:40,120
Or should I think about if I have code, I just want that code to run somewhere, which

165
00:10:40,120 --> 00:10:42,620
sounds a lot like the cloud foundry sort of value prop, right?

166
00:10:42,660 --> 00:10:46,240
But with functions as well for K native, because there's a whole build service there.

167
00:10:46,300 --> 00:10:49,980
Like just give me my function source code, build it, and then run it on Kubernetes.

168
00:10:50,140 --> 00:10:52,900
I don't really care that it's Kubernetes, just run this thing for me.

169
00:10:53,180 --> 00:10:56,120
So I think it continues to try to move up the abstractions.

170
00:10:56,180 --> 00:11:01,020
It says, as a dev, if I'm being paid to ship software, I'm probably not being paid to figure

171
00:11:01,020 --> 00:11:03,380
out some of the plumbing if I can help it.

172
00:11:03,760 --> 00:11:05,700
So why don't I just keep staying good at software?

173
00:11:05,880 --> 00:11:09,700
So it seems like it's trying to move everyone up a layer and it's, it's helping you focus

174
00:11:09,700 --> 00:11:13,840
on source code and not necessarily having to focus on packaging and configuration.

175
00:11:14,380 --> 00:11:14,760
Right, right.

176
00:11:14,860 --> 00:11:19,360
And there was a, there was a demo by the other Google guy whose name, I can't remember.

177
00:11:19,860 --> 00:11:22,100
And it was just a basic, I mean, there was two demos he had.

178
00:11:22,100 --> 00:11:28,560
One was a hello world demo where he built his own container and then they, he had the system

179
00:11:28,560 --> 00:11:29,800
build a container for him.

180
00:11:30,380 --> 00:11:38,500
And yeah, I mean, I guess what'll be interesting to see is when, at what point do you not deploy

181
00:11:38,500 --> 00:11:40,340
your application fully?

182
00:11:40,500 --> 00:11:43,660
I'm doing air quotes here, serverless, right?

183
00:11:43,940 --> 00:11:46,120
You know, it would be nice to think about.

184
00:11:46,320 --> 00:11:51,420
So if I'm doing a, and I've gone above sort of, well, I'll just use K native as the demo

185
00:11:51,420 --> 00:11:54,120
example, like doing that style of programming.

186
00:11:54,120 --> 00:11:57,020
Could you do an entire online banking system from it?

187
00:11:57,100 --> 00:12:01,760
Like seeing your accounts and transferring money and bill pay, or is there some sort of,

188
00:12:01,800 --> 00:12:05,780
to be jokey about it, do I need some server full layers?

189
00:12:06,460 --> 00:12:10,780
And, and let's, let's assume there's no like legacy stuff you need to support or, you know,

190
00:12:10,780 --> 00:12:11,660
any stuff like that.

191
00:12:11,800 --> 00:12:13,300
It's just a brand new application.

192
00:12:14,580 --> 00:12:19,420
Yeah, I mean, you know, being, I'm purposely steering all this conversation towards serverless

193
00:12:19,420 --> 00:12:22,300
because, you know, that, that's a part that we're spending a lot of attention on.

194
00:12:22,340 --> 00:12:23,780
But in reality, this is just apps.

195
00:12:23,920 --> 00:12:25,360
So apps run on K native.

196
00:12:25,500 --> 00:12:30,000
And yes, they're more ephemeral scale to zero apps, which we think of as more of serverless

197
00:12:30,000 --> 00:12:31,420
and functions and things like that.

198
00:12:31,460 --> 00:12:34,880
But in reality, I can deploy just apps to K native.

199
00:12:35,120 --> 00:12:38,260
Now, is it going to be as friendly to some legacy stuff and things like that?

200
00:12:38,280 --> 00:12:38,840
Probably not.

201
00:12:38,840 --> 00:12:42,820
I'm still going to have, as always, multiple sorts of abstractions for different types of

202
00:12:42,820 --> 00:12:43,220
workloads.

203
00:12:43,940 --> 00:12:49,380
But it feels like, I mean, yes, in some cases, I could run full systems on K native with different

204
00:12:49,380 --> 00:12:54,100
types of apps, some that potentially are function sort of stuff, others that are just full blown

205
00:12:54,100 --> 00:12:58,460
apps, and then having the eventing subsystem that works between them, which is part of K native

206
00:12:58,460 --> 00:12:58,940
as well.

207
00:12:59,240 --> 00:13:03,680
We'll see if that's a pattern that emerges, or if this kind of gets used for one sort of

208
00:13:03,680 --> 00:13:08,620
workload, and you still have other sorts of abstractions for more stateful stuff or long

209
00:13:08,620 --> 00:13:10,880
running services or streaming or what have you.

210
00:13:11,300 --> 00:13:16,580
But, you know, it's an exciting way to maybe have us spend a little less time on infrastructure

211
00:13:16,580 --> 00:13:18,480
plumbing and a little more time thinking about software.

212
00:13:18,920 --> 00:13:19,280
Yeah, yeah.

213
00:13:19,460 --> 00:13:25,540
I mean, that seems to be, that was what was exciting about that demo is here's a more concrete

214
00:13:25,540 --> 00:13:32,380
example of how serverless is just a new way of doing application programming and not sort

215
00:13:32,380 --> 00:13:35,660
of like the lesser thing of like, you know, a lot of the conversation here about serverless

216
00:13:35,660 --> 00:13:41,460
is like, it's these ephemeral event driven things that run and you're kind of left to think

217
00:13:41,460 --> 00:13:47,200
of them as like, weird little magic scripts somewhere and not just like, not just like I wrote

218
00:13:47,200 --> 00:13:50,620
a go application and I put it in the Docker container and now it's running.

219
00:13:51,040 --> 00:13:56,560
And it also is sort of like, I mean, the legacy thing is always a problem.

220
00:13:56,680 --> 00:14:01,500
I always think of, you know, I was never a big physics person, but I remember a lot of

221
00:14:01,500 --> 00:14:05,720
physics equations were like, well, first of all, let's assume friction doesn't exist.

222
00:14:06,200 --> 00:14:10,660
And I think that's the equivalent of like, let's just assume legacy doesn't exist.

223
00:14:10,760 --> 00:14:15,700
So we just take friction and legacy off the table to have sort of a pure understanding of

224
00:14:15,700 --> 00:14:20,500
things which is fine. But but it does it does seem like when you started thinking about it

225
00:14:20,500 --> 00:14:26,920
in that way, it's interesting that it gets back to the cycle of like no ops, like a long,

226
00:14:27,080 --> 00:14:30,780
a long time ago, I don't think I'll look this up must have been like four years ago, everyone

227
00:14:30,780 --> 00:14:35,660
in the DevOps world, or not everyone, but the discussion in the DevOps world was like this

228
00:14:35,660 --> 00:14:40,440
no ops thing is crazy. There's there's, it's not that there's not going to be any operators.

229
00:14:40,440 --> 00:14:44,860
So we shouldn't say no ops. But then on the other hand, like you kind of like, think about

230
00:14:44,860 --> 00:14:49,880
you look at that demo and other things, and it does seem like, you know, in a less sassy

231
00:14:49,880 --> 00:14:55,440
way, this vision that we had of no ops in the past can sort of come to fruition. And instead

232
00:14:55,440 --> 00:15:00,380
there's, you know, platform ops and SRE and things like that. But it's in the same way that

233
00:15:00,380 --> 00:15:06,720
like, I think maybe two or three years ago, all of the all the, you know, you know, hair

234
00:15:06,720 --> 00:15:10,800
color tinted people, and all the DevOps stuff, we're saying how serverless was ridiculous.

235
00:15:10,800 --> 00:15:15,260
That was a name. And now everyone says it as a name. Like this kind of like this cycle

236
00:15:15,260 --> 00:15:17,220
of these phrases that come and go.

237
00:15:17,480 --> 00:15:21,300
There you go. I think magic little scripts is probably the title of this episode.

238
00:15:22,700 --> 00:15:25,180
That's right. Only quotes are magic little scripts.

239
00:15:25,620 --> 00:15:31,020
Yeah. So yeah, the last piece of news, I think you might have added one more was also related

240
00:15:31,020 --> 00:15:37,400
to this was the was the ST1.0. And this stuff's kind of plumbing for people, this idea of service

241
00:15:37,400 --> 00:15:42,140
meshes and control planes and sidecars. And like, gosh sakes, I can't keep track of Kubernetes

242
00:15:42,140 --> 00:15:46,860
and serverless. Why do I have to care about a freaking service mesh? So on one hand, I guess

243
00:15:46,860 --> 00:15:51,840
people could tune this stuff out and feel like it's just noise. But it is something that's

244
00:15:51,840 --> 00:15:56,140
important to platform builders. It's something that our pivotal post actually did a really nice

245
00:15:56,140 --> 00:16:00,960
job telling kind of a history story that explains why this stuff matters and why this is coming

246
00:16:00,960 --> 00:16:05,040
into Cloud Foundry and why this is something that platform builders should care about. I mean,

247
00:16:05,040 --> 00:16:09,580
should most, you know, enterprise engineering teams be deploying this stuff? I don't know.

248
00:16:09,580 --> 00:16:15,760
It still feels like potentially you want something integrated by a platform provider, but you can.

249
00:16:16,240 --> 00:16:20,080
So but there's also gonna be some new architecture paradigms that come from this as you think of

250
00:16:20,080 --> 00:16:25,440
sidecars versus things embedded in your code itself or things like circuit breakers or distributed

251
00:16:25,440 --> 00:16:30,220
tracing and instead moving that into the service mesh. Like these are now fundamental conversations

252
00:16:30,220 --> 00:16:35,240
we're gonna have to have about where does this stuff belong? So I guess my advice is don't,

253
00:16:35,460 --> 00:16:39,220
I mean, be on the sidelines, maybe keeping an eye on it. Maybe you don't jump in with two feet

254
00:16:39,220 --> 00:16:43,060
on deploying these things, but don't ignore this conversation because I think it's going to impact

255
00:16:43,060 --> 00:16:48,000
how you are deploying software as an enterprise in the next couple of years at the latest.

256
00:16:48,440 --> 00:16:53,300
Yeah. And to sort of reprise something I was talking about earlier, I think as you're saying,

257
00:16:53,680 --> 00:16:58,080
there's sort of like this coalescing of standardization. And I don't think you're supposed

258
00:16:58,080 --> 00:17:04,100
to talk about standards nowadays. I think in the post like WS star like error, we can't ever have

259
00:17:04,100 --> 00:17:08,840
standards again. Very, very bad to have standards. You don't want that. But let's say, let's pretend

260
00:17:08,840 --> 00:17:15,220
like we can use that word. But there's standards that are emerging. And as pretty much everyone

261
00:17:15,220 --> 00:17:23,060
on the vendor side and the user side, and then the open source side, like really, things turn out better

262
00:17:23,060 --> 00:17:30,600
when there's standards. Because one, you know, if you're buying on the buy side, someone consuming

263
00:17:30,600 --> 00:17:35,680
this technology, like you kind of know what you're getting into, you understand, I want to buy something

264
00:17:35,680 --> 00:17:41,240
that satisfies the standard operates this way. And I can focus on if it's the best way of doing it and

265
00:17:41,240 --> 00:17:46,060
how performant it is, or if I like the way it does it. But you don't have to focus on like understanding

266
00:17:46,060 --> 00:17:51,840
what serverless means, or what cloud native means. And then of course, on the production side, people

267
00:17:51,840 --> 00:17:57,860
like making and selling stuff. It's good because you don't have to like, spend a lot of money reinventing

268
00:17:57,860 --> 00:18:01,520
everything. Like it just makes everything more efficient to have standards around this, which

269
00:18:01,520 --> 00:18:07,480
it's probably for the better that things coalesce towards that. And you know, it's nice to have like a

270
00:18:07,480 --> 00:18:12,320
period of innovation where there's all these different standards happening. And you've got your

271
00:18:12,320 --> 00:18:19,080
thousand flowers of blooming grass that gets cut because it's too high or something. But, you know,

272
00:18:19,100 --> 00:18:24,800
eventually, you want to coalesce down into just a few things or it's or it's madness. So when one just

273
00:18:24,800 --> 00:18:30,360
little fun thing, I haven't actually used this yet. Because that because I've been moving, as I mentioned,

274
00:18:30,900 --> 00:18:36,380
but I saw that Amazon released this thing called part finder. And, you know, it doesn't really have

275
00:18:36,380 --> 00:18:42,040
anything to do. Well, it sort of does. But as I understand it, you can like point your camera at

276
00:18:42,040 --> 00:18:47,760
a physical object, and it will say, that is like a three and a quarter inch, or I don't know, 20

277
00:18:47,760 --> 00:18:54,680
millimeter screw. And of course, Amazon's motivation is like, so you can go buy some. But it is it is

278
00:18:54,680 --> 00:19:00,640
like, it's an intriguing and I've noticed my son has this issue every now and then is well, actually,

279
00:19:00,640 --> 00:19:05,720
I'll tell you exactly what happened. We were in the airport here. And he found half of this weird

280
00:19:05,720 --> 00:19:10,120
little wooden thing with spikes on it. And he kept asking what it was. And I was thinking like,

281
00:19:10,200 --> 00:19:15,220
oh, if only we had the part finder, we could point it at it, and it would tell him what that thing was.

282
00:19:15,500 --> 00:19:21,320
But it's a fun idea. And I'm sure it's not this great and universal. But it'd be a fun idea that

283
00:19:21,320 --> 00:19:25,740
you could just sort of walk around kind of, I guess, whether you want to think of yourself as that

284
00:19:25,740 --> 00:19:30,500
Terminator view, or maybe the predator one, I'm sure in Star Trek, there's one that's like peace

285
00:19:30,500 --> 00:19:34,780
loving and non capitalistic or something. But you could just point your little

286
00:19:35,060 --> 00:19:39,260
camera at something and have it tell you what it was and information about it. It seems like

287
00:19:39,260 --> 00:19:45,380
a really interesting use of a lot of like, you know, giga technologies we've been talking about

288
00:19:45,380 --> 00:19:48,680
for five years with augmented reality and machine learning.

289
00:19:48,900 --> 00:19:53,040
That's the stuff that normal people can relate to and not all the necessarily plumbing stuff that

290
00:19:53,040 --> 00:19:57,180
sometimes we geek out over, but it's actually not outcome oriented. So the things you're talking

291
00:19:57,180 --> 00:20:00,960
about, that's the actual outcome, right? That's the things that somebody will make money on and make

292
00:20:00,960 --> 00:20:05,160
me want to use your service. Yeah, now that I think of it, you know, I don't know if you've

293
00:20:05,160 --> 00:20:09,740
had this problem. But you know how you're like, I never really know which screw I should be using

294
00:20:09,740 --> 00:20:14,540
for some or if you got to match a drill bit to a screw. And that's always a problem. And that

295
00:20:14,540 --> 00:20:19,640
would be a great little AR thing is to put like a screw down and have it say you need the three

296
00:20:19,640 --> 00:20:24,520
force drive, you know, screw drill bit or you need this one. That would actually be great. That's

297
00:20:24,520 --> 00:20:30,440
kind of, you know, the first AR thing that I saw that was really useful was the hanging pictures AR

298
00:20:30,440 --> 00:20:35,520
thing. Do you ever use one of those where I have, you know, I don't know, maybe you don't have this

299
00:20:35,520 --> 00:20:41,480
problem over there in the Pacific Northwest. But typically, let's say you've got two people in a

300
00:20:41,480 --> 00:20:46,840
relationship. One of them wants to hang a picture on the wall. And the other one is like, maybe what I'd

301
00:20:46,840 --> 00:20:53,540
like to do is anything else. Because, because what will happen is you want to make sure the picture's

302
00:20:53,540 --> 00:20:59,380
even. And so you hang the picture up. And it's, of course, not even the other person is like, you

303
00:20:59,380 --> 00:21:03,540
know, maybe you move the left up a little bit. And then you do that, and it's not even and you know,

304
00:21:03,540 --> 00:21:07,740
you're trying to make it level. But there are some apps that you could use. I'm still so I'm sure

305
00:21:07,740 --> 00:21:11,500
they're still around. And they would tell you basically like where to put the holes so that things

306
00:21:11,500 --> 00:21:16,260
would be even. And so relationships be less stressful, essentially.

307
00:21:16,260 --> 00:21:21,600
I think also in the past two weeks, the the the a lot of the sessions for SpringOne platform were

308
00:21:21,600 --> 00:21:26,780
announced, I forget the exact date. But every year, we like to kind of go through and talk about ones

309
00:21:26,780 --> 00:21:32,220
we're looking forward to. And I think we've both been involved. And I mean, you've done some crack

310
00:21:32,220 --> 00:21:37,880
sharing and a whole lot more as well. So you kind of have been watching things as they evolve. But yeah,

311
00:21:37,880 --> 00:21:42,260
there's, you know, looking through our list, there's a few that we both chose. So we've got a good,

312
00:21:42,260 --> 00:21:48,200
good Venn diagram, but not not that overlapping. So I think this year, speaking of track sharing,

313
00:21:48,200 --> 00:21:55,540
I was as as I was last year, and maybe the year before, I don't really remember. I was I was helping

314
00:21:55,540 --> 00:22:00,600
out along with several other people on the the newly every year, this track gets a little different. But

315
00:22:00,600 --> 00:22:06,540
we have the the DevOps pipeline and agile track. And I think what's fun about that track is agiles added

316
00:22:06,540 --> 00:22:12,840
in there, which which has shown up here and there in the past. But it's a huge, huge part of what

317
00:22:12,840 --> 00:22:18,480
pivotal customers do. You know, the whole point is improving the way you do software. So they should be

318
00:22:18,480 --> 00:22:24,420
doing your software in an agile way. So there's a few sessions in there that I think will be interesting

319
00:22:24,420 --> 00:22:29,820
to see one of them. And I remember going to this one, there's one called data driven decision making

320
00:22:29,820 --> 00:22:36,560
for product development, which by far is not the longest title of the talk on my list. So you can get

321
00:22:36,560 --> 00:22:41,840
ready for that. You know, I'm always a fan of very long titles. So I'm looking forward to it. But I think

322
00:22:41,840 --> 00:22:47,300
what's interesting about this talk is, you know, it's essentially, you know, we talk a lot about,

323
00:22:47,300 --> 00:22:52,400
or at least I do, about the point of doing software better is to put it and using all this container

324
00:22:52,400 --> 00:22:56,540
stuff and cloud native things, whether you're server full or serverless, or you've got ops,

325
00:22:56,560 --> 00:23:01,320
or you're no ops, or whatever, is eventually, you want to have good software. And the way you're

326
00:23:01,320 --> 00:23:05,900
going to have good software is to put a fast feedback loop or a small batch process in place where

327
00:23:05,900 --> 00:23:11,000
you can deploy some software. And every week, you can observe how it's being used and make

328
00:23:11,000 --> 00:23:16,980
product decisions based on it. And this talk, I think, is going over how you do that, what it looks

329
00:23:16,980 --> 00:23:22,760
like, as the title says, to make data driven decision making for product development. And I think

330
00:23:22,760 --> 00:23:27,860
it's a topic that is, I don't know, it's discussed every now and then here and there, but it's never

331
00:23:27,860 --> 00:23:32,740
really discussed as much as I would like it to. For example, now I'm gonna have to go find the link to

332
00:23:32,740 --> 00:23:38,880
this. I mean, I think, I think the one of the, I guess it's sort of academic, but one of the

333
00:23:38,880 --> 00:23:44,920
academic-y sort of citations for the idea that you should observe what your users do,

334
00:23:44,920 --> 00:23:51,700
and it will make your software better is this, I think it's maybe like a 2008 Microsoft write-up

335
00:23:51,700 --> 00:23:58,860
where I think it was in, maybe in Bing or Xbox, they were, they were looking at user behavior

336
00:23:58,860 --> 00:24:04,020
and they tracked, I don't know if it was all, but they tracked a lot of features that they had put

337
00:24:04,020 --> 00:24:09,620
into the version of the software. And they found out something that like only, I think it was like

338
00:24:09,620 --> 00:24:15,240
30% of the features were used in a way that their product managers originally thought they would be

339
00:24:15,240 --> 00:24:22,960
used in, which is a little bit of a weird wording. It basically means that 70% of the work that they did

340
00:24:22,960 --> 00:24:28,320
didn't really result in what they wanted. Like the feature didn't really work out very well. So

341
00:24:28,320 --> 00:24:35,700
I bring that up because that's sort of like the most widely known citation of like data-driven things.

342
00:24:36,000 --> 00:24:39,940
So it's always good to get a lot more of those things out there because, you know, I guess that

343
00:24:39,940 --> 00:24:45,200
was a decade ago or more. And, uh, but it'll be interesting to see what, uh, the two speakers in

344
00:24:45,200 --> 00:24:50,060
there go over. So how about, how about you? What's a, what's one, we'll go back and forth.

345
00:24:50,460 --> 00:24:56,200
Yeah, we'll go back and forth. Yeah. I know for those who, uh, haven't attended SpringOne before

346
00:24:56,200 --> 00:25:01,180
we did update some of the track stuff. I know Coté, you had mentioned that, you know, not specifically

347
00:25:01,180 --> 00:25:05,980
just a DevOps track. We're doing some agile stuff in there as well. We added some serverless

348
00:25:05,980 --> 00:25:11,180
attention this year, a Kubernetes track, just kind of reflecting reality of what are our customers

349
00:25:11,180 --> 00:25:15,180
doing? What is pivotal offering? So the tracks continue to evolve. The mainstays,

350
00:25:15,180 --> 00:25:18,580
stage, which I'm responsible for, uh, has come together really nicely. There's actually

351
00:25:18,580 --> 00:25:23,140
code every day on stage, including the third day. So you're always going to have code demos

352
00:25:23,140 --> 00:25:28,140
and then kind of people talking about outcomes and then back to some product updates and just

353
00:25:28,140 --> 00:25:33,060
keeps a, hopefully a good vibe. We also have different MCs every day just to mix it up.

354
00:25:33,060 --> 00:25:38,380
So people like Josh Longman and Dormain on day one and Diogenes and Lauren on day two, Peter

355
00:25:38,380 --> 00:25:43,480
Humphrey and Andrew Clay Schaefer on day three, just kind of keep up, uh, keep things unexpected.

356
00:25:43,480 --> 00:25:47,980
So it should be fun. Just the, the vibe continues to change every year just for fun. So you don't get

357
00:25:47,980 --> 00:25:53,060
bored. But when you look at the talks that I'm, I was flipping through, you picked more than me and I was

358
00:25:53,060 --> 00:25:58,560
trying to down select, I guess I shouldn't have. Uh, one of the ones I picked was, it was use cases for

359
00:25:58,560 --> 00:26:04,560
STO and Envoy integration with Cloud Foundry with, with Shannon and Usha and, and Shree as well. I think

360
00:26:04,560 --> 00:26:08,900
they've, uh, two or three of those have been on the podcast before, but one of this was, as we just

361
00:26:08,900 --> 00:26:13,560
talked about, you know, as we think about STO, as we think about Envoy and Cloud Foundry, like who,

362
00:26:13,660 --> 00:26:18,440
who cares? Like what is all that doing for the platform? So for them to be able to come in and

363
00:26:18,440 --> 00:26:22,680
they explain this stuff well as like, what is this going to enable in the platform? How is this going to

364
00:26:22,680 --> 00:26:27,480
make it possible to have potentially clusters talk to each other or different abstractions talk to each

365
00:26:27,480 --> 00:26:32,300
other? You mentioned Coté, this idea of, Hey, would maybe my whole banking architecture just be on

366
00:26:32,300 --> 00:26:36,900
something like K native or does it still spread across? And if we assume the answer is it spreads

367
00:26:36,900 --> 00:26:42,800
across, how can the networking be transparent? Like, I don't want to care that this is on K native and this is on

368
00:26:42,800 --> 00:26:47,900
some other Kubernetes cluster and this is on Cloud Foundry. I just want things to reach each other and talk to

369
00:26:47,900 --> 00:26:53,860
each other and it doesn't matter. So what happens when networking becomes just this sort of connected

370
00:26:53,860 --> 00:26:59,940
mesh that spans clouds, spans different facilities, spans different clusters, abstractions? So I think

371
00:26:59,940 --> 00:27:03,300
that's where we're starting to go with this. So I'm interested in this particular talk just to see

372
00:27:03,300 --> 00:27:08,200
how we're starting to plant those seeds. Yeah, I know that there will be a good, good to see that.

373
00:27:08,260 --> 00:27:12,480
I mean, I think that's like looking through all of the talks and I won't go over all the talks

374
00:27:12,480 --> 00:27:18,440
because I did, or the ones I selected, but there is a, there's like a whole lot of new topics even from,

375
00:27:18,440 --> 00:27:23,060
from last year as we're going over. I mean, we've had a, there's, there's of course some Istio things

376
00:27:23,060 --> 00:27:27,140
and there's, there's another good one. I forget the name of comparing Spring Cloud to Istio, which

377
00:27:27,140 --> 00:27:33,360
I would be eager to see. That's always one of my first questions. And there's also, you know,

378
00:27:33,360 --> 00:27:40,420
also in the, as I mentioned, the DevOps track talks about pipelines now, which, and I remember

379
00:27:40,420 --> 00:27:45,020
making sure we selected a sufficient amount of pipeline talks, which I think is another thing

380
00:27:45,020 --> 00:27:51,780
that is good to start highlighting because it seems like, I don't know which one would be number one

381
00:27:51,780 --> 00:27:56,660
versus number two. That's always kind of a false distinction, but it seems like one of the most

382
00:27:56,660 --> 00:28:03,140
important assets you have is your build pipeline, right? Like a lot of, a lot of problems that get

383
00:28:03,140 --> 00:28:10,320
solved, get done in your, your build pipeline because of the automation and the tracking and the kind

384
00:28:10,320 --> 00:28:16,760
of non-manual way of doing things all the way from compliance things to handling security to just

385
00:28:16,760 --> 00:28:23,920
like making sure your code works. And then the, the ability to roll back and run multiple versions,

386
00:28:23,920 --> 00:28:28,920
all of these things are made a lot easier by your build pipeline. So there's a couple of sessions

387
00:28:28,920 --> 00:28:34,240
on that. And one of them that, you know, I always like actual customers talking because us people at

388
00:28:34,240 --> 00:28:39,160
pivotal are great and brilliant, but, uh, then it would just be, if it was only pivotal people talking

389
00:28:39,160 --> 00:28:43,760
about how we did stuff, it'd be a conference about software vendors, which might be fun, but not as

390
00:28:43,760 --> 00:28:49,960
widely applicable. So there's one called, uh, uh, as short a title as you can have two words called

391
00:28:49,960 --> 00:28:56,360
extreme pipelines that has a MasterCard person and a pivotal person on, and it goes over how, uh,

392
00:28:56,360 --> 00:29:01,340
MasterCard built up their pipeline and, and, you know, some lessons learned with it. And so that'll be a good

393
00:29:01,340 --> 00:29:06,660
talk to look at for people who are, uh, you know, curious about actually building out a pipeline.

394
00:29:06,660 --> 00:29:12,620
And I say actually, because, you know, what I tend to find is, uh, based on questions people are asking

395
00:29:12,620 --> 00:29:17,920
and what they're using, they might have like a continuous integration, uh, pipeline, so to speak

396
00:29:17,920 --> 00:29:22,480
in place, but they may not have the full blown pipeline, uh, that you would expect from people.

397
00:29:22,920 --> 00:29:25,740
So, uh, that, that'll probably be a fun one to check out as well.

398
00:29:26,340 --> 00:29:30,080
Yeah, no doubt. Related to that, you had mentioned one, uh, in your,

399
00:29:30,280 --> 00:29:35,020
in your notes about this, but it was one I flagged to around zero to multi-cloud related to that.

400
00:29:35,020 --> 00:29:40,600
Cause that point of, okay, how do I actually kind of take what I'm doing in probably multiple

401
00:29:40,600 --> 00:29:44,880
environments, multiple clouds, even, and just have some automated deployments to each of those.

402
00:29:44,960 --> 00:29:49,600
It doesn't feel unique each time. And actually, frankly, right before I jumped on the, uh, the

403
00:29:49,600 --> 00:29:54,420
podcast, I was reading some thoughts from, from Mitchell at Hashi Corp who had some good answers

404
00:29:54,420 --> 00:29:58,860
today around what does multi-cloud mean? What's the point of it? And again, it was kind of consistency

405
00:29:58,860 --> 00:30:02,800
of some of these things across environments and what does it take to achieve that? So,

406
00:30:02,860 --> 00:30:07,320
I mean, this talk by our folks from John and, and margin thinking about that and how they use

407
00:30:07,320 --> 00:30:11,600
Spinnaker, how they use spring cloud pipeline. I think that's important stuff. Cause if we assume

408
00:30:11,600 --> 00:30:15,700
the future is I have lots of infrastructure in different places, how can we at least have

409
00:30:15,700 --> 00:30:20,340
consistency to all of them so that your choice of cloud is made at the last responsible moment,

410
00:30:20,340 --> 00:30:24,280
not the first thing you're figuring out. And if we can do that, that seems to offer a ton more

411
00:30:24,280 --> 00:30:29,880
flexibility. Oh, and I think also, as always, Marcin has figured out how to get multiple talks accepted.

412
00:30:30,340 --> 00:30:35,380
He's, he's always clever. Yeah. I think the other one he's talking on is, uh, is going over at Zipkin,

413
00:30:36,080 --> 00:30:42,500
which, uh, will be exciting. Uh, it's always fun to see tracing, you know, for someone, for someone who

414
00:30:42,500 --> 00:30:48,820
used to, uh, walk SNMP MIBs, I always like a good tracing story. Do you ever do that? Do you ever

415
00:30:48,820 --> 00:30:53,760
get like a home router or home wifi access point and you're very excited because there's SNMP on there

416
00:30:53,760 --> 00:30:59,000
or, or, you know, you can turn it on in, in, uh, I guess it was OS 10 back then. You can turn it on

417
00:30:59,000 --> 00:31:03,320
in Mac OS and you can just sit there and look at your SNMP stuff.

418
00:31:03,920 --> 00:31:08,360
Man, you have more fun than me. I need to change my routine.

419
00:31:08,620 --> 00:31:12,260
That's a good response. You have more fun than me. Uh, yeah.

420
00:31:12,680 --> 00:31:13,440
What's your next one?

421
00:31:13,720 --> 00:31:18,700
Well, I think, uh, there's the, speaking of, uh, people doing things as a world of customers,

422
00:31:18,700 --> 00:31:23,160
there's, I, I didn't write down the whole, uh, the whole title for it, but there's, uh, Boeing has

423
00:31:23,160 --> 00:31:27,900
a talk that they're doing, uh, with a little person and I'm, you know, other than it being from,

424
00:31:27,900 --> 00:31:33,960
uh, you know, Boeing is an interesting company to see how they do software because, um, I guess most

425
00:31:33,960 --> 00:31:39,020
people know them for airplanes, which, you know, important that that stuff works. Uh,

426
00:31:39,020 --> 00:31:43,960
and also is a huge enterprise managing the supply chain and all the contractors, let alone your

427
00:31:43,960 --> 00:31:48,820
own people and the parts to do it. So they have big complicated problems, but they also do, uh,

428
00:31:48,860 --> 00:31:53,300
you know, defense contracting, which has to be like regulated and secure. So, you know,

429
00:31:53,320 --> 00:31:56,640
they're one of these companies that sort of like, if they can do it, what's your problem?

430
00:31:57,200 --> 00:32:01,940
Um, and the other, so they're, they're just a good case in general or company in general to see how

431
00:32:01,940 --> 00:32:06,720
they're improving the way they do software. And then also last year at SpringOne platform, uh,

432
00:32:06,720 --> 00:32:11,660
Nikki Allen from there, she gave a, um, she gave a talk. It was pretty short keynote. I mean,

433
00:32:11,660 --> 00:32:15,920
as, as it should have been, but it was a good sort of like, here we are launching on our initiative

434
00:32:15,920 --> 00:32:21,820
to improve how we're doing software. And she gave a good, um, what I'd call sort of like vision

435
00:32:21,820 --> 00:32:27,580
level, uh, thinking about here's what we want to do and how we want to do it. And some early lessons

436
00:32:27,580 --> 00:32:33,420
of how we motivate people, which, um, I don't know if you're a developer and you hear the word vision,

437
00:32:33,420 --> 00:32:38,120
you probably like tune out and go check, read it or something like that, or read it, however you say

438
00:32:38,120 --> 00:32:44,000
it. Uh, but it is like, it turns out at the enterprise level to be extremely important to, uh,

439
00:32:44,000 --> 00:32:48,000
figure out your vision and your leadership and your management and your teams and then individual

440
00:32:48,000 --> 00:32:53,640
staff contributors to kind of like walk down the higher speaking of MIBs. And so it'll be interesting

441
00:32:53,640 --> 00:32:59,020
to like, uh, I've watched that talk many times from my booklets and stuff, but it'll be interesting

442
00:32:59,020 --> 00:33:04,060
to see, uh, the connection between those two and how those practices are being put into place.

443
00:33:04,060 --> 00:33:09,700
And I think sort of analogously also from last year, uh, there was, there was like a keynote talk

444
00:33:09,700 --> 00:33:14,700
from, uh, I forget his name, but this guy from, uh, is it synchronicity? I think the, uh,

445
00:33:14,880 --> 00:33:19,520
the card synchrony, there you go. I think I have an Amazon card through them, but this,

446
00:33:19,520 --> 00:33:23,460
this person was laying out on the keynote, kind of like the vision of what they were doing at a very

447
00:33:23,460 --> 00:33:28,080
high level thing. And then there were a couple of sessions last year that were, you know, like 40,

448
00:33:28,260 --> 00:33:32,520
50 minute sessions about, uh, how they had done that work. And it was fun to see the connection

449
00:33:32,520 --> 00:33:36,900
between the high level vision of like, we want to shoot towards these, uh, I don't think they call

450
00:33:36,900 --> 00:33:42,160
them KPIs, but these end results, uh, and we're kind of on this journey because of this reason.

451
00:33:42,160 --> 00:33:46,840
And then like, here's how we set up the little cloud downgrades and, and how we connect through

452
00:33:46,840 --> 00:33:50,720
those two things. So you'll make a nice little suite of, uh, talks.

453
00:33:52,020 --> 00:33:57,100
Nice. Yeah. And we have the Boeing CIO, uh, Ted will be on stage for main stage as well this year.

454
00:33:57,100 --> 00:34:02,160
So kind of a progress report and different update on what they're working on. So it'll be nice,

455
00:34:02,160 --> 00:34:06,920
nice bookend to what Nikki did last year. Good. My, uh, I got a couple of spring ones. I,

456
00:34:07,040 --> 00:34:10,540
I pointed out this is SpringOne. So I guess I should make sure I'm picking spring talks. I'm

457
00:34:10,540 --> 00:34:15,920
interested in, which isn't hard. There's a great spring track. Uh, one of them. Yeah. I always

458
00:34:15,920 --> 00:34:20,900
love watching Dave Sire speak. And in one of his talks is how fast is spring? Because I think one

459
00:34:20,900 --> 00:34:26,080
thing that we can worry about is, you know, abstraction on abstraction on abstraction, like

460
00:34:26,080 --> 00:34:30,920
what's the performance penalty? What, what tax am I paying for simplicity? And that's often a

461
00:34:30,920 --> 00:34:34,640
concern. Even, you know, I had a customer asking me last week, like, Hey, if I'm using Kubernetes,

462
00:34:34,640 --> 00:34:39,020
what's my performance drain when I'm hitting the app in there versus bare metal. And that's,

463
00:34:39,020 --> 00:34:44,500
you know, kind of a, sometimes you're not really paying much of a tax, but it's good to understand

464
00:34:44,500 --> 00:34:49,120
those things. You do feel like there's layers of layers of virtualization. So what's the actual

465
00:34:49,120 --> 00:34:53,740
impact? So it looks like Dave's talks in the focus on kind of what, what's all spring doing?

466
00:34:54,020 --> 00:34:58,840
What are some of these preconceptions you may have about slow slowness and how these apps start up and

467
00:34:58,840 --> 00:35:03,440
auto configure. And so he's got some new benchmarks. I've seen him working on some stuff in the Slack

468
00:35:03,440 --> 00:35:07,440
channels. And so I think being able to come in saying like, look, look, spring is actually helping

469
00:35:07,440 --> 00:35:11,820
you build high performance apps. You're not really paying the tax, but here are things to know. So I

470
00:35:11,820 --> 00:35:17,260
think that's really important. So that how fast does spring is one I'm looking forward to. And then

471
00:35:17,260 --> 00:35:23,280
related to spring then is one by guy who is the CEO of sneak, one of our partners. And he's got some

472
00:35:23,280 --> 00:35:27,900
really interesting thoughts on serverless. I've seen him present before. And so, and he's written up some

473
00:35:27,900 --> 00:35:32,180
great stuff as well. So I'm excited that he's coming to the show and he's going to talk about

474
00:35:32,240 --> 00:35:37,520
securing spring functions by breaking in. So again, what does it mean to create a vulnerable

475
00:35:37,520 --> 00:35:41,920
function? Like just because you're using these abstractions doesn't absolve you of some

476
00:35:41,920 --> 00:35:46,780
responsibility for security. So what are the weaknesses in things like serverless apps and

477
00:35:46,780 --> 00:35:51,160
apps and functions? And how do you avoid those mistakes? And what do you have to think about

478
00:35:51,160 --> 00:35:55,280
with dependencies or whatever, all those sorts of things. So serverless doesn't mean I don't worry

479
00:35:55,280 --> 00:36:00,080
about security anymore. So this talk from Guy and thinking about spring functions, I think will be pretty

480
00:36:00,080 --> 00:36:04,720
compelling. Yeah, there's probably there probably shouldn't ever be a movement called security list.

481
00:36:05,360 --> 00:36:09,760
That's probably I hope not something to go for. I don't know, maybe maybe a Hello

482
00:36:09,760 --> 00:36:13,840
world app could be security list. But I'm sure there's some way that could be exploited as well.

483
00:36:16,160 --> 00:36:23,520
Well, so I'm going to save the one with the longest title for last. But I think the runner up for

484
00:36:23,520 --> 00:36:29,280
longest title of talk that looks interesting. It's called buckets, funnels, mobs and cats. Now they're

485
00:36:29,280 --> 00:36:35,440
missing that last comma before mobs. I forget if that's a Cambridge Oxford or Harvard comma. But maybe I

486
00:36:35,440 --> 00:36:43,040
should put that in there. That's just gonna drive me crazy. All right, buckets, funnels, mobs and cats

487
00:36:43,040 --> 00:36:48,720
or colon. See, this is my kind of title, how we learned to love scaling apps to the cloud. Now this is

488
00:36:48,720 --> 00:36:54,880
from three of the people on our application transformation team. And you know, it just promises

489
00:36:54,880 --> 00:37:01,280
to be about that, how how how they took some legacy applications and started working or, you know,

490
00:37:01,280 --> 00:37:05,840
legacy is always a weird word, some existing applications, sure, and started transforming

491
00:37:05,840 --> 00:37:11,360
it around and tips and tricks they had from it. And so I think I think that's always a that's that's

492
00:37:11,360 --> 00:37:17,600
always an excellent talk, topic to see people going over. And then there's also a another another

493
00:37:17,600 --> 00:37:22,320
application that looks like it's a way. I mean, another session called rethinking legacy and

494
00:37:22,320 --> 00:37:28,640
monolithic systems. See, that one's straightforward. And it looks like it's going to be going over how

495
00:37:28,640 --> 00:37:34,480
to apply domain driven design to basically pull apart your monoliths, which, you know, when you

496
00:37:35,920 --> 00:37:41,360
sort of I mean, not really all the way back to like Michael Feathers, like dealing with legacy code,

497
00:37:41,360 --> 00:37:48,000
a lot of what you're doing to what would be the opposite of legacy? I don't know on legacy.

498
00:37:49,600 --> 00:37:54,080
Anyways, a lot of what you're trying to do when you're trying to rejuvenate your legacy applications

499
00:37:54,080 --> 00:38:00,080
is breaking them apart and finding finding ways to back to the feathers book, how to test things so

500
00:38:00,080 --> 00:38:05,680
you can change them. So finding the scenes where you break things, break them in a good way, split them.

501
00:38:06,800 --> 00:38:11,520
And I think I think a lot of why something like domain driven design is so helpful is it's

502
00:38:11,520 --> 00:38:17,040
that exact kind of architectural science, so to speak, how would we, how would we come up with a

503
00:38:17,040 --> 00:38:23,360
method to divide an application with components? And then the method that we want to use, as far as

504
00:38:23,360 --> 00:38:30,240
I understand the voodoo of data driven design is from a, maybe not an end user, but from a business

505
00:38:30,240 --> 00:38:36,000
perspective, what are the different components that this business has? And then let's directly,

506
00:38:36,000 --> 00:38:40,560
as directly as possible, divide our system up into those business components.

507
00:38:41,520 --> 00:38:45,280
You know, and then that contrast with like, you could also divide your system up into

508
00:38:46,160 --> 00:38:51,680
technical components, like, I don't know, the three tier application layer where you've got your data

509
00:38:51,680 --> 00:38:56,720
layer, your controller layer, and your UI layer, and then all of the layers in between for things.

510
00:38:57,360 --> 00:39:02,880
So I think, I think when I look at look at how people are doing application modernization,

511
00:39:02,880 --> 00:39:07,200
a lot of it involves putting a domain driven design in there. So these, these two talks together

512
00:39:07,200 --> 00:39:09,760
should be some interesting fodder to chew over.

513
00:39:09,760 --> 00:39:12,640
Good. What else do I have? So I picked one as well.

514
00:39:12,640 --> 00:39:17,360
Then we think of customer stories, automation and culture changes for 40 million subscriber

515
00:39:17,360 --> 00:39:22,880
platform operations, but it's the story of Yahoo Japan. So I haven't heard a ton about them,

516
00:39:22,880 --> 00:39:28,800
but they are, you know, Yahoo Japan supports like a third of the Japanese population. They have tons

517
00:39:28,800 --> 00:39:33,280
of services, most of them on PCF. So they have some really interesting stories that just candidly,

518
00:39:33,280 --> 00:39:38,800
I haven't always heard a ton about. So interested just to hear about the non-traditional stories that,

519
00:39:38,800 --> 00:39:42,480
you know, we love our, kind of our flagship customers at Pivotal, but, but frankly,

520
00:39:42,480 --> 00:39:45,920
I like hearing completely fresh stories from folks who've been using this for a while,

521
00:39:45,920 --> 00:39:50,560
that just haven't been as public with their consumption. So looking forward to that talk.

522
00:39:50,560 --> 00:39:55,920
And then as we think about the Kubernetes track, another one I flagged was cloud-native

523
00:39:55,920 --> 00:40:00,800
streaming platforms. What's it mean to run Kafka on PKS? You know, we've got folks from Confluent,

524
00:40:00,800 --> 00:40:05,840
as well as Pivotal talking about Kafka and PKS and what does it mean to run kind of, again,

525
00:40:05,840 --> 00:40:09,840
these complex platforms on something like Kubernetes, which is where it makes a lot of sense.

526
00:40:10,560 --> 00:40:15,440
One I didn't flag, but I'm also interested in is the one we have that's about running Pivotal

527
00:40:15,440 --> 00:40:21,280
Greenplum on PKS. What does it mean to actually run an enterprise data warehouse on containers? And what

528
00:40:21,280 --> 00:40:25,760
does it mean to engineer for that? What do you have to consider? Frankly, the, or candidly,

529
00:40:25,760 --> 00:40:30,960
the tech preview just hit Pivotal on Friday. So if you want to mess around with Kubernetes and

530
00:40:30,960 --> 00:40:35,920
Greenplum, you can actually do that right now, kind of leading up to the conference. So I think I'm

531
00:40:35,920 --> 00:40:40,800
interested in seeing these more complex platforms come to Kubernetes, not just custom apps, which still

532
00:40:40,800 --> 00:40:45,040
will probably make a lot of sense for Cloud Foundry and Pivotal application service. But what does it

533
00:40:45,040 --> 00:40:50,560
mean to run a streaming platform like Kafka or a warehouse like Greenplum on PKS? I think there's

534
00:40:50,560 --> 00:40:57,040
some things for us to learn there. You know, on the way over here, I saw the new Pacific Rim movie.

535
00:40:57,040 --> 00:41:04,480
I think it's called Uprising. Yeah. And it, you know, people like to use Voltron as an example of

536
00:41:04,480 --> 00:41:08,000
things coming together. But I think there's a potential thing in there. There's this like,

537
00:41:08,960 --> 00:41:13,920
I don't know, it's, it's, it's distressingly analogous to the, I forget the name of it,

538
00:41:13,920 --> 00:41:20,800
but the new Star Wars movie, you know, with like, not, not like this Han Solo one or the rogue one,

539
00:41:20,800 --> 00:41:25,680
I forget what the new series is called. But you know, you have sort of like, you know, this,

540
00:41:25,680 --> 00:41:30,720
this sort of orphan girl who's developed her own, not giant robot, but I could, they call them

541
00:41:30,720 --> 00:41:35,040
Jaegers. Right. I don't know why they call them Jaegers. There's probably some reason

542
00:41:35,040 --> 00:41:39,680
because they're trying to be global in their movie stuff. They got all the great cultures.

543
00:41:39,680 --> 00:41:46,320
And I don't know if they have Latin America in Pacific Rim, but whatever. Anyways, she creates

544
00:41:46,320 --> 00:41:51,760
her own like little robot out of parts that she's found, which is kind of similar to a DIY platform.

545
00:41:51,760 --> 00:41:57,360
But then there's the very well-made fit together gigantic Jaegers, which have these big booming voices.

546
00:41:58,000 --> 00:42:01,680
And, and so I think that's, that's like, I think you and I have like observed this over

547
00:42:01,680 --> 00:42:04,880
time and it's kind of like the standards we were talking about, but there's all these different

548
00:42:04,880 --> 00:42:10,320
parts that are like coalescing together into like a nice, you know, big chunk of Jell-O with the

549
00:42:10,320 --> 00:42:14,800
little fruit suspended in it. And that's evolving more and more. And there's, there's a couple other

550
00:42:14,800 --> 00:42:22,480
talks about, you know, hey data, you might want that in your application. That'll be interesting to look at.

551
00:42:22,480 --> 00:42:28,160
So my final one, and this is the one with the longest title by I think maybe five or six characters.

552
00:42:29,040 --> 00:42:34,480
And then there's another one related to this, but it's, let me take a breath here. Building digital

553
00:42:34,480 --> 00:42:40,240
capabilities in the energy sector, leveraging agile processes and cloud technologies. And this is, this

554
00:42:40,240 --> 00:42:47,680
is from Singapore power. And as always, I enjoy hearing what actual enterprises or organizations are

555
00:42:47,680 --> 00:42:53,440
doing. But I think also the other reason I'm, I'm eager to see this one is we have, we have a lot of

556
00:42:53,440 --> 00:43:00,480
customers who are industrial power company, IOT people, but we don't, we only have a handful of

557
00:43:00,480 --> 00:43:06,160
them that seem to publicly talk about it. And so there's a lot of industrial companies out there and

558
00:43:06,160 --> 00:43:11,680
a lot of interest in IOT. So anytime there's something like this that comes up, you know, a power company

559
00:43:11,680 --> 00:43:16,880
sort of hits all of those, those things. Uh, it's really good to like, see what they're doing and

560
00:43:16,880 --> 00:43:22,880
how they're, uh, you know, whether they're doing IOT stuff or planning out or strategizing it. And

561
00:43:22,880 --> 00:43:28,480
also just dealing with like physical stuff, like a power grid and how those industries are evolving.

562
00:43:28,480 --> 00:43:35,040
I think those are fascinating to see what happens. Cause you know, um, it was, uh, over my software

563
00:43:35,040 --> 00:43:41,280
defined interviews podcast, I talked with John Mitchell at Duke energy. It seems like a long time ago now.

564
00:43:41,680 --> 00:43:46,560
Uh, but what's interesting, at least in the U S about that industry, as he was saying is that

565
00:43:46,560 --> 00:43:51,360
traditionally they've used a lot of off the shelf software. So, and I imagine, I don't know who it's

566
00:43:51,360 --> 00:43:57,600
from, but, um, package software to manage grid energy sector stuff. And what he was saying is

567
00:43:58,240 --> 00:44:04,240
the, uh, the speed at which that software innovates, for example, to give you mobile apps just wasn't

568
00:44:04,240 --> 00:44:09,440
fast enough for them. And so probably I'm guessing globally, it's that same way that people have been using

569
00:44:09,440 --> 00:44:15,360
vertical specific software and I don't know, power company management. And, uh, as those companies

570
00:44:15,360 --> 00:44:19,920
want to evolve and do all this, like IOT grid management stuff, they're, they're finding that

571
00:44:19,920 --> 00:44:24,240
they need to write their own software for it. So this is probably like a common pattern that plays

572
00:44:24,240 --> 00:44:29,040
over and over again, that these companies need to, uh, improve the way they do software. So that one,

573
00:44:29,040 --> 00:44:34,800
it'll be fun to see if, uh, it delivers on my hopes and dreams. And, and then, uh, since that's from

574
00:44:34,800 --> 00:44:40,800
Singapore, there's another just transformational one, uh, from DBS, uh, Singapore bank, uh, going

575
00:44:40,800 --> 00:44:45,920
over the traditional things in a good way that are nice to see of how we, we basically wanted to

576
00:44:46,800 --> 00:44:52,000
go digital. If you will, we wanted to have a more, you know, just better software. And it looks like

577
00:44:52,000 --> 00:44:56,400
it'll go over the, uh, the strategy that they put in place, thinking through like what types of

578
00:44:56,400 --> 00:45:01,360
applications they would do. And as always, uh, things that worked for us as we tried to get more of

579
00:45:01,360 --> 00:45:07,520
that, uh, as we used to say, Silicon Valley mindset or whatever. But, uh, so we have at least,

580
00:45:07,520 --> 00:45:11,360
there's probably some more, but there's at least two people coming over from Singapore to talk,

581
00:45:11,360 --> 00:45:15,120
uh, which, which is great. It's always good to find an excuse to go over there and get some crabs

582
00:45:15,520 --> 00:45:18,160
and also just meet with the, uh, super friendly people there.

583
00:45:18,560 --> 00:45:21,760
Yeah, no, I mean, one of the goals for the show this year was also to be a little more

584
00:45:21,760 --> 00:45:27,200
international and not so us centric. So excited. We have rabble bank on stage for main stage. We have

585
00:45:27,200 --> 00:45:32,480
DBS also doing a main stage talk. And, you know, again, I think it just, it brings not only diversity

586
00:45:32,480 --> 00:45:37,040
in terms of use cases, but in terms of just, you know, the cultural background and what goes into

587
00:45:37,040 --> 00:45:41,520
your choices and look, is DevOps trickier here versus there because of some other sort of

588
00:45:41,520 --> 00:45:46,320
inbuilt or traditional thing. I love that, right? That's, that's, it's not all just a roadmap from

589
00:45:46,320 --> 00:45:51,520
here's how you go from A to A to Z. It's going to zig and zag based on all sorts of characteristics.

590
00:45:51,520 --> 00:45:56,400
So I love when we have a different type of audience there. Yeah. So the last one I had,

591
00:45:56,400 --> 00:46:00,480
I think we both had it was, uh, our own Nate Schuda's thinking architecturally, you know,

592
00:46:00,480 --> 00:46:04,400
I've, I've really gotten to enjoy his series on microservices. He's been working on right now

593
00:46:04,400 --> 00:46:10,320
on our blog, you know, book stuff coming out and, you know, just a really a thoughtful technologist.

594
00:46:10,320 --> 00:46:14,800
And so this talk looks like it's focused more on how are we thinking about technology choices

595
00:46:14,800 --> 00:46:18,480
on projects? How are we actually making sure we're, we're factoring in the big picture

596
00:46:18,480 --> 00:46:22,640
when we're making some of these choices and how do we choose things at the right level of maturity and

597
00:46:22,640 --> 00:46:27,040
all those sorts of things that Nate does a good job chewing through. So I'm excited for that talk.

598
00:46:27,040 --> 00:46:31,760
I mean, I always appreciate his take and I think both of us flagging, it's probably a good sign.

599
00:46:31,760 --> 00:46:36,560
It's, it's going to be a good one. Yeah. I think I've seen him give that talk a few times. I mean,

600
00:46:36,560 --> 00:46:42,480
not that one, but you know, an early version of it, uh, coincidentally, when we're kicking around

601
00:46:42,480 --> 00:46:48,400
Europe and, uh, I, he, uh, he, you know, usually I don't like the, uh, the, the one word per slide

602
00:46:48,400 --> 00:46:53,040
thing, but I think he does that pretty well. And, uh, you know, there's a certain entertainment level

603
00:46:53,040 --> 00:46:58,000
of that, but I think as he goes through the talk, he's got, uh, he's got that sort of way of doing

604
00:46:58,000 --> 00:47:02,480
the presentation down and then, you know, you, uh, you accent that every now and then with a funny

605
00:47:02,480 --> 00:47:08,000
picture of sort of failure or celebration. There's never just sort of like, uh, you know,

606
00:47:08,000 --> 00:47:12,320
funny picture where nothing interesting is happening. Just know, just a field of flowers.

607
00:47:12,880 --> 00:47:17,280
That's right. You know, but that would be a fun challenge is to have a, uh, I think we're going

608
00:47:17,280 --> 00:47:24,080
to have ignite talks. It's our, you know, ignite karaoke talks. We should try to get one that is, uh,

609
00:47:24,080 --> 00:47:31,120
every single like windows, like, uh, field background image and just see what people, uh, make with that.

610
00:47:31,120 --> 00:47:34,320
And then the last one could just be like Clippy just sitting there.

611
00:47:34,320 --> 00:47:37,920
And you got to tie it all together with Clippy, you know, that's going to be for Microsoft.

612
00:47:37,920 --> 00:47:38,800
Bob or whatever.

613
00:47:38,800 --> 00:47:42,880
Yeah. See, you clip it together with Clippy. That's, that's, that's how that works out.

614
00:47:43,360 --> 00:47:45,600
Or you could have that. Remember that little dog they had?

615
00:47:45,600 --> 00:47:49,840
That was, that was, yeah. Can I help you with a new resume? Like, yes, you can dog.

616
00:47:49,840 --> 00:47:50,320
Thank you.

617
00:47:53,360 --> 00:47:57,280
Well, I mean, there's a whole lot more, uh, talks that are out there and then, and it's,

618
00:47:57,280 --> 00:48:01,600
it's pretty easy to go look them up. If you just go to SpringOne platform.io.

619
00:48:01,600 --> 00:48:06,720
Um, and, uh, I think are these all the ones that have been announced or there's some that still

620
00:48:06,720 --> 00:48:10,000
haven't been announced yet. Yeah. Good question. We've got a last batch that are

621
00:48:10,000 --> 00:48:13,200
going to be going online soon. We're actually pretty early. A lot of shows don't put the whole

622
00:48:13,200 --> 00:48:17,280
agenda online until a couple of weeks before, but we wanted to give people a chance to plan.

623
00:48:17,280 --> 00:48:21,760
So yeah, the whole agenda will be online in the, in the coming week or so, and then get your ticket

624
00:48:21,760 --> 00:48:25,040
booked and hotel booked and it really should be a pretty wild four days.

625
00:48:25,040 --> 00:48:29,600
Yeah. Yeah. We'll have some good Maryland crabs, all sorts of things. I hope. And, uh,

626
00:48:29,600 --> 00:48:35,600
if you're interested, all of us have discount codes, but if you want to get $2 off, uh, $2,

627
00:48:35,600 --> 00:48:42,320
$200 off, see the monetary conversion. It's got my mind clunking here, but if you want to get $200 off

628
00:48:42,320 --> 00:48:47,920
the ticket, I'll put this in the show notes as well, but you can use the code S one P 200 underscore

629
00:48:47,920 --> 00:48:54,720
Coté. That's my name, C O T E. And, uh, as I'm fond of saying, I think if, if I, if I people uses a

630
00:48:54,720 --> 00:49:00,160
few times, I might get a fancy pin. Now this might be the same pin that you get in your gift bag, but

631
00:49:00,160 --> 00:49:04,560
I'm going to think that it was a reward for all of my effort in getting people to register.

632
00:49:05,120 --> 00:49:10,080
So yeah, if you're interested in all this, just go to SpringOne platform.io and you can check out

633
00:49:10,080 --> 00:49:14,480
all the other sessions. Uh, you know, there's all sorts of fun pictures of people. You should find the

634
00:49:14,480 --> 00:49:19,920
one picture where the guy has drawn some sort of a dinosaur spikes around his eye. That's a,

635
00:49:19,920 --> 00:49:24,880
that's a good one. You don't see that too often. Uh, and, and with that, this has been another

636
00:49:24,880 --> 00:49:29,520
episode of Pivotal Conversations. If you want to find all the, uh, the archives and

637
00:49:29,520 --> 00:49:35,600
the, uh, the shows find an RSS feed you can subscribe to. You can go to soundcloud.com

638
00:49:35,600 --> 00:49:40,800
slash Pivotal Conversations with no space or anything, just one word. Um, and you know,

639
00:49:40,800 --> 00:49:45,840
you can also search around whatever podcast listener you're looking for. And every Thursday,

640
00:49:46,240 --> 00:49:51,840
usually, uh, I put the full show notes. We keep mentioning over on pivotal.io slash podcast.

641
00:49:52,080 --> 00:49:54,640
And with that, we'll see everyone next time. Bye.

642
00:49:57,280 --> 00:50:04,000
The dog was perfect. Perfect. Perfect. Just right. That's right.