1
00:00:00,000 --> 00:00:02,500
Well, I'm here in London for dual purposes.

2
00:00:02,760 --> 00:00:07,200
I was at the FutureStack conference for New Relic on the partner panel.

3
00:00:07,320 --> 00:00:10,520
There was actually a fun discussion of, I thought we were going to have to talk about

4
00:00:10,520 --> 00:00:14,320
how great our partnership is and everything, but they just wanted to know about DevOps.

5
00:00:14,720 --> 00:00:16,240
So that was a lot easier.

6
00:00:17,240 --> 00:00:18,100
Here's a pro tip.

7
00:00:18,160 --> 00:00:21,480
I don't know if you do this, Richard, but you should ask for the questions they're going

8
00:00:21,480 --> 00:00:26,620
to ask ahead of time or the themes, which thankfully I got late last night so I could

9
00:00:26,620 --> 00:00:28,640
think about these DevOps-y things.

10
00:00:29,000 --> 00:00:30,280
Yeah, you were well-prepared.

11
00:00:31,080 --> 00:00:32,200
Always, always.

12
00:00:32,340 --> 00:00:40,620
I prefer to think of it as I was optimizing my margins by just-in-time preparing, as it

13
00:00:40,620 --> 00:00:40,820
were.

14
00:00:41,440 --> 00:00:45,280
But I got them last night, so I had some time on the plane to sort out the answers.

15
00:00:45,400 --> 00:00:47,560
You know, it was the usual exciting things.

16
00:00:48,720 --> 00:00:51,760
What do people start with, automation or development first?

17
00:00:52,000 --> 00:00:54,060
You know, of course, the answer is both.

18
00:00:54,320 --> 00:00:59,420
Otherwise, I said, you know, automation, because if it takes you like six months to ship, all

19
00:00:59,420 --> 00:01:05,160
of your great development is for not using sort of like lean gold-ratany in theory.

20
00:01:05,380 --> 00:01:06,020
Gold-rat-ian?

21
00:01:06,440 --> 00:01:06,800
Anyways.

22
00:01:07,140 --> 00:01:11,200
And then I think the other one was like, what metrics do people use?

23
00:01:12,060 --> 00:01:13,500
And I've kind of forgotten the third one.

24
00:01:13,780 --> 00:01:14,580
I should look that up.

25
00:01:14,840 --> 00:01:15,120
Anyways.

26
00:01:16,060 --> 00:01:18,020
But that's not what I was going to talk about.

27
00:01:18,080 --> 00:01:22,080
I'm also here for a meetup that if you want to go to, you know, if you listen to this

28
00:01:22,080 --> 00:01:25,820
show right when it's released and you live in London, it's tomorrow night, August the

29
00:01:25,820 --> 00:01:26,160
2nd.

30
00:01:26,560 --> 00:01:29,880
On metrics, what Coté has figured out so far.

31
00:01:30,000 --> 00:01:31,100
Yeah, October the 2nd.

32
00:01:31,220 --> 00:01:31,680
Isn't that tomorrow?

33
00:01:31,800 --> 00:01:32,260
I said August.

34
00:01:32,440 --> 00:01:33,380
I thought you had a DeLorean.

35
00:01:33,700 --> 00:01:34,940
No, no, no, no, no.

36
00:01:35,020 --> 00:01:36,400
Man, that would be nice.

37
00:01:37,020 --> 00:01:42,380
You know, that would be a fun episode one day is if you could go back one month, what

38
00:01:42,380 --> 00:01:43,140
would you do differently?

39
00:01:43,480 --> 00:01:44,480
I guess that was two months.

40
00:01:45,180 --> 00:01:45,440
Anyways.

41
00:01:46,700 --> 00:01:52,300
But anyway, so while we were there, some sort of door or fire alarm went off.

42
00:01:53,240 --> 00:01:58,760
And I recall the last, one of the last times I was in London presenting at the register

43
00:01:58,760 --> 00:02:04,180
conference during my talk, a fire alarm went off right before the best joke in the whole

44
00:02:04,180 --> 00:02:04,780
presentation.

45
00:02:05,120 --> 00:02:06,560
And we all had to leave the building.

46
00:02:06,680 --> 00:02:11,800
And then as we were starting, I looked up the TV in my hotel room here and it says, please

47
00:02:11,800 --> 00:02:17,900
be advised that today at 4 p.m. we will be undertaking our weekly planned fire alarm test.

48
00:02:18,360 --> 00:02:23,180
So I don't know what the deal is with me in London, but I really bring the fire alarm

49
00:02:23,180 --> 00:02:25,640
testing when I come to town here.

50
00:02:25,920 --> 00:02:27,160
So people should just prepare.

51
00:02:27,340 --> 00:02:31,640
So if in about 20 minutes you hear a fire alarm, everything's fine.

52
00:02:31,780 --> 00:02:38,280
That's as they say, this test is an essential requirement in order to guarantee your health

53
00:02:38,280 --> 00:02:41,880
and safety with health and safety capitalized for some reason.

54
00:02:42,640 --> 00:02:46,220
So that's just a warning for what's going on.

55
00:02:46,220 --> 00:02:51,580
But last week we were at, we were at SpringOne Platform 2018 in National Harbor.

56
00:02:51,960 --> 00:02:53,040
How did it go for you?

57
00:02:54,060 --> 00:02:54,540
It went well.

58
00:02:54,580 --> 00:02:57,780
We didn't have any fire alarms, but there was a bat in the keynote hall.

59
00:02:57,900 --> 00:03:00,580
So that was arguably the most exciting thing for me for the week.

60
00:03:00,800 --> 00:03:01,100
Really?

61
00:03:01,920 --> 00:03:02,840
Yeah, I saw it.

62
00:03:03,000 --> 00:03:03,840
Like it was pretty awesome.

63
00:03:04,040 --> 00:03:05,640
Like that bat's flown flying overhead.

64
00:03:06,100 --> 00:03:07,600
That was, there was no mistaking it.

65
00:03:07,680 --> 00:03:08,300
That was a bat.

66
00:03:08,580 --> 00:03:12,760
You know, you remember that, you remember that story, that story, that movie, American Beauty,

67
00:03:12,760 --> 00:03:17,980
where there was a guy with a camcorder and plastic bags and how artful they were.

68
00:03:18,500 --> 00:03:22,820
Like I think, I think, you know, a lighter version of that might be like birds in grocery stores.

69
00:03:23,280 --> 00:03:27,500
Like I'm sure that's a phenomenon you have where there's just like a bird in a grocery store all of a sudden,

70
00:03:27,680 --> 00:03:32,880
just kind of sadly flying around, trying to figure out if it's going to like live there for the rest of its life

71
00:03:32,880 --> 00:03:41,420
or like not kill itself bumping into things as it flies out those relatively tiny doors to the rest of the thing.

72
00:03:42,060 --> 00:03:43,800
I was obsessed with his backstory.

73
00:03:44,340 --> 00:03:47,280
Like I really wanted to know, yeah, how did he get there?

74
00:03:47,840 --> 00:03:51,180
Was his future just going to be in that conference hall, just dive bombing speakers?

75
00:03:51,340 --> 00:03:52,900
Like that'd be an amazing life for him.

76
00:03:53,220 --> 00:03:55,280
Hopefully he learned about digital transformation.

77
00:03:56,100 --> 00:03:58,580
Well, I have to if you're going to listen to the SpringOne main stage.

78
00:03:58,700 --> 00:03:59,720
You're left pretty inspired.

79
00:04:00,840 --> 00:04:01,160
Exactly.

80
00:04:02,200 --> 00:04:04,140
So it was a good show.

81
00:04:04,260 --> 00:04:09,600
You know, in the moment, it always feels so frantic and manic and I can't wait for it to kind of be done.

82
00:04:09,840 --> 00:04:11,980
And then by like three days later, I'm like, that was a really good show.

83
00:04:12,080 --> 00:04:12,660
I had a great time.

84
00:04:12,960 --> 00:04:15,920
But it takes like being away from the show to actually appreciate it.

85
00:04:16,020 --> 00:04:16,440
It's true.

86
00:04:16,580 --> 00:04:16,880
It's true.

87
00:04:16,880 --> 00:04:25,900
Yeah, there were several, you know, we had Pivotal Cloud Foundry 2.3 announced and Pivotal Container Service 1.2.

88
00:04:26,080 --> 00:04:32,980
And there's, as always, from your team, there are extensive write-ups of everything that's running around in there.

89
00:04:33,200 --> 00:04:44,440
I was looking at the PCF releases and among many other things, you know, back long ago when I developed, I did J2EE back when there was a 2 in it.

90
00:04:44,640 --> 00:04:50,440
And as I was reading it, I was occurring like, oh, there's all these services in the platform now.

91
00:04:50,700 --> 00:04:56,280
Like when I joined Pivotal like three years ago, I think a lot of PCF, there were services in it.

92
00:04:56,340 --> 00:05:10,220
But a lot of the discussion was, I don't know, operational, sort of like core compute and hooking, you know, a little bit of the networking and hooking components together and building the containerized apps and things like that.

93
00:05:10,220 --> 00:05:23,600
But in recent times, in addition to like, you know, there's a whole slew of security stuff and there's always like some isolation and managing your sort of multi-tenant from the perspective of, you know, spaces and orgs and stuff and PCF.

94
00:05:23,740 --> 00:05:26,960
But each release, there's a lot new features that are in there.

95
00:05:27,700 --> 00:05:34,020
You know, I'm sorry, services that are in there, which, you know, are essentially to some extent middleware that you might have.

96
00:05:34,340 --> 00:05:45,040
But there's also things like, you know, what set me on this, this trail of thinking was that there's a, to disambiguate from container land, there's a task set scheduler in there.

97
00:05:45,400 --> 00:05:48,140
Which I remember, you know, it'd be old man Coté.

98
00:05:48,380 --> 00:05:58,360
I remember back in the day of J2EE, you know, scheduling things was a, it was a difficult but fun task to use.

99
00:05:58,420 --> 00:06:00,740
Like, I think we used like courts or something.

100
00:06:00,920 --> 00:06:01,320
I don't know.

101
00:06:01,500 --> 00:06:06,400
I forget what like the big open source Java scheduler was back then.

102
00:06:06,400 --> 00:06:13,740
But it was like understanding how two-phase commits worked and then also understanding how to tune a JVM.

103
00:06:13,860 --> 00:06:18,760
Those are right there with like understanding how to schedule things and figure out that working.

104
00:06:19,440 --> 00:06:25,080
So anyways, I mean, that's, that's sort of like my major takeaway without detailing the PCF release so much.

105
00:06:25,860 --> 00:06:26,280
Yeah, that was good.

106
00:06:26,320 --> 00:06:28,700
I'm going to be endorsing you on LinkedIn for JVM tuning.

107
00:06:29,060 --> 00:06:31,280
So that's going to be, it's going to be a big day for you today.

108
00:06:31,620 --> 00:06:31,940
Thank you.

109
00:06:31,940 --> 00:06:36,400
But yeah, there was, there was a number of good PCF announcements.

110
00:06:36,400 --> 00:06:39,440
As we talked about, PAS 2.3 or PCF 2.3.

111
00:06:39,560 --> 00:06:43,320
We had, we've had Jared on talking about some of these releases in the past.

112
00:06:43,320 --> 00:06:54,040
But, you know, the CredHub stuff, as you mentioned, the services, like I went to a few CredHub talks and like that's pretty sweet stuff for storing credentials, using it for your apps, you know, even generating certificates now that you can use.

113
00:06:54,160 --> 00:06:57,840
So like those are ancillary services you might not think of that you have to bolt on.

114
00:06:57,840 --> 00:07:05,060
But like, that's just all in there or service discovery or Spring Cloud Dataflow keeps doing some really cool stuff in PCF itself and HealthWatch.

115
00:07:05,540 --> 00:07:06,920
So yeah, it was a nice highlight of that.

116
00:07:06,980 --> 00:07:15,140
And then we had the PKS announcement as well with Amazon Web Services support and multi-master support and a lot of good stuff there.

117
00:07:15,220 --> 00:07:19,580
So yeah, the kind of flagship announcements around PCF, but there were a ton of Spring announcements.

118
00:07:20,260 --> 00:07:23,080
We have a link in the show notes to Spring Tools 4.

119
00:07:23,400 --> 00:07:26,760
This is if you like building Spring apps, but don't want to just use Eclipse.

120
00:07:26,920 --> 00:07:27,840
You can use Atom.

121
00:07:28,040 --> 00:07:29,500
You can use Visual Studio Code.

122
00:07:29,940 --> 00:07:32,120
That's all in these various marketplaces and things.

123
00:07:32,220 --> 00:07:35,160
So a lot of Spring-based announcements, Spring Framework 5.1.

124
00:07:35,860 --> 00:07:56,000
You know, a lot of great things are socket kind of, I saw a story written up today on InfoQ about our socket and we announced that this was this new protocol level thing that works kind of at layer seven, but for more reactive systems developed by Facebook and Pivotal and Netify and kind of these companies coming together to build maybe a more efficient communication protocol versus just straight HTTP.

125
00:07:56,420 --> 00:07:59,720
So a lot of really neat things came out last week that I think surprised some folks.

126
00:08:01,220 --> 00:08:07,980
Yeah, and as I was going over stuff, how is the .NET stuff doing in PCF?

127
00:08:08,060 --> 00:08:12,420
Since you're a Microsoft MVP, you must have an opinion.

128
00:08:13,060 --> 00:08:13,960
Thanks for reminding people.

129
00:08:14,520 --> 00:08:20,260
We did do another Windows update, Windows Server 18.03.

130
00:08:20,400 --> 00:08:21,580
It's not just the versions anymore.

131
00:08:21,660 --> 00:08:23,920
Now they more or less ship Windows Server every six months.

132
00:08:23,920 --> 00:08:26,940
And I believe that the support is only like 18 months.

133
00:08:27,100 --> 00:08:36,400
So you're getting these Windows shops into this world where it's being updated all the time, which is weird for companies still sitting on Windows Server 2003 or 2008 or these versions.

134
00:08:36,500 --> 00:08:40,620
So the fact that we bake it into the platform and just roll it out there with no downtime is nice.

135
00:08:40,900 --> 00:08:42,240
So a lot of good improvements there.

136
00:08:42,320 --> 00:08:50,340
I actually moderated a panel with a woman from Fiserv and a fellow from Magenic, the consulting firm, kind of talking about their transformation with .NET.

137
00:08:50,340 --> 00:08:55,500
And the Magenic fellow was dogging me a bit that there wasn't even more .NET content at SpringOne.

138
00:08:55,660 --> 00:08:58,060
So we've got to up our game to have even more talks.

139
00:08:58,160 --> 00:09:03,020
But there was a great number of talks this year, more than ever, on .NET, around Windows.

140
00:09:03,480 --> 00:09:07,100
So you'll probably see more and more of that as we think that's a big bet for us.

141
00:09:07,160 --> 00:09:11,120
And our customers seem to like having a decent Windows story that's all managed by the platform.

142
00:09:11,660 --> 00:09:20,220
And, you know, to add to the reasons why I should be endorsed on J2E, you know, I probably already have an endorsement for that being the fancy pants that I am.

143
00:09:20,340 --> 00:09:20,560
We'll see.

144
00:09:20,640 --> 00:09:28,800
It's probably right next to like Styrofoam peanut construction from that era a couple of years ago where people would just make up crazy LinkedIn endorsements.

145
00:09:29,980 --> 00:09:40,520
But anyhow, yeah, I mean, I think one of the other things that's notable is that, you know, of course, the embedded operating system was updated.

146
00:09:41,020 --> 00:09:44,480
And in PKS, the Kubernetes instance was updated.

147
00:09:44,700 --> 00:09:54,000
And, you know, the following kind of falls into a little bit of the, let's call it EBC sort of like, you know, fear sort of inducing stuff.

148
00:09:54,000 --> 00:09:59,960
But there is a good example related I was reading to the need to patch things and keep things updated.

149
00:10:00,740 --> 00:10:12,680
And you might remember last year, maybe you don't, but well, you probably do because you would notice this kind of thing like me that there was, I don't know, I think 15 hours where you couldn't file your taxes in the U.S. with the IRS.

150
00:10:13,500 --> 00:10:20,640
And I came across, I think it came out a couple of weeks ago, I came across a, I don't know, a postmortem.

151
00:10:20,640 --> 00:10:26,880
It's like this fun, well, fun, if you enjoy reading about train wrecks, it's this fun postmortem.

152
00:10:27,000 --> 00:10:32,060
And basically, there was this known firmware problem in a storage array they were using.

153
00:10:32,860 --> 00:10:36,880
And I think they had sort of been notified like a couple of times.

154
00:10:37,020 --> 00:10:43,060
But more importantly, like any large organization, especially in the government, they had outsourced it to someone else.

155
00:10:43,060 --> 00:10:45,480
And for some reason, the outsourcers hadn't updated it.

156
00:10:45,940 --> 00:10:47,720
So, you know, you should patch these things.

157
00:10:48,160 --> 00:10:50,260
I think it was in some sort of deadlock situation.

158
00:10:50,260 --> 00:11:09,340
But it is also, you know, on this little digression here, as I was tweeting about where one puts this kind of commentary, there's kind of a depressing, blameful postmortem in it, where several times they're basically just like, here's the people who screwed up, and we should punish them by extracting cash from it.

159
00:11:09,760 --> 00:11:17,280
And I don't know, it's kind of a read, a good read of like, how not to do things.

160
00:11:17,320 --> 00:11:23,220
Not even the patching part, but there must be something a little better that the analysis they could have done.

161
00:11:23,620 --> 00:11:26,120
So, you know, it's good to make sure you patch things.

162
00:11:28,560 --> 00:11:28,920
Yeah.

163
00:11:29,120 --> 00:11:36,740
So some other things that we had in the news were, we mentioned it last week, but Amazon shipped a beta of their new service brokers.

164
00:11:36,940 --> 00:11:44,340
They built one that helps you connect your PCF apps to, I think it's 18 different Amazon services from machine learning to data services, things like that.

165
00:11:44,580 --> 00:11:45,580
So it was a great partnership.

166
00:11:45,580 --> 00:11:51,000
They were out there in force as well, SpringOne, supporting that and talking about that.

167
00:11:51,080 --> 00:11:56,860
So between PKS and the service brokers, some good stories for Amazon customers using Pivotal technology.

168
00:11:57,380 --> 00:12:01,920
Yeah, and then also, we may have other partners that I'm excluding in this area.

169
00:12:01,920 --> 00:12:23,720
But because I'm at the FutureStack thing, New Relics Conference, they had a little, I don't know, thing they released last week that's basically, you know, if you're familiar with Pivotal stuff, we have this concept of the five S's, which are a way of grouping together the sort of performance and business metrics that, you know, you could call them KPIs.

170
00:12:23,720 --> 00:12:29,700
But the numbers that you're interested in, why you would redo things a pivotal way and what you would track afterwards.

171
00:12:29,880 --> 00:12:35,160
And I, well, I will embarrass myself by saying why I'm not going to embarrass myself.

172
00:12:35,380 --> 00:12:39,160
I don't really have them all memorized, but they all start with S.

173
00:12:39,440 --> 00:12:41,220
Maybe you know them better than I do.

174
00:12:41,320 --> 00:12:45,360
But anyways, I'll let you skirt by by not making you recite them.

175
00:12:46,100 --> 00:12:48,480
But there's a blog post, which I'll link to.

176
00:12:48,860 --> 00:12:53,700
And New Relic did an interesting, they have an interesting, I don't know what they call it, a package.

177
00:12:53,720 --> 00:13:02,860
But basically they have five dashboards and I think a roll-up dashboard that's oriented around metricing and reporting on those five S's, which is great.

178
00:13:03,160 --> 00:13:07,020
It's a good reference of how you would implement these things.

179
00:13:07,080 --> 00:13:14,760
And of course, visuals, which I am planning on stealing from my presentation tomorrow to go over briefly in addition to our own methodology.

180
00:13:15,160 --> 00:13:26,000
And then finally, as people, a few people kindly told me, we're going to have a conference in Austin next year on October 7th and 10th, which is exciting.

181
00:13:26,660 --> 00:13:30,380
You know, as often happens, I no longer live there.

182
00:13:30,840 --> 00:13:36,200
So, you know, it won't be a great advantage, but I'll get to go visit my storage lockers.

183
00:13:36,420 --> 00:13:45,420
I think I'll just sort of like open them up and maybe lie down and just like feel my stuff, see how everything's going there in storage locker land.

184
00:13:45,520 --> 00:13:47,120
I had a little bit of a panic.

185
00:13:47,340 --> 00:13:50,220
I didn't quite remember where I put the keys for my storage lockers.

186
00:13:50,220 --> 00:13:56,060
But then like a good boy, I had put it in my backpack, which is sort of the equivalent of like the purse that I never lose.

187
00:13:56,560 --> 00:13:57,860
So it's in there.

188
00:13:57,940 --> 00:13:58,440
I was smart.

189
00:13:58,540 --> 00:13:59,440
I knew I would lose it.

190
00:13:59,520 --> 00:14:01,720
So I put it in the place I knew would always exist.

191
00:14:02,300 --> 00:14:03,220
Always thinking ahead.

192
00:14:04,280 --> 00:14:07,000
Well, what else did you see happening last week?

193
00:14:07,460 --> 00:14:09,440
Yeah, it was a big news week in general last week.

194
00:14:09,520 --> 00:14:11,820
So it was tough to keep up with everything.

195
00:14:11,820 --> 00:14:17,460
But Microsoft had their giant conference, actually flew down Thursday after SpringOne and went and spoke at that one on Friday.

196
00:14:17,700 --> 00:14:18,160
I saw that.

197
00:14:18,760 --> 00:14:19,100
Yeah.

198
00:14:19,440 --> 00:14:20,580
Yeah, because I make good choices.

199
00:14:20,980 --> 00:14:23,700
But that was they made a number of announcements.

200
00:14:23,700 --> 00:14:28,040
The ones that caught my eye, the one I pointed out here in our show notes was their Cosmos DB.

201
00:14:28,240 --> 00:14:30,500
This is their planet scale, NoSQL database.

202
00:14:30,700 --> 00:14:38,840
They made some cool updates to that, actually adding multi master, meaning you could have this database striped across, let's say, five or six geographies.

203
00:14:38,840 --> 00:14:41,120
And each one is actually a master to read and write.

204
00:14:41,480 --> 00:14:47,060
So you're not just having the sort of lag of like, well, we only write in the US and it eventually replicates to Europe.

205
00:14:47,300 --> 00:14:50,480
No, I could still write it in Europe and it's actually still considered the master.

206
00:14:50,480 --> 00:14:54,120
So some really neat stuff there from a database perspective.

207
00:14:54,120 --> 00:15:03,660
And then they added an SLA that's actually five nines for read and write, which I don't know if I've seen that in a cloud database in terms of that much availability for both read and write.

208
00:15:03,660 --> 00:15:18,780
So just doing some good stuff in Microsoft land, if you're looking at distributed databases, you know, PCF plug, if you use the Azure service broker, you can connect that easily from your apps, .NET or Java or whatever, from anything running a PCF, which is pretty cool.

209
00:15:18,840 --> 00:15:38,640
You know, on the topic of cloud databases, which comes up every now and then in our literal view, you know how people say that like releasing to production should be boring, by which they mean you should automate as much of it as possible with not only automation stuff, whether that be a platform or other things.

210
00:15:38,640 --> 00:15:51,060
But then also standardize on your practices and standardize to the extent that maybe you don't even think that they are – that you're having to choose something.

211
00:15:51,460 --> 00:15:58,780
Like I was reading some – I forget what it was, but I was rereading some old like, you know, how to do software better stuff.

212
00:15:59,340 --> 00:16:02,940
I think it was in the Puppet DevOps report or maybe it was the Dora one.

213
00:16:03,540 --> 00:16:12,540
And they were saying, you know, it's okay to be sort of lockstep about things you should do because that's what a best practice is, right?

214
00:16:12,540 --> 00:16:22,540
Like if you develop a best practice, there shouldn't be any argument about like, for example, we should probably just not write a file system and use the file system that comes with it.

215
00:16:22,540 --> 00:16:35,340
Anyways, with all of the sort of cloud databases out there, do you think we either are or will quickly approach the point where like databases are no longer like hard or difficult?

216
00:16:35,540 --> 00:16:41,080
Like in the same way that in theory, like deploying to, you know, infrastructure isn't that difficult.

217
00:16:41,080 --> 00:16:48,600
And I ask because it seems like databases have always been like this mystery and this like difficult thing.

218
00:16:48,800 --> 00:16:56,360
But maybe if you remove a lot of the tension of having to stand them up and manage them, then they're not such a big deal.

219
00:16:56,660 --> 00:16:57,180
I don't know.

220
00:16:58,420 --> 00:17:02,100
Yeah, I mean, it's interesting thought there.

221
00:17:02,180 --> 00:17:03,620
I think there's two parts to it though.

222
00:17:03,620 --> 00:17:12,480
I guess there's the complexity of managing them and using them, you know, standing them up, maintaining them, patching them, which has clearly gotten simpler in a cloud world.

223
00:17:12,560 --> 00:17:16,100
I mean, you and I can go provision a global scale database in the next three minutes.

224
00:17:16,280 --> 00:17:17,420
Like that's amazing, right?

225
00:17:17,480 --> 00:17:20,200
It's automatically patched and it's replicated and backed up.

226
00:17:20,320 --> 00:17:26,680
Like those sort of traditional DBA tasks in terms of operations have largely started to disappear and even on premises.

227
00:17:26,860 --> 00:17:28,140
Now you still need certain things.

228
00:17:28,240 --> 00:17:29,320
You still may need an index.

229
00:17:29,440 --> 00:17:32,360
You still may need, you know, certain components that you operate.

230
00:17:32,360 --> 00:17:34,780
But that sort of stuff has gotten simpler.

231
00:17:34,900 --> 00:17:40,620
I wonder on the app dev side though, like is that still, you know, it still may be tricky on what's the shape of my data.

232
00:17:40,920 --> 00:17:43,840
Should I write a stored procedure or put my stuff in code instead?

233
00:17:44,220 --> 00:17:50,000
Or, you know, how do I change a data field and go from full name to split it to two fields to first name, last name?

234
00:17:50,020 --> 00:17:51,640
How do I refactor that in my data?

235
00:17:51,740 --> 00:17:53,020
Like that stuff's still not trivial.

236
00:17:53,300 --> 00:17:54,400
There's patterns for it.

237
00:17:54,660 --> 00:17:57,440
But I haven't seen that get easy yet, if you will.

238
00:17:57,440 --> 00:18:01,540
No, yeah, that's a good cutting through all my babbling there.

239
00:18:01,620 --> 00:18:16,500
Because that was kind of like the analogy I was thinking of is like you could say like with all your cloud stuff that doing all of your, as I would call it, sort of like more lock level like management and operations and release management.

240
00:18:16,500 --> 00:18:22,780
You can remove that from the overall like software delivery pie of suffering, right?

241
00:18:22,800 --> 00:18:27,520
So you can kind of like, you can kind of like take that effort out so you can spend effort on other things.

242
00:18:27,520 --> 00:18:34,100
And then, however, it's still difficult to like design good software and make good product, right?

243
00:18:34,160 --> 00:18:37,380
Like there's no, I don't know, we don't have a build pack for that.

244
00:18:37,540 --> 00:18:40,200
That's just like pops out good software on the other end.

245
00:18:40,380 --> 00:18:51,740
And it seems like in a similar way, like just as you were saying, as there are more public cloud databases, or I guess like managed down in the private cloud.

246
00:18:51,740 --> 00:19:01,180
Let's just say databases that are managed in a cloud way, wherever they are on the side of the firewall, like it removes all of that nonsense from our pie of suffering.

247
00:19:01,420 --> 00:19:04,420
And then you can worry about like schema design.

248
00:19:04,680 --> 00:19:05,080
I don't know.

249
00:19:05,260 --> 00:19:10,040
Whatever the equivalent of design is in a database, and you can spend much more effort on that.

250
00:19:10,660 --> 00:19:12,680
But, you know, I'm not a database person.

251
00:19:12,900 --> 00:19:19,900
We should get those data cow people or like, you remember, you ever read that, all the agile database stuff that Scott Ambler wrote?

252
00:19:20,020 --> 00:19:21,700
That was kind of fun.

253
00:19:22,200 --> 00:19:30,400
Yeah, I attended a talk of his back at the agile conference this summer, and he was talking actually about refactoring databases and not using that as an excuse to slow down velocity.

254
00:19:30,640 --> 00:19:37,060
So there's a good movement at hand, I think, to make sure we demystify kind of agile data as part of the pipeline.

255
00:19:37,160 --> 00:19:44,120
All that automation you just mentioned, like it doesn't matter if I automate all the app delivery if I'm still waiting for a DBA team to run a script to update a field.

256
00:19:44,440 --> 00:19:46,440
Like then I might as well not automate the rest of it.

257
00:19:46,500 --> 00:19:47,020
What's the point?

258
00:19:47,240 --> 00:19:47,460
Exactly.

259
00:19:47,460 --> 00:19:49,080
I think that's still my constraint.

260
00:19:49,700 --> 00:19:55,140
So, yeah, it's good to see more and more about that, although I don't see a ton of simple patterns always evangelize.

261
00:19:55,200 --> 00:19:56,200
We could probably do better there.

262
00:19:57,000 --> 00:20:05,620
Yeah, you know, I think his book on dad or disciplined agile deliveries, the only book I've seen where there's mind maps sort of printed as the overview, which is nice.

263
00:20:05,680 --> 00:20:07,580
Speaking of, how's your book going?

264
00:20:08,600 --> 00:20:12,040
The first draft I delivered the Friday before SpringOne.

265
00:20:12,040 --> 00:20:13,300
Wow, what a machine.

266
00:20:13,800 --> 00:20:14,520
I'm a monster.

267
00:20:14,660 --> 00:20:16,380
Luckily, it's one of those smaller O'Reilly books.

268
00:20:16,460 --> 00:20:18,660
So I'm not taking credit for like a 500 page monster.

269
00:20:18,820 --> 00:20:19,640
It's like 100 pages.

270
00:20:19,920 --> 00:20:20,600
Yeah, that's good.

271
00:20:20,680 --> 00:20:21,080
That's good.

272
00:20:21,260 --> 00:20:21,480
Okay.

273
00:20:21,680 --> 00:20:24,400
But yeah, so I'm waiting for the first brutal reviews back.

274
00:20:24,400 --> 00:20:27,820
And then I got to, of course, make like 30 updates because technology keeps changing.

275
00:20:27,940 --> 00:20:28,900
Thanks a lot, technology.

276
00:20:29,280 --> 00:20:29,480
Yeah.

277
00:20:29,840 --> 00:20:30,640
Brutal updates.

278
00:20:31,000 --> 00:20:32,140
That's always exciting.

279
00:20:32,760 --> 00:20:45,780
Well, you were suggesting, rightly so, that we should give a summary other than sort of the releases of like some of our highlights and, as they say, takeaways from SpringOne platform last week.

280
00:20:45,780 --> 00:20:53,560
Now, I didn't do, despite being here at the FutureStack thing, I didn't attend like the partner award thing or sort of conference.

281
00:20:53,560 --> 00:21:00,000
Although, I did get a challenge code from Nima, our partner person, a challenge coin.

282
00:21:00,640 --> 00:21:02,560
So I'll have to do something with that.

283
00:21:02,600 --> 00:21:09,780
It seems like a good paperweight, but I'm not sure a situation is ever going to come up where I need to pull out a challenge coin so I can sort of pass muster.

284
00:21:09,840 --> 00:21:10,220
We'll see.

285
00:21:10,320 --> 00:21:11,740
I should have brought it to this event, I guess.

286
00:21:11,820 --> 00:21:12,340
I've failed.

287
00:21:12,920 --> 00:21:13,380
Come on.

288
00:21:13,720 --> 00:21:14,240
But how?

289
00:21:15,160 --> 00:21:17,640
Yeah, I can bet it's not in your man purse backpack there.

290
00:21:17,780 --> 00:21:18,520
There you go.

291
00:21:18,720 --> 00:21:19,340
Fire alarm.

292
00:21:19,340 --> 00:21:19,760
Fire alarm.

293
00:21:19,760 --> 00:21:23,860
So while I mute this, why don't you tell me the partner's part?

294
00:21:24,580 --> 00:21:24,800
Sure.

295
00:21:25,480 --> 00:21:28,720
Yeah, so this SpringOne, we had our first ever partner awards.

296
00:21:29,020 --> 00:21:33,260
So we gave out a couple dozen or so awards to different partners.

297
00:21:33,440 --> 00:21:35,660
You know, SI partner of the year, do the right thing.

298
00:21:35,980 --> 00:21:41,660
A number of things to just demonstrate things that have worked well with our partnerships, kind of customer impact and the like.

299
00:21:41,760 --> 00:21:46,540
So we highlighted a number of those, sent out a press release, put together some great material.

300
00:21:46,620 --> 00:21:48,080
And it seemed to be well received.

301
00:21:48,080 --> 00:21:52,780
We have an amazing partner ecosystem at this point of system integrators, of software vendors.

302
00:21:53,620 --> 00:21:54,760
And so it was good to highlight those.

303
00:21:54,840 --> 00:22:02,020
We had a partner off-site on the first day of the conference, or I guess day zero on Monday, just bursting at the seams, kind of working together.

304
00:22:02,140 --> 00:22:05,700
How do we help these partners accelerate what they're doing with us?

305
00:22:05,760 --> 00:22:09,540
How do we learn what they need from Pivotal and from customers?

306
00:22:09,880 --> 00:22:11,660
So that was extremely successful.

307
00:22:11,660 --> 00:22:17,800
It was rewarding to see all the hard work that our partner team puts into building a great ecosystem, kind of come to fruition at the conference.

308
00:22:17,880 --> 00:22:22,460
The show floor was bustling with all the partner booths who seemed to be packed at a lot of times.

309
00:22:22,700 --> 00:22:32,580
And it was, you know, I walked around, I think the last day of the conference, just to kind of shake hands and talk to each person, find out what they had kind of taken from the conference, each of the partners at the booth.

310
00:22:32,580 --> 00:22:39,500
So it was just a good partner show, and I think it was probably the best we've done so far and a good indicator that this thing might actually stick.

311
00:22:40,360 --> 00:22:40,920
That's right.

312
00:22:41,360 --> 00:22:47,520
Well, you know, the conference is actually, I guess, did it start on Saturday?

313
00:22:47,880 --> 00:22:49,600
I forget, or was it on Monday that it started?

314
00:22:49,880 --> 00:22:51,520
Pretend started on Monday, obviously.

315
00:22:51,600 --> 00:22:51,900
That's right.

316
00:22:52,180 --> 00:22:53,480
Pre-team got there Friday.

317
00:22:53,680 --> 00:22:54,660
But yeah, Sunday was there.

318
00:22:54,780 --> 00:22:55,800
Monday was the real first day.

319
00:22:55,800 --> 00:22:59,240
And, you know, sometimes there's like workshops on Sunday or workshop days.

320
00:22:59,760 --> 00:23:05,080
But on Monday, there was an analyst day, which I have to admit, I did not attend all of.

321
00:23:05,660 --> 00:23:11,960
But the two sections that I made sure to attend were the customers talking, which is always interesting.

322
00:23:12,540 --> 00:23:17,300
And then the, you know, the executive Q&A is always fun to see what analysts ask.

323
00:23:17,360 --> 00:23:20,060
And then I guess also what my coworkers answer.

324
00:23:20,460 --> 00:23:21,180
That's fun.

325
00:23:21,980 --> 00:23:28,440
But I think, you know, some of the things are under NDA and not in an analyst event.

326
00:23:29,080 --> 00:23:34,160
But later on, there was a keynote by one of them, the Rabobank guy.

327
00:23:35,140 --> 00:23:38,960
You know, now I'm much more familiar, a large Dutch bank.

328
00:23:39,640 --> 00:23:57,280
And, you know, I think what was interesting about his keynote and what he was talking about in the analyst day was the sort of like general cultural sort of path that they went down to have things to get pivotal Cloud Foundry in there.

329
00:23:57,280 --> 00:24:07,140
Like his his his his posing of it was that essentially they were convinced of like doing Agile and DevOps and they kind of had that under control.

330
00:24:07,400 --> 00:24:15,260
And I don't know if it's unlike a lot of people that we work with, but it's certainly not maybe the majority of people, at least that I know of.

331
00:24:15,320 --> 00:24:26,420
But is very they were very interested in just looking at pivotal Cloud Foundry as just like the tool they would use to accomplish this, which which I think was an interesting pull in that they were doing.

332
00:24:26,500 --> 00:24:34,780
And also, you know, I'll have to I'll have to go look at look at his his keynote again to make sure it matches the tone that he had in the analyst day.

333
00:24:34,780 --> 00:24:42,840
But I would say if they're you know, there are a few better representations of like the Dutch humor I've encountered than the one he was doing.

334
00:24:42,900 --> 00:24:52,160
He's very like, very not like dry, like English people, but he just sort of like marches through some jokes without necessarily waiting for you to catch up.

335
00:24:52,400 --> 00:24:55,180
So you got to be pretty quick that like, oh, he's joking right now.

336
00:24:55,480 --> 00:24:57,760
And there were some good zingers in there.

337
00:24:58,180 --> 00:24:59,920
That's funny. Yeah, I thought he had a great talk.

338
00:24:59,960 --> 00:25:02,780
And it was you mentioned this elsewhere, too.

339
00:25:02,780 --> 00:25:11,360
Like, again, this idea of just tools, I think I just heard over and over again, the U.S. Air Force did this, a bunch of others of just the sort of like we had to do a few things to make this successful.

340
00:25:11,480 --> 00:25:12,660
This wasn't just any product.

341
00:25:12,840 --> 00:25:16,620
And like, although that like no one product fixes anything, that's insane.

342
00:25:16,700 --> 00:25:17,420
No one platform.

343
00:25:17,420 --> 00:25:20,280
And it was that way of working sort of stuff.

344
00:25:20,360 --> 00:25:21,240
I actually had jotted down.

345
00:25:21,320 --> 00:25:26,540
I was reading transcripts today and there was a Boeing discussion on kind of moving fast and automation.

346
00:25:26,540 --> 00:25:36,500
One of the panelists said, you know, quoting here, the hardest part about the transformation was actually the fact that the users we were interviewing couldn't comprehend a world of actual automation and self-service.

347
00:25:36,500 --> 00:25:45,560
Like it was so beyond there to think, wait, you're going to do all this stuff like you had to even just sell this idea of working in a different way, ignoring the technology.

348
00:25:46,340 --> 00:25:53,200
So I thought that was always a good undercurrent, that this is a complimentary set of pieces of how do you run technology well?

349
00:25:53,320 --> 00:25:59,280
How do you rethink how maybe you develop software and do product design stuff and automate the path to production?

350
00:25:59,480 --> 00:26:02,080
And yes, there's tools in tech that makes a ton of sense there.

351
00:26:02,160 --> 00:26:08,080
But if you don't come in it with the right mindset or have the right empathy for your customers, it's all just going to be disappointing shelfware.

352
00:26:08,480 --> 00:26:09,900
And it was nice to hear that.

353
00:26:10,300 --> 00:26:10,740
Yeah, yeah.

354
00:26:10,820 --> 00:26:28,100
I mean, that was a theme that came up here and there was the, to put it in an extreme way, like once you get things optimized as far as like not, like kind of we were talking about earlier with databases, analogously that you don't have to worry about automating this or releasing it or whatever.

355
00:26:29,720 --> 00:26:32,380
There's often a phase you go through where no one believes you.

356
00:26:33,200 --> 00:26:44,000
And so, and so you've got to like, you've got to like emphasize to them that it's sort of like actually real and, and these things happen, which I think, you know, you, you, you mentioned the Air Force.

357
00:26:44,120 --> 00:26:47,640
I mean, they had, they had a pretty good update to their, their ongoing story.

358
00:26:47,720 --> 00:26:50,520
What, what, what, what, what did you think about their talk?

359
00:26:50,960 --> 00:26:54,060
I thought that was, you know, interesting, inspiring.

360
00:26:54,220 --> 00:26:59,400
It's fun to see how they're trying to improve, you know, again, having them on stage talking about the main stage,

361
00:26:59,400 --> 00:27:01,880
talking about their progress and how well they're shipping software.

362
00:27:02,100 --> 00:27:04,960
And for some reason, I don't usually take pleasure in the pain of others.

363
00:27:04,960 --> 00:27:09,540
Like that's not my, my thing, but it was during that talk, it was fun to see somebody tweak.

364
00:27:09,640 --> 00:27:12,340
I'm like, oh my gosh, like the Air Force ships more often than we do.

365
00:27:12,380 --> 00:27:13,060
Like we suck.

366
00:27:13,220 --> 00:27:14,420
And I like that.

367
00:27:14,460 --> 00:27:18,320
Like you're looking at these companies going, wow, like they're doing this.

368
00:27:18,320 --> 00:27:21,660
And I think it was also this reminder that better doesn't equal good.

369
00:27:22,060 --> 00:27:24,320
Like I could be better than I was last year.

370
00:27:24,380 --> 00:27:29,320
I could be now shipping every six months instead of every 12 months, but I need those reminders that that might not be good yet.

371
00:27:29,340 --> 00:27:30,980
I need to look at what good is.

372
00:27:30,980 --> 00:27:33,700
And in this case, Air Force was saying, look, here's our journey.

373
00:27:34,140 --> 00:27:38,240
We're now saving half a million dollars a day on fuel because of this fuel tanker improvement thing.

374
00:27:38,360 --> 00:27:40,460
And hey, we're shipping code so often now.

375
00:27:40,540 --> 00:27:48,580
And then I went to one of the U.S. Air Force breakouts where they were actually putting this in so many PCF and so many remote sites and doing this faster than they'd ever done.

376
00:27:49,360 --> 00:27:52,540
But again, it was still this journey of like, OK, now we have to operate this thing.

377
00:27:52,880 --> 00:27:56,940
What does good look like from a day two perspective, not just getting it up and declaring victory?

378
00:27:57,540 --> 00:28:06,540
So their whole thing at the show, I thought, was fascinating as they talked about what they were trying to do, how they were using software to get better, what that actually meant to their own people,

379
00:28:06,940 --> 00:28:13,220
and how excited their own people were about doing some of this work and getting better at software and not fighting bureaucracy.

380
00:28:13,440 --> 00:28:18,240
So I thought the Air Force team did a really nice job putting their work into perspective as well as what the outcomes were.

381
00:28:18,300 --> 00:28:20,740
They weren't done, but they were showing a nice progress report.

382
00:28:20,740 --> 00:28:27,980
Yeah, I particularly like that because of, I don't know, for numerous reasons other than it's a good idea,

383
00:28:28,260 --> 00:28:36,860
like have studied the Air Force case quite a bit, like finding all the little bits I can and tracking their projects over the past couple of years.

384
00:28:36,980 --> 00:28:42,040
And so, one, it was good just to get an update of what the numbers are and things like that.

385
00:28:42,040 --> 00:28:53,540
And then, as you pointed out, so the original number, essentially, you know, the most famous one they have is this, like, Project Jigsaw, which, of course, is all capitalized and probably stands for something.

386
00:28:54,220 --> 00:28:59,260
They also have, like, great names like Raven and Marauder and these other things.

387
00:28:59,380 --> 00:29:02,580
Marauder is one of the underappreciated words in the English language, I think.

388
00:29:02,580 --> 00:29:09,880
Like, do you remember when there was a muscle car in that tragic period in the late 90s when all American cars looked terrible called the Marauder?

389
00:29:10,360 --> 00:29:14,980
It was basically, like, kind of like a Monte Carlo that was, like, carved down.

390
00:29:15,500 --> 00:29:16,860
It was quite the automobile.

391
00:29:17,360 --> 00:29:26,700
Anyhow, they were going over, originally, when their tanker planner thing came out, just a plan where tankers fly around to refuel jets.

392
00:29:26,900 --> 00:29:37,700
You know, the number was, like, they were saving $284,000 a day in fuel because they optimized the analytics behind it so much because it was no longer a whiteboard.

393
00:29:37,960 --> 00:29:45,300
It was software that they didn't have to put an extra tanker up to account for errors in the analog computation that was happening.

394
00:29:46,100 --> 00:29:59,720
And then, like you pointed out, I think there was further, I'm assuming, further features that they added and sort of, like, an evolution of the problem where they, I can't do the math in my head, but they around doubled the amount of savings that they had.

395
00:29:59,720 --> 00:30:05,240
And if I remember, they also, like, reduced the amount of, like, operators or people needed to run the program.

396
00:30:05,400 --> 00:30:09,740
So maybe they talk about that longer more in the session that I didn't attend.

397
00:30:09,900 --> 00:30:18,960
But I think that kind of story, that sort of year-over-year thing is useful for looking at, that it's not just sort of, you know, this is the other side of the tools thing.

398
00:30:19,020 --> 00:30:25,900
That installing, like, a Pivotal Cloud Foundry or whatever tool you might have, it's not just sort of, like, a one-time boost that you get.

399
00:30:25,960 --> 00:30:36,120
But it really puts in place this thing, as in the case with the Air Force, where every week you can, like, release a feature or two and study it and, slowly is the wrong word.

400
00:30:36,180 --> 00:30:43,240
But to use the idiom, slowly but surely improve the business process that you're applying it to.

401
00:30:43,600 --> 00:30:48,500
Yeah, I love, in one of those breakouts, what they had mentioned is, it was funny the impact that had on culture.

402
00:30:48,500 --> 00:30:55,000
Like, first of all, yes, that they weren't just big banging, releasing something, all moving on to something else, that software's always just shipped.

403
00:30:55,080 --> 00:30:55,740
It's never done.

404
00:30:56,200 --> 00:31:10,920
But what they know, this is that when their other business clients, if you will, I guess there's business clients in the Air Force, that when there's other clients, that when they saw that software was just kind of constantly iterated on, they would actually call up and pull over an airman or an engineer going, like, hey, this isn't working.

405
00:31:11,000 --> 00:31:11,580
Can you sit with me?

406
00:31:11,600 --> 00:31:12,280
Can I show you this?

407
00:31:12,300 --> 00:31:13,640
Because they know it's actually going to get fixed.

408
00:31:13,960 --> 00:31:19,600
It's not like, let me just send it into some faceless help desk where maybe four releases from now in three years, it'll get fixed.

409
00:31:19,680 --> 00:31:22,860
It was, hey, let me call you over or let me give you a feature idea.

410
00:31:23,160 --> 00:31:31,700
Because, again, it was this constant just sense that I will give you new ideas, and those new ideas, if they're good ones, will get reflected fairly quickly here.

411
00:31:31,960 --> 00:31:37,840
And that was completely new to them, but it created actually a new partnership where it wasn't just to get IT in the business, which are terms I hate.

412
00:31:38,160 --> 00:31:40,560
But it was the idea of, like, we're all in on this, right?

413
00:31:40,560 --> 00:31:46,460
We're all trying to make this better, and you've proven to me, like, you've proven that you can take my input and turn that into software.

414
00:31:46,560 --> 00:31:47,760
I thought that was really neat.

415
00:31:47,840 --> 00:31:49,660
It was a cool switch to see them flip.

416
00:31:50,080 --> 00:31:50,920
Yeah, yeah, yeah.

417
00:31:51,040 --> 00:32:02,780
I mean, I think, you know, there's, building out that there's two other things I noticed a lot in the discussion with, let's call them end users or not pivotal people.

418
00:32:03,360 --> 00:32:20,620
At the conference, one of them was, you know, you're kind of alluding to this, is that one of the needs, and the Air Force is, in the talks I give, are always very clear about this because of the, I think it's because of the comp structure that they have and the hiring that they have to do.

419
00:32:21,460 --> 00:32:28,720
And there was some discussion from one of the civilian heads who was speaking on their behalf.

420
00:32:29,000 --> 00:32:31,120
But basically, hiring is really hard.

421
00:32:31,700 --> 00:32:44,040
Like, people who do technical things, you know, the kind of people you would want for programming and operation stuff, it's hard to not only get them, but because of various weird reasons, it's hard to retain them.

422
00:32:44,840 --> 00:32:50,280
Even retaining them beyond just wanting to be in the job, but you can only, like, work for six months or something.

423
00:32:50,920 --> 00:32:58,300
It was one of these situations where it was like, you know, you can't fight City Hall or Congress in this case, just some weird regulation.

424
00:32:58,620 --> 00:33:14,600
But this similar thing came up, you know, whether it was people talking at the analyst day or just customers I would talk with, you know, over lunch or in the hallway, which was, and I mentioned this because I don't take it too seriously, is like, we got to figure out how to, like, hire and retain people.

425
00:33:14,840 --> 00:33:17,140
Like, that's really difficult.

426
00:33:17,500 --> 00:33:30,240
And so part of the joy, I guess, that comes with not doing more Lockheed and Drudge work, the toil, that's one way of making people happier, to retain them and then kind of tell them when we're trying to recruit them.

427
00:33:30,680 --> 00:33:39,100
But also, just showing up to events like this and talking about what we're doing and how we're helping people out is a good recruiting mechanism as well.

428
00:33:39,100 --> 00:33:44,180
I mean, everyone laughs in a keynote when they do this, but, you know, of course they do it.

429
00:33:44,280 --> 00:33:45,160
They're like, we're hiring.

430
00:33:45,500 --> 00:33:46,540
You should come work for us.

431
00:33:47,120 --> 00:34:02,620
And I think that, you know, the other thing that I noticed that kind of you see in the Air Force example and that came up with a lot of the talks and the conversations that I had with people is basically, I mean, I don't know.

432
00:34:02,620 --> 00:34:24,600
This is kind of an obvious thing, but talking with people made me realize it a lot more is a lot of what these organizations are doing is basically becoming a software product-centric company, which I think, you know, forever we've been talking about how, you know, everyone's a software company or whatever, which I'm sure I've said that here.

433
00:34:24,600 --> 00:34:31,920
It always, like, mentally, like, grinds in my head because I'm like, I feel like unless you're selling software as your product, you're not a software company.

434
00:34:32,260 --> 00:34:32,680
Right, exactly.

435
00:34:32,680 --> 00:34:39,760
In the same way that, like, you know, if you're delivering packages, maybe you're not a transport company.

436
00:34:39,860 --> 00:34:40,320
I don't know.

437
00:34:40,660 --> 00:34:51,700
Or I guess the equivalent would be like, you know, we realize that we're an experienced delivery mechanism, but really you're just like the catering for airlines or something, which nothing wrong with catering for airlines.

438
00:34:51,880 --> 00:34:54,080
It's just like maybe you're just catering for airlines.

439
00:34:54,080 --> 00:35:04,380
So anyways, but I think the kind of toned down version of that is a lot of what people are talking through is like, basically, we need to become a product company, which has two effects.

440
00:35:04,480 --> 00:35:10,900
One, you know, we were kind of stumbling through this with like, are there business people in the Air Force or whatever?

441
00:35:11,620 --> 00:35:19,020
The phrasing for this always gets fraught when you cross between for-profit enterprises and mission enterprises.

442
00:35:19,360 --> 00:35:21,580
I don't know how to categorize public sector.

443
00:35:21,880 --> 00:35:25,800
Um, as I just proved, it's hard to use the words.

444
00:35:26,400 --> 00:35:32,360
Anyways, uh, but you know, what you're getting at in both of those organizations is that we're delivering a product.

445
00:35:32,640 --> 00:35:37,660
Uh, and so we should do things in a design oriented way and all the usual agile stuff we talk about.

446
00:35:37,920 --> 00:35:57,520
And one of the things, uh, I was talking with, um, a couple of people about, um, is that also on the other side of it, like if we go up to the mythical C suite or, you know, the, the, the agile side, like we need to get to the point where they understand, um, the tools that are available to them to change their business.

447
00:35:57,560 --> 00:36:04,380
And there's a couple of examples you could think of, like in retail, there's, uh, probably like omni-channel stuff you should look at.

448
00:36:04,440 --> 00:36:04,620
Right.

449
00:36:04,700 --> 00:36:14,300
So on the non-IT side of the house, people should think about like, well, what if we had a mobile phone to buy groceries or whatever, which people do, but it's just a simple example.

450
00:36:14,880 --> 00:36:36,280
Um, but then I think, I think the, uh, you know, the analogous thing I was thinking of was like, probably at some point, like maybe, I don't know when aerosol cans were invented, but maybe in the twenties or something, I'm sure all the way up to like in the shaving care industry, like up to the board level, there was probably some presentation where they were like this new technology called aerosol spray cans.

451
00:36:36,280 --> 00:36:51,000
And, you know, eventually we should get to that point where, uh, the sort of like leadership in a company is understanding somehow this, this, what this technology can do for them as far as like doing weekly releases and doing better design.

452
00:36:51,000 --> 00:36:57,440
And, uh, hopefully over the next few years, that will be sort of like a, uh, I don't know, a more pervasive thing than we have currently.

453
00:36:57,440 --> 00:37:02,900
Cause we're still kind of like, you know, the IT more locks, uh, it seems like to the vast majority of people.

454
00:37:03,760 --> 00:37:04,700
Yeah, that's good.

455
00:37:04,880 --> 00:37:15,240
Yeah. Speaking of the IT more locks, I was, uh, as you think of the other sort of things that we hope become ubiquitous all the way up to that thread, I was reading again, a transcript this morning from the Wells Fargo presentation.

456
00:37:15,480 --> 00:37:23,680
They, it's great to see all these new customers on stage, StubHub and DBS bank and Wells Fargo and Dick's sporting goods and, and others, but the Wells Fargo team was talking about repaving.

457
00:37:24,100 --> 00:37:26,520
And I'd like that that's starting to become more of a thing.

458
00:37:26,520 --> 00:37:31,560
And so they're saying, look, we've got 15, 18,000 VMs in our overall, all our PCF environments.

459
00:37:31,560 --> 00:37:33,900
Our mandate by the end of next year is to repave daily.

460
00:37:33,980 --> 00:37:35,760
We're doing it now every two to three days.

461
00:37:35,960 --> 00:37:42,780
So they're just talking about how do we rebuild our entire environments every day with gold images, always patched, all up to date, no downtime.

462
00:37:43,380 --> 00:37:50,760
And just making that like a thing saying like, Hey, if we want to be secure, that means having a much more aggressive approach to how we build infrastructure and rebuild it.

463
00:37:50,820 --> 00:38:01,640
Like that's just so neat to me that something that we've talked about for a bit, hopefully that keeps moving up the chain so that these maybe executive suite folks go, why are we rebuilding VMs every day?

464
00:38:01,700 --> 00:38:02,920
Like that seems like a lot of work.

465
00:38:03,020 --> 00:38:04,580
Like, no, no, this is what we're getting.

466
00:38:05,020 --> 00:38:06,060
Automation makes it possible.

467
00:38:06,240 --> 00:38:10,000
And this is sort of security profile and results that have come from that.

468
00:38:10,180 --> 00:38:15,300
And like, that's a technology thing that someone even who might be a line of business lead goes, yeah, I get that.

469
00:38:15,360 --> 00:38:16,260
How do I get more of that?

470
00:38:16,760 --> 00:38:22,480
So I like that there's some of those even technical concepts are moving up into leadership teams to other people.

471
00:38:22,560 --> 00:38:24,040
And I think that's pretty inspiring stuff.

472
00:38:24,380 --> 00:38:24,540
Yeah.

473
00:38:24,660 --> 00:38:43,680
I mean, I think security is a good example of what I was grasping at to have the, you know, move beyond more locks knowing about stuff, which is, you know, I think most people in a company, especially the leadership, whether they're technical or not, know that security is important and it's something they need to worry about.

474
00:38:44,240 --> 00:38:53,760
And unfortunately, I think their knowledge is motivated by like negative forces, like, like it's something that we need to survive.

475
00:38:54,100 --> 00:39:00,200
And, you know, maybe it would be great if what we in the software world could offer was a more like positive force.

476
00:39:00,200 --> 00:39:09,460
Like here's, here's something you don't do because you will get fired if you don't, but here's something you can do that's like a positive growth mechanism that you can take advantage of.

477
00:39:09,540 --> 00:39:11,880
So, so we'll see what goes on there.

478
00:39:11,880 --> 00:39:21,920
And then speaking of that was my, my, my keynote thing to pick the, I need to go back and rewatch it, not to look up if there was extended, an extended session.

479
00:39:21,920 --> 00:39:31,960
But I liked the, I don't know, maybe the last, I think second to last penultimate for those who like dictionaries slide that the Dick Sporting Good guy had.

480
00:39:32,080 --> 00:39:40,200
And it had the usual sort of like, and I mean usual in a good way, usual sort of like things we learned from our digital transformation or whatnot.

481
00:39:40,440 --> 00:39:50,320
But there, there were, there were two at the bottom that were, I think they were things that you normally wouldn't see people admit to however many hundred thousand or so people,

482
00:39:50,480 --> 00:39:53,460
hundreds of thousands of people who are in the room and will watch the videos.

483
00:39:53,700 --> 00:40:00,340
And the first one was, uh, you know, the cultural change of, of, of changing the skills and the norms and the structure.

484
00:40:00,540 --> 00:40:01,840
I mean, he was pretty blunt.

485
00:40:01,900 --> 00:40:03,420
He was like, we're going to lose some people.

486
00:40:03,860 --> 00:40:05,700
Like, they're just not going to like it.

487
00:40:05,820 --> 00:40:10,940
And they're either going to like sandbag and like not go along with it or they'll quit.

488
00:40:11,180 --> 00:40:15,400
And, and that was, um, that's usually not something that people like to admit.

489
00:40:15,400 --> 00:40:28,460
But I think, I think it's helpful to say these things because it's, uh, it's sort of confirming and soothing that like, if you're trying to do this and you're having difficulty retaining people, like that's totally normal.

490
00:40:28,700 --> 00:40:31,120
Like that's unfortunately going to happen.

491
00:40:31,120 --> 00:40:34,040
It's not because you're necessarily doing something terribly wrong.

492
00:40:34,120 --> 00:40:35,920
It's just that, that shift is difficult.

493
00:40:36,140 --> 00:40:44,440
And then, and then the second thing he said, which I mean, I, I, this is, this is remarkable to me because I don't know if I've ever seen someone say this is like, oh yeah.

494
00:40:44,440 --> 00:40:56,980
And then we're light on design talent, which, which is another thing that I imagine given, uh, that most people are not product centric around aerosol spray cans, uh, metaphorically speaking.

495
00:40:57,240 --> 00:41:01,400
Yeah, probably designers are something that most organizations don't have.

496
00:41:01,400 --> 00:41:12,160
And so it's a, a, um, uh, a function that you'll need to be on the lookout for, for hiring around, uh, not the aerosol spray can engineers, but the software design people.

497
00:41:12,160 --> 00:41:16,860
But he had a, uh, he had a good and, and again, sort of, uh, Frank talk.

498
00:41:16,860 --> 00:41:19,780
And also he was hiring as I recall.

499
00:41:20,340 --> 00:41:20,960
Of course he was.

500
00:41:21,660 --> 00:41:22,060
Yeah.

501
00:41:22,120 --> 00:41:24,440
Again, I thought Vincent did a great talk, the Robo Bank guy.

502
00:41:24,520 --> 00:41:26,560
I thought that was, that was good stuff.

503
00:41:26,600 --> 00:41:28,540
Were there other main stage talks that jumped out at you?

504
00:41:28,600 --> 00:41:35,520
I know for me, I, uh, my first get was Neha from Confluent back, I think in February I asked her and it was a leap of faith for her.

505
00:41:35,600 --> 00:41:38,960
So I, it really meant a lot to me that she said, yes, probably just unwittingly.

506
00:41:38,960 --> 00:41:49,200
Like this seems interesting, but we weren't even really partners yet with Confluent, the creators of Kafka, but you know, our Neha is one of the co-creators of Kafka, but I thought her talk was just outstanding.

507
00:41:49,200 --> 00:41:58,360
It was a good walkthrough of like why events matter, how to think of events in the data-driven world as you start to almost turn the database inside out with some of these event streaming platforms.

508
00:41:58,700 --> 00:42:00,300
So I saw it was a really great talk.

509
00:42:00,440 --> 00:42:01,980
She just, just nailed it.

510
00:42:02,040 --> 00:42:04,060
And so it was one of my favorite talks of the show.

511
00:42:04,620 --> 00:42:08,820
And my other technical talk I really liked, I mean, all the spring team always does a great job.

512
00:42:08,840 --> 00:42:10,820
You can just tell how much they prepare for this.

513
00:42:10,900 --> 00:42:12,720
And that, again, I respect that a lot.

514
00:42:12,720 --> 00:42:23,000
Michael Manella had the unenviable spot of like closing the show and talking about batch and like, and I'd asked that team, I said, look, give me kind of an oldie, kind of golden oldies talk for the last day.

515
00:42:23,060 --> 00:42:30,820
Like help us remember something that's actually really cool in spring, not just always like latest and greatest, sometimes just like what's good, like what's already mature and awesome.

516
00:42:31,200 --> 00:42:35,020
And so I just thought he really did a wonderful job setting up why batch still matters.

517
00:42:35,560 --> 00:42:38,940
Here's an example of using it with things like data flow, even a newer technology.

518
00:42:38,940 --> 00:42:41,580
But so, I mean, that was one of my favorite technical talks.

519
00:42:41,660 --> 00:42:45,480
I thought Michael really took a tough slot and did something really interesting with it.

520
00:42:46,080 --> 00:42:46,540
Yeah, yeah.

521
00:42:46,660 --> 00:42:52,660
And, and yeah, I mean, I think to, to, to go back to the, the Kafka talk as it were.

522
00:42:53,740 --> 00:43:05,240
Yeah, I thought, I thought she did a, a great job presenting it because it was, it had, it had that always difficult to achieve mix of like, it had some interesting new like ideas about databases.

523
00:43:05,240 --> 00:43:22,080
And I guess Kafka people get upset if I called it a database, but whatever your, your, your data, your place where data is that you based this, your data on, uh, you know, like going over kind of, as you were saying, like how, how things change and why events become important.

524
00:43:22,080 --> 00:43:28,480
And then, and then, and then the other thing, again, that most technical people don't always has is man, she was like super confident.

525
00:43:28,680 --> 00:43:31,960
It almost like was part of the, the, uh, the content on its own.

526
00:43:32,320 --> 00:43:37,240
Uh, and you know, most technical people, including myself are just sort of like, eh, take it or leave it.

527
00:43:37,480 --> 00:43:42,560
But, uh, afterwards, since I got, I was like, man, I got to use this stuff because it's very important and it works.

528
00:43:42,960 --> 00:43:44,860
So that, that, that, that was a good talk.

529
00:43:44,900 --> 00:43:52,260
It was, it was, uh, it was nice to have like some data talk up there from, from someone who was, uh, outside of, of our overall community.

530
00:43:52,960 --> 00:43:57,540
Well, so, uh, you know, we usually put these videos up very rapidly.

531
00:43:57,760 --> 00:44:01,720
When, when do you think, uh, we've got some keynote ones up, uh, that you can go see.

532
00:44:01,720 --> 00:44:09,460
I think, I think the, the Dick's one is up there and probably all of the, all of the keynotes, but when, uh, what's, what's, what's the trickle strategy that we're going to have?

533
00:44:09,860 --> 00:44:13,600
Yeah, we've worked with our, uh, our vendor to actually render these super fast.

534
00:44:13,680 --> 00:44:16,900
So yeah, all the keynotes were online, like by the end of the day of the keynotes.

535
00:44:16,900 --> 00:44:23,080
And then I think all the breakouts should be online this week, this, you know, this last week of our first week of October, I guess we're in.

536
00:44:23,300 --> 00:44:25,100
So people should be able to watch those.

537
00:44:25,460 --> 00:44:31,600
Um, you'll probably see us starting to recap some of these in different blog posts as well, as I don't expect you to watch a couple of hundred sessions.

538
00:44:31,720 --> 00:44:32,820
Unless you have a lot of free time.

539
00:44:33,060 --> 00:44:39,400
So we'll try to do our best to, uh, to summarize some of the greatest hits across some of these different, different talks.

540
00:44:39,400 --> 00:44:44,960
But I know I, when I look at the schedule, I was like, I maybe watch 5% of the show.

541
00:44:44,960 --> 00:44:47,120
Like when I look at all the breakouts, all this stuff.

542
00:44:47,260 --> 00:44:52,240
So I'll be immersing myself in a lot of stuff just to just kind of hear what customers are talking about here.

543
00:44:52,380 --> 00:44:57,920
A lot of the engineering talks and some of the things coming in, you know, this is still not just customers talking.

544
00:44:58,040 --> 00:45:01,800
This is still how engineers explain what we're building and what matters and what's next.

545
00:45:01,940 --> 00:45:04,140
So a really good mix between the two.

546
00:45:04,300 --> 00:45:06,180
So tons of stuff to, to watch.

547
00:45:06,540 --> 00:45:12,780
And then hopefully people attend SpringOne tour for kind of that little version throughout the year until, uh, next year in Austin.

548
00:45:13,120 --> 00:45:13,800
Yeah, yeah.

549
00:45:13,860 --> 00:45:15,620
No, I, I, I, I agree.

550
00:45:15,800 --> 00:45:20,520
There's a lot of them and it's hard to see everything, you know, and, uh, I need to redouble my efforts.

551
00:45:20,520 --> 00:45:26,500
I mean, given, given what my job is and what I do and things I'm interested in, uh, I need to try to actually watch all of them.

552
00:45:26,500 --> 00:45:35,760
Cause I, I pull a tremendous amount of content from things I talk about from these, uh, these SpringOne platform videos and some CF summit videos here and there.

553
00:45:35,760 --> 00:45:48,180
But I mean, as an example of how difficult it is, I was, uh, there were, there were some, there were a couple of people from, uh, Mercedes bins.io sort of like a, uh, consumer facing kind of browsing cars and scheduling things.

554
00:45:48,180 --> 00:45:51,580
You know, part of, part of, as we would say, the funnel of getting a car.

555
00:45:51,840 --> 00:45:59,100
And I think some, I think some post, uh, buying activities as well, but, um, I was, uh, I'm going to have a podcast with them sometime.

556
00:45:59,520 --> 00:46:02,720
I don't know, in the next couple of weeks or time going over that.

557
00:46:03,100 --> 00:46:09,520
And, uh, I went back and watched their 2017 podcast from the presentation from SpringOne platform, which I hadn't seen.

558
00:46:09,560 --> 00:46:10,320
And it was awesome.

559
00:46:11,880 --> 00:46:16,180
And it, you know, it reminded me that like, there's a, there's an endless well of these things.

560
00:46:16,180 --> 00:46:34,060
But I think, I think if you're interested in, uh, whatever digital transformation is and agile and DevOps, it's, it's well worth your time to allocate some time to sort of at least find three or four of those that tell these extended stories and kind of extract out, uh, some, what would you call them?

561
00:46:34,580 --> 00:46:38,140
Anecdotes as helpful tips, uh, that people have gone through.

562
00:46:38,700 --> 00:46:45,220
And then I'll, I'll have to get those transcripts from you and then, uh, I don't, I don't have to make transcripts on my own.

563
00:46:45,380 --> 00:46:47,920
I know I've got a secret drive, which I may share with you.

564
00:46:48,180 --> 00:46:49,100
Secret drive.

565
00:46:49,380 --> 00:46:49,600
Yes.

566
00:46:49,940 --> 00:46:53,060
I'll, I'll have to, I'll look up in my little book, how to ask things nicely.

567
00:46:54,540 --> 00:46:56,240
Then I will also endorse you for that.

568
00:46:56,380 --> 00:46:59,680
Oh, can I get skilled and asking things nicely?

569
00:47:01,360 --> 00:47:11,540
Well, uh, you know, if you've listened to the past few episodes, I had, uh, I had a interview with, uh, with a couple of people with Kyle, uh, who used to be at CSAA.

570
00:47:11,540 --> 00:47:16,200
And now works at Smarsh and then also, uh, Thomas from, uh, West.

571
00:47:16,560 --> 00:47:24,280
And, uh, this idea of product thinking and what culture is came up in both of those conversations, which I'm sure a listener you have listened to in detail.

572
00:47:24,840 --> 00:47:29,900
Uh, but those, those are actually fun episodes to do there, uh, on the, in the lobby of the hotel.

573
00:47:29,900 --> 00:47:33,920
Well, I think there was some Gwen Stefani as the soundtrack when Thomas and I were talking.

574
00:47:34,460 --> 00:47:39,700
Um, and I think there's some follow-up interviews that I was, I will have like with the, uh, Mercedes Benz people.

575
00:47:40,140 --> 00:47:47,440
But, uh, if there, if there's any of the talks that you, the listeners saw, and you think that would be good to have those people on here for extended conversations, you should send them to me.

576
00:47:47,740 --> 00:47:54,100
And then our sister podcast, Pivotal Insights, we'll beat them to talking to customers that, that are interesting.

577
00:47:54,100 --> 00:47:56,320
They're always much better at doing that.

578
00:47:56,560 --> 00:47:58,780
So I'm sure they'll have some people on as well.

579
00:47:59,120 --> 00:48:01,380
And, uh, as always, thanks for listening.

580
00:48:01,500 --> 00:48:02,920
This has been Pivotal Conversations.

581
00:48:03,000 --> 00:48:08,020
If you want to get the most recent episodes and you're thinking, oh, I should go listen to, uh, those old episodes.

582
00:48:08,020 --> 00:48:13,880
Cause, uh, I was a teenager in the nineties and I love Gwen Stefani or, you know, or the early two thousands.

583
00:48:14,280 --> 00:48:19,360
Uh, you can go to soundcloud.com slash Pivotal Conversations, and they're all listed there.

584
00:48:19,520 --> 00:48:25,460
And then we post the show notes about every Thursday on pivotal.io slash, uh, podcasts.

585
00:48:26,000 --> 00:48:30,920
Um, and, uh, I'll put a link to many of the things we mentioned there and maybe things that we didn't.

586
00:48:31,000 --> 00:48:32,800
And with that, we'll see everyone next time.

587
00:48:32,920 --> 00:48:33,540
Bye-bye.