1
00:00:00,000 --> 00:00:05,140
Well, you know, I just recorded another podcast and I asked this question and usually I assume

2
00:00:05,140 --> 00:00:09,960
that everyone who listens to any one of my podcasts listens to all of them.

3
00:00:09,960 --> 00:00:14,760
My son's been doing word problems in math, so I think I just formulated one there for

4
00:00:14,760 --> 00:00:15,180
logic.

5
00:00:15,720 --> 00:00:18,660
But I'm going to go ahead and ask this question again because I'm very curious.

6
00:00:19,380 --> 00:00:23,640
So for each of you, do you use pencils or pens?

7
00:00:24,100 --> 00:00:25,460
And what is your rationale?

8
00:00:26,760 --> 00:00:27,840
Why don't you go first, Richard?

9
00:00:28,840 --> 00:00:34,220
Yeah, I believe I'm a pen person because I'm not seven and I don't have pencils sitting

10
00:00:34,220 --> 00:00:34,660
around.

11
00:00:35,560 --> 00:00:40,920
So I do typically use pens because if I can't get it the first time, that's not worth doing.

12
00:00:41,060 --> 00:00:42,180
No, no erasers for me.

13
00:00:42,620 --> 00:00:45,740
That's perfect every time or I destroy it.

14
00:00:46,580 --> 00:00:47,320
That's right.

15
00:00:48,840 --> 00:00:50,480
How about how about yourself, Jared?

16
00:00:51,400 --> 00:00:56,620
I think in the corporate world, there's actually a lot more martens for error than in the school

17
00:00:56,620 --> 00:00:56,940
world.

18
00:00:57,080 --> 00:00:58,180
So I'm a pen guy.

19
00:00:58,300 --> 00:01:02,000
Also, if you make a mistake, you just cross it out and you kind of move on.

20
00:01:02,000 --> 00:01:06,080
There isn't quite as much focus on penmanship in the corporate world from what I found.

21
00:01:06,480 --> 00:01:06,720
That's true.

22
00:01:06,900 --> 00:01:08,940
I'm drawing a race marker more than any of them now.

23
00:01:09,400 --> 00:01:09,520
Yeah.

24
00:01:09,600 --> 00:01:21,540
I think if I was in a meeting where whiteboarding happened and someone started writing in cursive, I would just scoot back from the desk and be like, all right, we're done here and just leave.

25
00:01:22,580 --> 00:01:23,140
That's it.

26
00:01:24,260 --> 00:01:25,920
That would be such a strange occurrence.

27
00:01:25,980 --> 00:01:29,700
I don't even see cursive in my normal life, let alone in a corporate world.

28
00:01:29,880 --> 00:01:32,540
We spent a lot of time learning that when I was in school.

29
00:01:32,680 --> 00:01:34,880
It's a weird vestigial thing.

30
00:01:35,260 --> 00:01:35,600
It is.

31
00:01:36,180 --> 00:01:38,880
So we've done a little bit of introducing.

32
00:01:38,980 --> 00:01:40,620
Why don't you introduce yourself briefly, guest?

33
00:01:42,260 --> 00:01:43,100
I'm Jerry Ruckel.

34
00:01:43,240 --> 00:01:47,580
I'm on the marketing team here at Pivotal in beautiful Seattle, Washington.

35
00:01:47,900 --> 00:01:52,860
I work on Richard's team helping tell the Pivotal Cloud Foundry story to the world.

36
00:01:53,440 --> 00:02:01,640
So I wanted to have – well, I should say we wanted to have you on because you wrote a post about the most recent release of our Pivotal Cloud Foundry, version 1.8.

37
00:02:02,240 --> 00:02:05,860
And when we get back – when we get to the second half of the show, we'll go over that.

38
00:02:06,020 --> 00:02:07,300
But thanks for being on here.

39
00:02:08,360 --> 00:02:09,040
Yeah, looking forward to it.

40
00:02:09,040 --> 00:02:09,400
My pleasure.

41
00:02:09,620 --> 00:02:11,880
Yeah, I like how you said that it was your idea.

42
00:02:11,980 --> 00:02:17,700
Like, I'm keeping him from – I'm trying to really keep Jared in a headlock and not unleashing him on the wild, but you fought me on that.

43
00:02:17,700 --> 00:02:25,980
Well, as everyone would presume from a company that talks about Agile and DevOps and culture, we try to maximize the output of employees.

44
00:02:26,160 --> 00:02:29,880
So I know I owe you a few favors for using up some of Jared's time here.

45
00:02:30,240 --> 00:02:32,560
I'll have to – I'll ship you a case of pencils.

46
00:02:33,100 --> 00:02:33,480
How about that?

47
00:02:33,960 --> 00:02:34,520
I like that.

48
00:02:34,600 --> 00:02:35,040
Better stay.

49
00:02:36,620 --> 00:02:43,700
Well, you know, I was joking before this that it was something of a slow news week, at least from the infrastructure perspective.

50
00:02:43,980 --> 00:02:49,140
We already talked about how Oracle is going to take out AWS last week.

51
00:02:49,260 --> 00:02:49,880
So we covered that.

52
00:02:49,960 --> 00:02:50,980
There was some more on that.

53
00:02:51,120 --> 00:02:52,880
You know, you can go read up about that.

54
00:02:53,020 --> 00:02:54,560
Very thrilling, exciting stuff.

55
00:02:54,760 --> 00:03:06,100
But there was – I think for me, the two most interesting things broadly – I think that, you know, there was – there's a new version of Windows Server coming out, which is always interesting from an infrastructure thing.

56
00:03:06,320 --> 00:03:09,640
We can – you can – you can school me being up in that neck of the woods about what's in there.

57
00:03:09,640 --> 00:03:17,380
But I think the most interesting practical thing is that apparently 500 million accounts were stolen from Yahoo.

58
00:03:17,480 --> 00:03:19,760
This is like in 2014 or something, right?

59
00:03:20,600 --> 00:03:20,900
Right.

60
00:03:21,560 --> 00:03:22,000
Right.

61
00:03:22,520 --> 00:03:27,180
Yeah, I need to – you know, I don't really use my Yahoo Mail anymore, but I do use Flickr.

62
00:03:27,460 --> 00:03:31,100
So I probably should go update my password and update it.

63
00:03:31,480 --> 00:03:32,620
Yeah, definitely scary stuff.

64
00:03:32,740 --> 00:03:34,680
I mean, obviously, there's plenty of jokes around.

65
00:03:34,760 --> 00:03:39,520
Like, it was great for their ads, you know, because they had a bunch of impressions by everyone logging in to change their password.

66
00:03:39,880 --> 00:03:44,540
And, you know, it's kind of a subtle way of also saying you had 500 million accounts, so well played.

67
00:03:44,680 --> 00:03:47,400
But it's, you know, not good stuff.

68
00:03:47,460 --> 00:03:49,600
Use a password manager if you don't already.

69
00:03:49,920 --> 00:03:50,020
Yeah.

70
00:03:50,040 --> 00:03:54,560
You know, that's definitely probably everyone's biggest takeaway is change passwords often.

71
00:03:55,020 --> 00:03:55,240
Yeah.

72
00:03:55,440 --> 00:03:59,380
Yeah, as we are fond – well, every now and then, you and I quipping on this podcast.

73
00:03:59,380 --> 00:04:01,220
Like, it's always be careful.

74
00:04:01,420 --> 00:04:10,020
You've got to be careful about throwing your rocks and glass houses because you, too, may one day be working at a company in the waning years of its revenue growth.

75
00:04:10,340 --> 00:04:11,660
You don't want to make fun of them too much.

76
00:04:12,300 --> 00:04:16,740
No, and these breaches, sometimes they're internal, sometimes they're whatever.

77
00:04:17,040 --> 00:04:18,420
So, again, it's never fun.

78
00:04:18,560 --> 00:04:20,740
It's something that you may face yourself in most companies.

79
00:04:20,940 --> 00:04:24,580
Now, you two seem like you probably know security much better than I do.

80
00:04:24,580 --> 00:04:29,740
But now, if I turn on the old 2FA stuff, I'm pretty much cool, right?

81
00:04:29,940 --> 00:04:34,940
Like, that's – whenever something gets breached, I'll be safe because they can't do their second factor.

82
00:04:35,100 --> 00:04:36,800
I mean, I should still change my password.

83
00:04:37,640 --> 00:04:41,940
But it's sort of like we'll more or less guarantee my account can't be hacked.

84
00:04:43,080 --> 00:04:44,180
I mean, you're better off.

85
00:04:44,420 --> 00:04:50,500
There's always the social engineering sort of stuff where, hey, call up and say, my God, I just dropped my phone in the toilet.

86
00:04:50,640 --> 00:04:52,340
I can't get the two-factor off.

87
00:04:52,400 --> 00:04:54,100
Can you just let me buy this one time?

88
00:04:54,160 --> 00:04:56,660
And, hey, I know your birthday because I trolled you on Facebook.

89
00:04:56,660 --> 00:05:00,820
So, there's still ways that that's not any sort of foolproof thing.

90
00:05:01,080 --> 00:05:05,740
And if someone does steal your phone, cut off your thumb or something, then they can also get in there.

91
00:05:05,940 --> 00:05:06,760
There's another way.

92
00:05:06,760 --> 00:05:07,920
The old toilet defense.

93
00:05:09,200 --> 00:05:10,120
Always a winner.

94
00:05:10,640 --> 00:05:21,040
There's another thing that I saw what people are also doing is that for the answers to the secret question, what's your mother's maiden name, what's your pet's name, is that you just have 15 strings of random text.

95
00:05:21,160 --> 00:05:26,000
So, it's essentially another protected password instead of what those values would actually be.

96
00:05:26,100 --> 00:05:28,400
So, that's some extra skunk works advice there.

97
00:05:28,720 --> 00:05:28,940
Yeah.

98
00:05:29,080 --> 00:05:34,240
You know, and maybe it does this automatically, but I was hoping – because I noticed that too recently, and that's clever.

99
00:05:34,360 --> 00:05:37,820
I was hoping the old LastPass and 1Password would work with that.

100
00:05:37,820 --> 00:05:42,580
And if they don't, I'll have to submit a feature request because that would be nice.

101
00:05:43,740 --> 00:05:45,180
It's just additional passwords.

102
00:05:45,320 --> 00:05:45,420
Yeah.

103
00:05:45,940 --> 00:05:48,680
I was – it does – well, what?

104
00:05:48,900 --> 00:05:49,220
Anyways.

105
00:05:49,640 --> 00:05:49,820
Yeah.

106
00:05:50,060 --> 00:05:51,100
Breaches are very annoying.

107
00:05:51,280 --> 00:06:04,220
I was talking with my wife about it because she has the thing where she uses her Yahoo account for her junk mail that, you know, I have other – you know, I have my infamous Johnny Legion account that I use for getting free PDFs.

108
00:06:04,720 --> 00:06:08,640
But she uses Yahoo for that, and she actually has changed her password in the last year.

109
00:06:08,800 --> 00:06:12,220
So, she's following the advice of rotating.

110
00:06:12,640 --> 00:06:13,920
So, good for her.

111
00:06:14,940 --> 00:06:15,160
Yeah.

112
00:06:15,460 --> 00:06:16,420
Good old passwords.

113
00:06:16,420 --> 00:06:28,760
I actually, you know, while we're on this topic, I just enabled the unlock your laptop with your Apple Watch thing, which it didn't work for the first three days, and miraculously it started working, which is kind of mysterious.

114
00:06:29,580 --> 00:06:31,760
But, yeah, it's actually kind of nice.

115
00:06:31,900 --> 00:06:39,520
I just – for this podcast, I just sat down now, and my computer was unlocking, and I was freaked out a little bit, and then I remembered it's because I have that turned on.

116
00:06:40,320 --> 00:06:41,820
But that'll be fun.

117
00:06:41,820 --> 00:06:46,200
So, as I mentioned, there's also the general availability of Windows Server 2016.

118
00:06:46,480 --> 00:06:52,200
Now, everyone who listens to this podcast knows that I don't know that much about Microsoft stuff, but you guys do.

119
00:06:52,580 --> 00:06:54,420
What's going on in Windows Server 2016?

120
00:06:55,660 --> 00:06:55,920
Yeah.

121
00:06:56,160 --> 00:06:59,320
I mean, it's the usual – you know, some updates on – it's always easier.

122
00:06:59,440 --> 00:07:02,980
I mean, you never see someone say, this is the second best version of Windows we've ever released.

123
00:07:03,080 --> 00:07:04,960
So, it's always, this is the best version of Windows.

124
00:07:05,360 --> 00:07:06,500
You know, you hope so.

125
00:07:07,000 --> 00:07:09,820
There's some simplicity, things around storage and networking.

126
00:07:10,100 --> 00:07:14,300
There's some support for some of the container things natively within Windows, which can be pretty exciting.

127
00:07:14,500 --> 00:07:16,960
So, there's a – it's the usual upgrade thing.

128
00:07:17,040 --> 00:07:24,100
I believe that Windows continues to bleed market share to Linux, as more people see that as an automation-centric OS to use.

129
00:07:24,220 --> 00:07:26,640
And, you know, people were getting a little excited today.

130
00:07:26,740 --> 00:07:30,960
Docker also announced some general availability for Docker on Windows 2016.

131
00:07:30,960 --> 00:07:33,280
And, again, it's really easy to get excited about that.

132
00:07:33,340 --> 00:07:40,600
So, I did some quick, you know, serious research using the Googles to find out, you know, what is the adoption rate of Windows versions?

133
00:07:40,680 --> 00:07:42,420
Because we can get excited about these new versions.

134
00:07:42,640 --> 00:07:52,140
But, you know, according to numbers from July of this year, Windows Server 2003, which is unsupported, still has an 18% market share.

135
00:07:52,140 --> 00:08:02,580
You have Windows Server 2008 is running 45% of workloads, and Windows Server 2012, you know, a four-year-old OS, is still only 24%.

136
00:08:02,580 --> 00:08:10,120
So, you know, we can be excited, but you're going to be 10 years out before Windows 2016 is seen as a mainstay in your enterprise.

137
00:08:10,280 --> 00:08:15,480
Does that kind of stick into a gloopy sort of bell curve there, if I heard the numbers right?

138
00:08:15,620 --> 00:08:16,360
That's kind of nice.

139
00:08:17,020 --> 00:08:18,080
Almost, yes.

140
00:08:18,120 --> 00:08:24,340
I mean, when you see Windows 2012 is used as much as Windows Server 2003, that makes you think the apocalypse is nigh.

141
00:08:26,120 --> 00:08:32,660
Well, first of all, that's sort of like, that's some activity after my own sort of tech news reading heart.

142
00:08:32,660 --> 00:08:43,400
Like, I don't, maybe I complain about this too much, but I hate those kind of like slapdash kind of tech journalism stories that have no context, right?

143
00:08:43,440 --> 00:08:52,120
So that's like an obvious question to ask is like, what is the, what is the, the, the sort of penetration and adoption patterns for this thing that came out?

144
00:08:52,200 --> 00:08:53,660
So good job.

145
00:08:53,760 --> 00:08:54,920
Gold star on that.

146
00:08:55,360 --> 00:08:57,360
You know, I want to be like you when I grow up.

147
00:08:57,400 --> 00:08:59,200
So I got to go double click in.

148
00:08:59,460 --> 00:09:01,340
Oh, go on, go on.

149
00:09:01,780 --> 00:09:02,140
Indeed.

150
00:09:04,140 --> 00:09:06,180
So, so yeah, that's exciting.

151
00:09:06,480 --> 00:09:16,780
I think, I think, you know, I think when I was a young programmer and I've commented on this several times when we cover Microsoft software news, like I was, I was, you know, like a PHP programmer and a Java programmer.

152
00:09:16,780 --> 00:09:29,400
And it's not until I became sort of like a, a real person in, in, with cognizance in the outside world that you realize like, oh, Microsoft is kind of a big deal in the, in, in the infrastructure software world.

153
00:09:29,400 --> 00:09:30,700
So that's great.

154
00:09:30,900 --> 00:09:31,180
It's good.

155
00:09:31,240 --> 00:09:32,960
They have a, a release out there.

156
00:09:33,500 --> 00:09:34,100
It's good.

157
00:09:34,160 --> 00:09:47,200
I think in, in light of our hot takes last week, which I enjoyed, you know, I would say if my hot take on this is that if you as a company are waiting for innovations at the OS level, then you are thinking at the wrong level.

158
00:09:47,300 --> 00:09:55,640
You need to be thinking at the, I mean, that's where PCF and platforms matter because your deployment of OS level updates is, is depressingly slow.

159
00:09:55,640 --> 00:09:59,600
So if you're looking for lessons to help you innovate, then you're probably not doing it right.

160
00:09:59,980 --> 00:10:05,220
So did you, did you read up on, uh, I just saw this before, but what's, what's the, uh, the Docker partnership thing?

161
00:10:05,640 --> 00:10:13,800
Did you, uh, yeah, I mean, it uses the native windows 2016 containers to let you now build and run Docker containers on windows, which is novel.

162
00:10:13,800 --> 00:10:18,340
Now I get PCF containerized windows for, for years now using other mechanisms.

163
00:10:18,340 --> 00:10:24,240
And really the goal is do I, can I isolate workloads and do some resource management that that's the goal here?

164
00:10:24,520 --> 00:10:26,200
So, you know, we've been doing that for a while.

165
00:10:26,280 --> 00:10:29,000
It's really cool that it runs natively in 2016.

166
00:10:29,000 --> 00:10:33,560
We've actually already tested and will support PCF on windows server 2016.

167
00:10:34,160 --> 00:10:35,600
So you're already set there.

168
00:10:35,660 --> 00:10:37,300
We're not using the native constructs yet.

169
00:10:37,360 --> 00:10:40,180
We're using what we've built around that, but all good stuff.

170
00:10:40,260 --> 00:10:46,020
So as, as that continues to mature as technology, you'll probably see us figure out some ways to support the native bits.

171
00:10:46,360 --> 00:10:46,520
Yeah.

172
00:10:46,660 --> 00:10:46,840
Yeah.

173
00:10:46,880 --> 00:10:54,200
I, you know, I, I, I like this, uh, this new Microsoft that, that very, uh, I wouldn't even call them a fast follower so much anymore.

174
00:10:54,200 --> 00:10:56,440
They're, they're pretty much on schedule for everything.

175
00:10:56,440 --> 00:11:07,060
And then they seem to, uh, they seem to fully to use an older and even an old term again, they seem to fully embrace, not so much extend like, uh, other technologies out there.

176
00:11:07,060 --> 00:11:12,660
And it just works like, I mean, for, for those who don't know, obviously they, they're an investor in pivotal.

177
00:11:12,660 --> 00:11:18,560
So, so they like the, like the way that we do things and they work with us a lot and they, they have their own way of going about things.

178
00:11:18,560 --> 00:11:30,360
I was just at a DevOps days, uh, Dallas or DFW last week and Jeffrey Snover, who I think is like head of engineering for STG or whatever they call it, or some highfalutin thing.

179
00:11:30,360 --> 00:11:36,380
He's one of the only fellows there, but the PowerShell person, like they have PowerShell, like they're, uh, I don't know.

180
00:11:36,380 --> 00:11:46,880
Like I, I think, I think if you were to, uh, as it were, be an alien who came to the planet and observed all of Microsoft's infrastructure stuff, it would seem pretty like, like everything else.

181
00:11:46,880 --> 00:12:01,940
When I mean that as, as, as like a, uh, a good compliment, they've really embraced the heterogeneous data center thing that you didn't really, for example, see people like Sundu way back when, who's kind of, uh, just, uh, didn't acknowledge the existence of that whole world.

182
00:12:01,940 --> 00:12:02,780
Very effectively.

183
00:12:03,600 --> 00:12:05,260
No, they've done a very good job.

184
00:12:05,360 --> 00:12:17,020
Now, of course there can't be any Microsoft news that doesn't get commented on, on Reddit or hacker news with people still referring to, you know, 1993 era Microsoft to putting the dollar sign in the Microsoft name and hating them.

185
00:12:17,220 --> 00:12:24,180
But, you know, as much as a company can transform, it should be, uh, they should be complimented for, for going a place.

186
00:12:24,220 --> 00:12:31,780
They could have gone sideways six years ago and instead they reinvented themselves around open source and agility and other stuff and kudos to them.

187
00:12:31,780 --> 00:12:37,280
So, yeah, hopefully there's some sort of, uh, Cade Metz or Steven Levy type of person writing a book about it.

188
00:12:37,360 --> 00:12:38,340
That, that would be nice.

189
00:12:38,340 --> 00:12:40,160
The, uh, the new era of Microsoft.

190
00:12:40,540 --> 00:12:41,460
I like that.

191
00:12:42,160 --> 00:12:43,720
So, uh, let's see.

192
00:12:43,760 --> 00:12:49,780
Also, it looks like also in Microsoft land that, that Azure has spread out to, uh, to many more regions.

193
00:12:49,780 --> 00:12:51,800
How many regions do you think they have going now?

194
00:12:52,280 --> 00:13:01,940
Yeah, they are up to 34, which, you know, Scott Guthrie, the, the big cheese of Azure is often prone to say that they have more than Amazon and Google combined.

195
00:13:02,160 --> 00:13:04,640
And, you know, the interesting thing, everybody can keep expanding.

196
00:13:04,740 --> 00:13:05,100
That's fine.

197
00:13:05,180 --> 00:13:12,120
What was interesting here is A, it's Germany and Germany is, is well renowned for having some extremely stringent data protection rights.

198
00:13:12,280 --> 00:13:22,080
So this one was interesting because they actually have this, these locations running under a trustee of sorts to make sure that they're, they're following all the right data protection concerns.

199
00:13:22,080 --> 00:13:32,660
So if you're wanting to keep data in Germany, which is often a huge criteria, then, you know, it seems like Microsoft went the extra mile to actually make sure that you have a lot of confidence in that.

200
00:13:33,040 --> 00:13:33,140
Yeah.

201
00:13:33,520 --> 00:13:33,960
Yeah.

202
00:13:34,100 --> 00:13:42,360
I mean, I, I think, I think that's, that's kind of, that's kind of a representative data point of, uh, when we were talking about the, uh, the public IaaS magic quadrant out there.

203
00:13:42,720 --> 00:13:50,000
And, uh, one of the ways of summarizing it is like, uh, well, there's two ways is like, good luck if you're not Amazon or Azure.

204
00:13:50,000 --> 00:13:58,680
Sure. And the, the, and the reason for that is the, the scale and barriers to entry are so massive that it's, it takes a long time and a lot of money to build up to that.

205
00:13:58,700 --> 00:14:11,940
And this is a good example of if you want to, if you want to be the world server, you've got to go out into the world kind of ironically for how you, how, for the way that people consume cloud, where you're not supposed to care about it and all of that stuff.

206
00:14:11,940 --> 00:14:20,780
But all of that gets shifted to the cloud provider and they have to worry about, you know, every single country, every region and, or I should say worrying about them and building it out.

207
00:14:20,900 --> 00:14:23,680
So it's, uh, that scale is, is pretty amazing.

208
00:14:24,380 --> 00:14:32,200
Yeah. And these clouds operate, I mean, I'll, I'll, I'm going to pepper Jared with this question later, but I mean, what's interesting is, you know, German now, Germany now behaves a little differently.

209
00:14:32,500 --> 00:14:36,580
China is usually a different type of cloud environment for vendors, obviously have others.

210
00:14:36,700 --> 00:14:44,340
So sometimes multi-cloud can actually all happen within the same provider because in essence, you're dealing with multiple data sets, sometimes even different policies.

211
00:14:44,560 --> 00:14:47,160
So multi-cloud doesn't have to span providers or even sites.

212
00:14:47,800 --> 00:14:48,980
No, that's, that's, that's a good point.

213
00:14:49,020 --> 00:14:54,320
And it's also to, to use the, uh, funny homogeneous heterogeneous stuff from, from the early days.

214
00:14:54,320 --> 00:14:59,020
It's, it's almost as if the, uh, countries are defining the heterogeneity now.

215
00:14:59,020 --> 00:15:10,600
I mean, not completely, but it's, to your point, it's interesting to think about how part of what as a large organization you have to worry about with incompatibilities and integration is due to, uh, geographic things.

216
00:15:10,780 --> 00:15:18,020
Not necessarily if you're using, uh, you know, Unix versus a mainframe versus windows versus Linux, but I don't know.

217
00:15:18,240 --> 00:15:19,740
That's just a fun thought exercise.

218
00:15:20,260 --> 00:15:25,820
Speaking of fun thought exercises, there were, there were rumors that the last of, uh, uh, at the end of last week.

219
00:15:25,820 --> 00:15:35,720
And I have to say the, uh, especially if it's from Bloomberg, like the, the rumor mill for tech acquisitions has, has been pretty, uh, accurate over the past couple of years.

220
00:15:35,900 --> 00:15:43,640
It's, it's always panned out pretty well, but it looks like maybe everyone's favorite Twitter is, is trying to sell itself and be acquired by someone.

221
00:15:43,640 --> 00:15:48,960
And the, uh, the interesting thought experiment is like, who would he, who, what would that be like?

222
00:15:48,960 --> 00:15:58,800
And it, and it is, I mean, before I get y'all's thoughts on it, it is a little, uh, I wouldn't say unnerving, but, but I, I usually don't care about what happens in the consumer space.

223
00:15:58,800 --> 00:16:07,840
But because Twitter is such like a, I guess, important mission critical part of my career, I actually care a lot more about this than, uh, normal things.

224
00:16:07,840 --> 00:16:11,220
I would like, it's, uh, I, I, I gotta, I gotta know what to go.

225
00:16:11,280 --> 00:16:17,780
I, I, I at least need to know when, and if it hits an iceberg so that I can start establishing myself somewhere else.

226
00:16:17,780 --> 00:16:33,040
Because I do this analysis every now and then, and like, aside from when, uh, our own corporation helps promote my own sort of content on my own, the only place that I'm really successful in driving a lot of traffic is in Twitter and the podcast that I do.

227
00:16:33,200 --> 00:16:39,240
So, you know, I got to keep this stuff up or, or, uh, or I'm going to have to downsize my life or something.

228
00:16:39,480 --> 00:16:41,660
So hopefully someone responsible buys them.

229
00:16:42,340 --> 00:16:42,740
Yeah.

230
00:16:42,800 --> 00:16:45,960
You'd be dusting off your Google plus profile, which we know that drives a lot.

231
00:16:46,320 --> 00:16:46,720
Exactly.

232
00:16:47,140 --> 00:16:50,460
I had to go look this up last week, but I'll, I'll have to go back to friend feed.

233
00:16:50,740 --> 00:16:53,700
Although Facebook, I, Facebook bought them and shut them down.

234
00:16:53,700 --> 00:16:58,680
So I don't know, but I don't know what's, uh, what's y'all's fantasy buyers for something like Twitter?

235
00:16:59,160 --> 00:17:08,020
I mean, you saw the list, I think of who's sniffing around here and everybody can make up the list of whether it's, it's obviously people like Google or Salesforce was in the mix Verizon.

236
00:17:08,340 --> 00:17:15,220
So, I mean, there seems like there's some bad places for them to go that it might be morphed into something that fits that company's worldview.

237
00:17:15,540 --> 00:17:16,020
I don't know.

238
00:17:16,020 --> 00:17:18,080
I feel like I'm kind of rooting for Google on this one.

239
00:17:18,080 --> 00:17:34,460
Because I think that they could do some cool stuff, integrating search into the firehose of Twitter and probably wouldn't muck with the spirit of what that thing is versus, you know, Hey, I love Salesforce, but you could see this becoming a very, something that integrates more into their worldview of customers and relationships.

240
00:17:34,460 --> 00:17:42,480
And like, I want it to just be a platform where people can scream about the weather and yell at each other, not something that business value.

241
00:17:42,640 --> 00:17:49,040
So, you know, I'd probably rather go to a company that just sees this as interesting data versus forcing it into an experience.

242
00:17:50,520 --> 00:17:55,360
You want old man yelling at cloud, not old man providing cloud business.

243
00:17:55,840 --> 00:17:56,720
That would be much better.

244
00:17:56,940 --> 00:17:58,160
Sorry, I interrupted you, Jared.

245
00:17:58,280 --> 00:17:59,180
What were you saying?

246
00:17:59,260 --> 00:18:05,160
Yeah, I think that, yeah, I agree with Richard that I'd probably be rooting for Google here as well because it's such a transformative platform.

247
00:18:05,360 --> 00:18:09,160
And I think that, you know, Coté, you mentioned some of the things of what it's done for you personally.

248
00:18:09,240 --> 00:18:11,860
I think a lot of the hardcore Twitter users feel the same way.

249
00:18:12,320 --> 00:18:24,980
And something like Google would probably make it more likely to be kind of left alone as this, you know, expression platform where it's so transformative and how news is transmitted and how real time it is and the citizen journalist kind of aspect of it.

250
00:18:24,980 --> 00:18:29,940
And it going to a business software firm, you know, seems a little weird.

251
00:18:30,540 --> 00:18:31,200
Yeah, yeah.

252
00:18:31,420 --> 00:18:32,000
Man, who knows?

253
00:18:32,120 --> 00:18:46,440
I mean, I think just to play armchair, like, iBanker or strategy person, like, I think Google is a good, like, second choice because of our assumptions that they would just, like, not have to be profitable, I guess.

254
00:18:47,400 --> 00:18:57,480
Or that they could be, like, you know, barely profitable just because, you know, Google seems to be happy because Google has lots of money and they can run things like that.

255
00:18:57,540 --> 00:19:01,660
On the other hand, they sort of, like, seem to have run Nest into the ground and other things like that.

256
00:19:01,740 --> 00:19:18,360
But it seems like long-term-wise, something like Facebook would be most interesting because I think Facebook has a pretty good history, like, with Instagram, for example, of not only not ruining but probably improving and making better a business of things.

257
00:19:18,520 --> 00:19:21,200
And the synergies there would be amazing, right?

258
00:19:21,260 --> 00:19:25,220
It's just like Facebook already is really good at selling ads and hopefully they would be good at Twitter.

259
00:19:25,220 --> 00:19:36,940
And the only risk is that probably the reason people like us like Twitter is a large part of it is because we don't like Facebook or we don't want to mix those two streams together, right?

260
00:19:37,200 --> 00:19:39,680
And so that would be a danger.

261
00:19:39,800 --> 00:19:41,840
They would have to, like, Instagram it, so to speak.

262
00:19:41,940 --> 00:19:43,060
But I don't know.

263
00:19:43,260 --> 00:19:44,260
We'll see what happens.

264
00:19:45,480 --> 00:19:55,380
Despite me saying that I think, like, Bloomberg and others are good at the rumor stuff, like, this is one of those that, like, it almost seems maybe this is, like, the old guy in me, like, not getting used to the future.

265
00:19:55,380 --> 00:19:57,780
But, like, Twitter being bought by someone?

266
00:19:57,880 --> 00:19:58,320
Come on.

267
00:19:58,380 --> 00:19:59,200
How could that happen?

268
00:19:59,780 --> 00:20:01,200
But we'll see.

269
00:20:01,400 --> 00:20:02,940
It seems like such a standalone brand.

270
00:20:04,040 --> 00:20:04,320
I know.

271
00:20:04,420 --> 00:20:07,300
Social media is just exploding and Twitter continues to grow slowly.

272
00:20:07,460 --> 00:20:17,080
So, I mean, it seems like the drumbeat has been there for a while that they need to figure out either a business model or find out a big parent who can take them under their wing and let them just keep growing organically.

273
00:20:17,360 --> 00:20:17,540
Yeah.

274
00:20:17,700 --> 00:20:18,500
No, that makes sense.

275
00:20:18,680 --> 00:20:19,200
That makes sense.

276
00:20:19,200 --> 00:20:28,620
Well, at the opposite end of success with glowing organically, which is to say, in a good way, we have a new version of Pivotal Cloud Foundry out.

277
00:20:28,860 --> 00:20:30,720
I think it GA'd a couple weeks ago.

278
00:20:30,900 --> 00:20:31,420
Is that right?

279
00:20:33,220 --> 00:20:33,620
Yep.

280
00:20:33,980 --> 00:20:34,220
Yeah.

281
00:20:34,320 --> 00:20:38,720
So, it's formally, I think, titled Pivotal Cloud Foundry 1.8.

282
00:20:39,160 --> 00:20:40,940
I think we're pretty good with our naming.

283
00:20:41,580 --> 00:20:45,560
And so, you know, you wrote a post on it, Jared, a little while ago.

284
00:20:45,580 --> 00:20:47,320
But before we get to that, why don't you introduce yourself?

285
00:20:47,440 --> 00:20:48,560
What's your background?

286
00:20:48,560 --> 00:20:49,860
How long have you been here?

287
00:20:50,420 --> 00:20:52,340
Like, you know, who are you?

288
00:20:53,940 --> 00:20:54,240
Yeah.

289
00:20:54,380 --> 00:21:04,380
I think probably the best place to start, I've been doing, you know, product marketing, product management for many, many years, longer than I think that I ever would have thought that I would have been doing that.

290
00:21:05,200 --> 00:21:08,760
Been at Pivotal for about two months, almost exactly.

291
00:21:09,940 --> 00:21:10,380
Yeah.

292
00:21:10,420 --> 00:21:14,440
Working on Richard's team with product marketing, telling our story out there.

293
00:21:15,300 --> 00:21:20,040
This software remains to still be very hungry and is eating the world five years on.

294
00:21:20,240 --> 00:21:27,000
So, a lot of cool things happening in how we can help our customers get their software to eat some market share, I guess.

295
00:21:27,380 --> 00:21:31,900
So, how would you define what product marketing does?

296
00:21:32,460 --> 00:21:34,120
Not just here, but just in general.

297
00:21:34,360 --> 00:21:41,960
And I ask this very selfishly, because every time I see my dad, who worked at IBM, so I don't know why he asked me these questions.

298
00:21:42,580 --> 00:21:44,880
But I think he's just, like, gaslighting me.

299
00:21:44,980 --> 00:21:48,360
But, like, it's a little weird to describe what product marketing does.

300
00:21:48,640 --> 00:21:50,920
So, I'm trying to get some cliff notes here.

301
00:21:51,060 --> 00:21:52,520
Like, what do you tell people you do?

302
00:21:53,640 --> 00:22:00,160
Yeah, it is a little bit tricky because you're not a developer, you don't code anything, and you're not a salesperson, so you don't sell anything.

303
00:22:00,420 --> 00:22:01,800
So, what is it exactly?

304
00:22:02,140 --> 00:22:03,160
Kickboxing, if I remember.

305
00:22:03,920 --> 00:22:17,760
And so, I go back to the pragmatic marketing school of thought, where product management is defined as voice of the user, and product marketing is voice of the buyer.

306
00:22:17,760 --> 00:22:32,960
And you spend a lot of your time trying to figure out what happens in that buying process, what type of personas are aligned in the sales process, you know, what artifacts resonate with the persona, what problems do they have,

307
00:22:32,980 --> 00:22:34,340
and how they're trying to solve it.

308
00:22:34,780 --> 00:22:44,820
And I think that it's really gotten interesting, that distinction in recent years in this subscription economy that we're in, where you don't, you know, buy a piece of software,

309
00:22:44,820 --> 00:22:48,980
and then, you know, try and get it to work for three years, and then maybe renew something.

310
00:22:49,560 --> 00:23:01,380
That buying and using criteria and behavior have a lot of kind of overlapping ebbs and flows as people are, you know, constantly kind of, you know, re-evaluating, you know, what tools they want to use and how they want to use them.

311
00:23:01,800 --> 00:23:03,120
Yeah, you know, I hadn't thought of that.

312
00:23:03,120 --> 00:23:07,040
I mean, that is, and it sounds cheesy to, like, say it out loud, but whatever.

313
00:23:07,200 --> 00:23:14,640
Like, there is, because of the subscription-based way of doing things, there's much more of a relationship people have with their software.

314
00:23:15,440 --> 00:23:20,860
In the sense of needing to, like, check up on it and think about what they're doing with it.

315
00:23:20,900 --> 00:23:25,640
I mean, it's different than, like, you bought this thing, and it's just sort of dropped off and see you later.

316
00:23:25,680 --> 00:23:28,240
I guess it's a relationship with the vendor.

317
00:23:28,580 --> 00:23:36,900
Like, you potentially have a more in-depth relationship because you're dealing with them more, which certainly is the case with us in a nifty way.

318
00:23:37,220 --> 00:23:44,580
Also, you're like the 50th person to name-check the pragmatic marketer stuff, so I should go look into that one day.

319
00:23:44,860 --> 00:23:46,020
That sounds really useful.

320
00:23:46,960 --> 00:23:52,840
Yeah, it was, where, you know, nobody goes to college for product management or product marketing.

321
00:23:52,840 --> 00:24:00,400
You sort of come up through the developer ranks or sales engineer ranks or, you know, through the marketing ranks with some type of, you know, technical savvy.

322
00:24:00,620 --> 00:24:08,740
So a lot of times you really need a playbook for how to make these things happen, and they've got all kinds of great, you know, slogans for how to deal with these things.

323
00:24:08,740 --> 00:24:25,320
You know, product managers have all the responsibility but none of the authority, and just all these kind of great, you know, bumper stickers that really reflect what life in tech is like where you don't have, you know, infinite time or infinite resources, and that's why I think the adjective pragmatic is such an apt one.

324
00:24:25,660 --> 00:24:25,780
Yeah.

325
00:24:26,020 --> 00:24:29,620
Well, let's see an example of product marketing in action.

326
00:24:30,040 --> 00:24:32,680
So what's up with 1.8?

327
00:24:32,840 --> 00:24:35,840
How would you sort of, like, summarize what's going on in this release?

328
00:24:37,120 --> 00:24:39,520
Yeah, it's interesting.

329
00:24:39,760 --> 00:24:47,840
I think for me, coming from more of the infrastructure-as-a-service or software-as-a-service world, this whole version number thing is quite the throwback.

330
00:24:48,880 --> 00:24:55,060
It's been an issue to kind of get your sea legs around the 1.8 and then all the other variations of version numbers.

331
00:24:55,360 --> 00:25:05,000
But once you get past that, one of the themes that kind of stood out to me when I was writing the post, you know, came from SpringOne platform that we had in July in Las Vegas.

332
00:25:05,880 --> 00:25:19,320
And one of the keynotes really focused on, you know, time to value, really this notion of being able to reduce the delta in time from when a new feature is ready and when that feature can actually be shipped into production.

333
00:25:19,680 --> 00:25:31,240
And so in trying to look at the story and look at those themes and where our buyers may be and, in fact, where a lot of our users may be, it's really this idea of how can we get time to value for more of our applications.

334
00:25:31,640 --> 00:25:43,460
Because a lot of the platform scale that we, you know, expound, a lot of customers can realize you really get a lot of those efficiencies when you can run more types of applications on a platform like Pivotal Cloud Foundry.

335
00:25:43,460 --> 00:26:02,460
So I think that some of the features that we talked about in this release really supports that idea of having, you know, more and more types of workloads on the platform with some more advanced networking features with TCP routing that allows you to have some legacy workloads or maybe some bring your own container type of opportunities

336
00:26:02,460 --> 00:26:10,300
or even some Internet of things type scenarios coming onto the platform that use this, you know, different type of, you know, routing protocol versus HTTP.

337
00:26:10,980 --> 00:26:11,140
Right.

338
00:26:11,360 --> 00:26:16,160
In that same type of vein, there's also PCI.

339
00:26:16,400 --> 00:26:19,560
You know, we were just talking about, you know, Germany and data sovereignty and data compliance.

340
00:26:19,560 --> 00:26:29,720
When you're talking about really big companies, you know, coming to cloud computing, they have to contend with these regulations, you know, HIPAA and PCI, you know, a lot of things in the financial services sector.

341
00:26:30,000 --> 00:26:38,080
And I know we at Pivotal invest a lot in trying to help customers, you know, comply with those without compromising the pace of their software development.

342
00:26:38,080 --> 00:26:48,660
And so having things like security as just part of the platform that maybe works in the guts that you aren't really exposed to as a developer operator is a good thing.

343
00:26:48,840 --> 00:26:57,440
And some things we've done with with the IPsec add on this release really, I think, supports that notion of making security just part of a platform.

344
00:26:57,440 --> 00:27:04,620
So you can go secure and go fast where those aren't necessarily, you know, diametrically opposed kind of kind of ideas.

345
00:27:04,900 --> 00:27:05,860
Right. Yeah.

346
00:27:05,940 --> 00:27:12,840
I mean, it seems like our our constant sort of theme, if you will, is whether you want to call it time to value or speed to market.

347
00:27:12,840 --> 00:27:25,480
But it's just it's just the good old fashioned IT thing of faster and and more specifically, like speeding up your release cycle and the way that you software and deploy it and everything.

348
00:27:25,480 --> 00:27:36,980
And and then, you know, a lot of what you went over is the the the other side of what we do is like, I mean, we have kind of a we don't always put it this way, but we have an audacious goal of.

349
00:27:37,680 --> 00:27:42,340
So here's the new platform for how you do all your software, right?

350
00:27:42,480 --> 00:27:48,360
Like basically a general purpose software runtime for all the software that you have.

351
00:27:48,520 --> 00:27:58,740
And as a consequence of that, right, like on the one hand, we want to have and we do have like all the if you want to do stuff like all the bleeding edge, like cloud native way, like there's definitely that in there.

352
00:27:58,740 --> 00:28:15,560
But as as we go more and more into our releases and have more and more customers, we just have to like add in and I don't mean this in a judgmental way by saying have to or whatever, but we have to add in a lot of standard things and just all all all of the things that that you need for a general purpose platform.

353
00:28:15,560 --> 00:28:19,920
And it's it's always interesting to see how we balance those two things on on each release.

354
00:28:19,920 --> 00:28:33,320
Yeah. And I think that the other the other big thing, too, just getting back to the features, is this log integration that we have with our PCF metrics module where, you know, it's great to go fast and release new software all the time.

355
00:28:33,720 --> 00:28:40,160
But there's always that day to consideration, you know, thinking about what it's like to actually run this stuff in production.

356
00:28:40,160 --> 00:28:46,880
And how can you you get that developer operator workflow to be as as tight and crisp as as possible?

357
00:28:47,080 --> 00:28:54,920
And with with metrics, giving you some information about how the application is behaving, you know, monitoring metrics information in this new release.

358
00:28:54,920 --> 00:28:58,560
Now you've got actual logs from the application mashed up in there.

359
00:28:58,560 --> 00:29:10,440
So as you're looking at these graphs that are essentially the health of the application, you can drill down into these very slick looking charts and see what was happening in the logs during that actual period of time.

360
00:29:10,440 --> 00:29:20,080
So this is, I think, really a key thing for a lot of our customers, because developers and operators have the same set of facts as the product management team, you know, puts it for that offering.

361
00:29:20,280 --> 00:29:26,280
When something goes up in the night or there is an issue, a lot of times those teams are bringing two sets of facts to the table.

362
00:29:26,480 --> 00:29:32,900
And now with it being integrated into, you know, a module that's connected up to the platform, you've got everything right there.

363
00:29:32,960 --> 00:29:34,800
So people have the same set of facts.

364
00:29:34,960 --> 00:29:39,260
And when it comes time to troubleshooting an issue, they can just review the facts and get on with it.

365
00:29:39,320 --> 00:29:43,640
They don't need to debate who has the best data because it's the unified thing that they have.

366
00:29:44,040 --> 00:29:44,180
Right.

367
00:29:45,380 --> 00:29:48,920
Yeah, I mean, you talked, you touched on TCP routing a little bit.

368
00:29:49,000 --> 00:29:49,960
I mean, that's pretty new for us.

369
00:29:50,020 --> 00:29:55,500
I mean, PCF has typically been about web traffic, you know, HTTP traffic into an application.

370
00:29:55,820 --> 00:30:02,100
So with TCP routing, the whole idea is you can just do TCP directives through our cloud load balancer, things like that.

371
00:30:02,180 --> 00:30:03,680
What else jumped out with you on that?

372
00:30:03,720 --> 00:30:09,200
You wrote up some examples of that, but as a customer, a developer, whatever, why do they care about that?

373
00:30:09,480 --> 00:30:15,060
Yeah, I think that it's really just kind of what we talked about with being able to support more different types of workloads.

374
00:30:15,060 --> 00:30:20,500
I think there's a specific type of IoT protocol that works with TCP routing.

375
00:30:21,200 --> 00:30:38,640
And then this idea of legacy, where you look at what workloads enterprises have in their data centers today, the stuff that actually makes all the money, being able to think about how those systems, which were sometimes, you know, built, you know, 15 years ago, you know, a lot of those were using some different type of networking protocols.

376
00:30:38,640 --> 00:30:56,620
So being able to carve off some of those, you know, monolithic services using TCP routing, bringing those into the platform can help you start to get, you know, more of this microservices, you know, goodness versus the legacy construct of having to go months in between releases a lot of the time.

377
00:30:56,620 --> 00:31:09,380
You know, you also touched on, you know, going back to the world of point releases, you know, when Jared and I worked together for a cloud provider, and we'd ship every couple of weeks, there was no concept of a version of the cloud.

378
00:31:09,500 --> 00:31:10,860
I mean, it was just whatever was out there.

379
00:31:10,940 --> 00:31:24,200
But we purposely at Pivotal don't make a big deal about releases, we do a blog post, we educate our field and our customers, but we don't do big PR stuff, we don't go brief every analyst, because I think we see it as there's just a drumbeat, we're still shipping pretty regularly.

380
00:31:24,780 --> 00:31:32,440
What even between the quote unquote point releases, you have new tiles coming out from partners, you have new plugins, you have new extensibilities in the open source.

381
00:31:32,660 --> 00:31:41,860
So, I mean, how is this different from you from maybe, you know, classic point release stuff to always shipping as a cloud provider to what this kind of hybrid thing is?

382
00:31:41,900 --> 00:31:43,080
Is that weird for you?

383
00:31:43,160 --> 00:31:45,040
Is that if you think that's just a good new reality?

384
00:31:45,360 --> 00:31:48,920
Yeah, I think it's a good new reality, because it's, it's great for the customer.

385
00:31:48,920 --> 00:32:02,440
It's great for the customer to have, you know, new, new chunks of features coming out constantly and sort of, you know, smaller bite size bits that, you know, reduce the risk of, you know, migration or reduce the risk of things that you're operating.

386
00:32:02,860 --> 00:32:09,220
I think there's been a lot that has been, you know, talked about, about, you know, what this new Agile thing means for developers and operators.

387
00:32:09,680 --> 00:32:28,960
But it's also a different, you know, world for a lot of other parts of the organization, you know, marketing teams, you know, sales teams, customer care teams to kind of adjust to this sort of, you know, agile new reality where you've got, you know, probably a lot of big companies with big releases where they'd have, you know, a few big bangs every, every, every times a year.

388
00:32:29,220 --> 00:32:36,960
There's a lot of pomp and circumstance around those releases with, you know, trade shows, you know, confetti parades, all kinds of, all kinds of things.

389
00:32:37,580 --> 00:32:46,000
But then, like we just talked about on the Windows Server 2016 thing, that's kind of a big bang release that in reality won't have its impact felt for a few years down the line.

390
00:32:46,500 --> 00:32:56,380
With platforms, all this cloud, cloud native stuff, we want to get the stuff in the hands of customers, you know, much faster so they can realize the value and frankly, so they can give us feedback on, on where to go.

391
00:32:56,380 --> 00:33:03,720
So it, it is kind of a brave new world, but is only, you know, going to get, you know, more like that versus less like that.

392
00:33:03,880 --> 00:33:07,020
Yeah, I mean, we have a pretty good collaboration between product and marketing.

393
00:33:07,220 --> 00:33:17,240
And so you were a lot of at least observing the sausage making of building PCF and getting it ready and kind of going through staging environments, running in PWS first so we could get some feedback.

394
00:33:17,520 --> 00:33:20,160
Again, I mean, building distributed systems is hard.

395
00:33:20,160 --> 00:33:24,820
You also think there's a parallel our customers are interested in because they're also trying to build complex software.

396
00:33:25,240 --> 00:33:34,680
And maybe we can even do more about explaining how we build it because what we're doing to build PCF may mirror some aspects of what they need to do to ship their own software.

397
00:33:35,340 --> 00:33:56,800
Yeah, there's definitely a lot of that where a lot of companies like Pivotal and I think a lot of others, you know, will do a lot of these executive briefings, EBCs, and essentially, you know, lift up the, lift up the kimono about how, how we work, how we build software, how we're able to, to go fast, what the culture is like, what the tooling is like, what the processes are like.

398
00:33:57,340 --> 00:34:12,400
And we even with Pivotal, I think we take that a step further with, you know, Pivotal Labs where we'll actually do, you know, long-term engagements with customers that teach them, you know, about how to kind of do this, you know, on their own and then, you know, go forth and prosper with this, you know, new methodology down the line.

399
00:34:12,600 --> 00:34:24,080
But I think that's a big part of the pitch and it's interesting that sort of the more automated the world becomes, the more important this human-to-human interaction is about, you know, doing things.

400
00:34:24,120 --> 00:34:30,060
And I guess that kind of gets back to the empathy idea that you hear a lot about at conferences and trade shows and stuff as well.

401
00:34:30,820 --> 00:34:40,620
So, so I, I, I, I had to, uh, uh, despite the fact that we're now raising up to the culture, empathy, uh, person level to go back down into the technical details.

402
00:34:40,880 --> 00:34:48,700
Now, now you've covered a little bit, but I have to admit, I have no idea what IPsec is because, uh, I, I don't like security.

403
00:34:48,700 --> 00:34:49,440
It's annoying.

404
00:34:49,640 --> 00:34:52,600
I mean, I like the effects of it, but I don't like knowing about it.

405
00:34:52,600 --> 00:34:56,380
So, uh, so that's good for my future employment opportunities.

406
00:34:56,680 --> 00:35:02,080
Uh, no security companies apparently, uh, but like, uh, like what is IPsec?

407
00:35:02,380 --> 00:35:04,420
What, what, can you tell me what that is?

408
00:35:05,100 --> 00:35:11,420
Yeah, I think that, uh, maybe the, uh, security for, for Coté, uh, book would have a couple of different chapters.

409
00:35:12,140 --> 00:35:17,020
Um, there, there's kind of this, you know, one way of thinking about, uh, encryption at rest.

410
00:35:17,300 --> 00:35:22,220
So when you've got your data in storage, what kind of protections do you have around that?

411
00:35:22,460 --> 00:35:29,500
And then once your data starts, uh, you know, was it wasn't around what's the encryption in transit, you know, type of story.

412
00:35:29,500 --> 00:35:44,540
So the IPsec add-on is essentially a module that you install, uh, deep in the, in the core of pivotal cloud foundry that will encrypt the traffic of, of the data that's going as it, as it whizzes around of cloud foundry.

413
00:35:44,740 --> 00:35:48,720
So I think it's release number 1.5.37.

414
00:35:49,240 --> 00:35:57,500
And I mentioned that only because, uh, the minutia of that version number, you know, 3.7 versus 3.5 or some other variation.

415
00:35:57,840 --> 00:36:05,320
Each one of those releases will have really key features that will help you in the PCI, uh, auditing type of vein.

416
00:36:05,820 --> 00:36:07,180
Every customer, you know, is different.

417
00:36:07,260 --> 00:36:08,380
Their applications are different.

418
00:36:08,520 --> 00:36:18,280
You know, every PCI auditor is different, but now having a, having a story and an easy mechanism that can help with, uh, encryption in transit for your data inside of cloud foundry.

419
00:36:18,400 --> 00:36:25,740
It's something that makes that PCI story, um, a lot easier for our customers that are dealing with the storage of, of credit card data and so on.

420
00:36:26,080 --> 00:36:34,180
And I, and I guess that's an important nuance is this not only stuff outside of, uh, pivotal cloud foundry, but also when it talks to itself, so to speak, it's encrypted.

421
00:36:34,180 --> 00:36:43,880
So that means that you're, you're, uh, as we were joking about earlier, like you're more protected than, than, than if you weren't doing that, essentially, there's not a, uh, an internal weakness.

422
00:36:44,880 --> 00:36:45,320
Right.

423
00:36:45,500 --> 00:36:46,100
That's right.

424
00:36:46,100 --> 00:36:56,440
And, and again, there's really no kind of, you know, uh, drawback to the developer operator productivity, which I think is a really key, key part of the security investments that pivotal continues to make.

425
00:36:56,440 --> 00:36:59,380
You mentioned the, the, the rotate credentials idea.

426
00:36:59,380 --> 00:37:15,600
That's, you know, one of the, the big pillars of the pivotal security story, um, you know, repair and repay being other kinds of elements that those are all things that you need to almost think about security differently with your, you know, cloud native applications where you, you can't really have it as trying to keep things out.

427
00:37:15,700 --> 00:37:19,560
But just remaster the entire security experience for your platform altogether.

428
00:37:19,860 --> 00:37:31,440
And you really diagnose what causes these, you know, bad actors to get into your system and, um, you know, really think, uh, you're quite, quite, quite differently about how the system can protect itself from those threats.

429
00:37:31,540 --> 00:37:31,940
Yeah.

430
00:37:32,460 --> 00:37:32,820
Yeah.

431
00:37:33,520 --> 00:37:33,940
All right.

432
00:37:34,220 --> 00:37:34,900
Well, that makes sense.

433
00:37:34,980 --> 00:37:44,000
And then the other area, you know, I just, uh, before this recording, I just saw that, uh, over at red monk, what, one of my old bosses, as it were, Steven O'Grady has this post.

434
00:37:44,080 --> 00:37:50,280
I haven't read yet about, uh, where's the databases and DevOps, but, uh, you know, we, we don't, we don't talk about it a lot.

435
00:37:50,340 --> 00:37:56,480
Maybe we need to update our diagram, but there's, there's, uh, there's some database improvements for like preexisting data sources.

436
00:37:56,480 --> 00:37:57,720
We have in this release, right?

437
00:37:59,080 --> 00:38:12,540
Yeah, this, uh, all goes to the version number kind of fun as well, where, um, uh, at, at PCF, we have our own, uh, you know, flavors of open source services, things like, you know, MySQL, things like RabbitMQ and, and Redis.

438
00:38:12,720 --> 00:38:22,240
And there's some interesting, you know, point releases that we have for the pivotal flavors of those that include the latest point releases of the open source versions of those particular products.

439
00:38:22,240 --> 00:38:30,640
So there's a lot of nice, you know, enhancements, um, latest features from the open source version that we'll package up into, into those different tiles that our customers can take advantage of.

440
00:38:30,780 --> 00:38:35,640
And I think this is another great example of, you know, how open source can really work well for, for big companies.

441
00:38:35,800 --> 00:38:44,180
You mentioned Coté earlier about, you know, maybe some objections that sometimes people will have about open source, um, by having a vendor that's committed to open source, like Pivotal is,

442
00:38:44,240 --> 00:38:53,960
but then helping take some of the rough edges off and upgrade in a regular cadence in a way that's contextual for the enterprise, um, can really, you know, make some of those barriers, you know, melt away.

443
00:38:54,140 --> 00:39:10,040
Yeah, I, I think, I think ongoing over the next few years, the way, uh, the way we handle things like whether it's MySQL or Redis or things like that and roll up those upgrades and make it as frictionless as possible for, for our customers like that.

444
00:39:10,520 --> 00:39:22,980
Uh, well, hopefully we'll be successful at it, but our, our success of that will help prove out the, uh, the kind of cloud platform model, namely being like, um, you shouldn't have to worry about that stuff, right?

445
00:39:22,980 --> 00:39:29,420
Like the only worrying you should have to do about your database usage more or less, and by you, I guess, I mean the product teams, right?

446
00:39:29,460 --> 00:39:38,840
Of course there should be someone worrying about the, uh, the finite attitudes, if that's a word of it here and there, but there shouldn't be as much needing to worry about upgrading it and doing all of this stuff.

447
00:39:38,840 --> 00:39:46,840
And so it'll be fun to see how, how collectively the sort of cloud native world wangles out updating, uh, those various middleware services.

448
00:39:46,840 --> 00:40:04,840
So it's, uh, I don't know, it's encouraging to see that that's, we're not, we're not just sort of running away from state, which, which is like the hardest part of, of, of a lot of, uh, programming that you do, or, or I should say it's becoming one of the hardest parts because, uh, we've solved so many other parts of application development and delivery.

449
00:40:05,320 --> 00:40:16,440
Well, I think that, that's a huge point is, is that's where data microservices keep picking up so much mindshare as people are now thinking about, gosh, it's great that I can ship my, my core web app all the time.

450
00:40:16,440 --> 00:40:26,040
But what happens when I have a schema change in my database, what happens when I'm, you know, adding things, data microservices and DevOps with database, how do I do that without breaking everything?

451
00:40:26,260 --> 00:40:30,120
How do I kind of protect people from downtime or completely hose you?

452
00:40:30,260 --> 00:40:40,480
So I'm glad that Pivotal with some of the Spring Cloud Dataflow stuff and trying to do some new patterns around data there and different thoughts of data microservices that we all have to get better at that.

453
00:40:40,540 --> 00:40:46,420
Because if the database slows you down, it really doesn't matter if the rest of it's fast to some extent, because you're still stuck on that.

454
00:40:46,420 --> 00:40:58,960
Yeah, it's, it's, uh, at least for me, it's sort of an interesting, uh, idle thought experiment to think that the, uh, that the, uh, the idea of no SQL came about like what, like five years ago.

455
00:40:59,320 --> 00:41:06,580
And, and I think, I think maybe it's just now that there's sort of, uh, extremely wide mainstream worrying and thinking about it.

456
00:41:06,580 --> 00:41:19,320
And to some extent, and I, and I, and what you're saying made me think of this is, is, uh, without changing your application model, it's really hard to just slot a no SQL type of thing in.

457
00:41:19,400 --> 00:41:27,380
I don't think anyone says no SQL anymore, but it's hard to think of using a non-relational database unless you also change over how you think about your application layer.

458
00:41:27,380 --> 00:41:31,720
And so I think the, uh, the application stuff has caught up to that.

459
00:41:31,720 --> 00:41:33,680
And so now there's a lot more interest in all of that.

460
00:41:33,680 --> 00:41:40,880
Like I was, I was looking at some chart, I should go find this, some chart of like all the non-relational database usage out there.

461
00:41:40,880 --> 00:41:45,820
And many of them have been over the last few years, years rising in popularity quite a bit.

462
00:41:46,480 --> 00:41:46,920
Yep.

463
00:41:47,300 --> 00:41:48,620
Yeah, no, no, no doubt.

464
00:41:48,820 --> 00:41:50,740
But we should cover that in some other episode.

465
00:41:50,920 --> 00:41:52,580
We'll get some, uh, some data person.

466
00:41:52,680 --> 00:41:57,360
I think the only coverage I've ever had in pivotal conversation podcasts about data is it's really

467
00:41:57,380 --> 00:41:57,780
hard.

468
00:41:58,160 --> 00:41:59,980
So, uh, we could delve into that.

469
00:42:00,680 --> 00:42:02,180
Yeah, that's probably, it's probably all we need.

470
00:42:02,260 --> 00:42:03,420
It's peak data right there.

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

472
00:42:04,540 --> 00:42:08,620
I wanted to ask one more question about this release, but we go into one other topic, but,

473
00:42:08,620 --> 00:42:11,000
um, on-demand service brokers.

474
00:42:11,000 --> 00:42:15,420
So we built some capability that is, is new for, for cloud foundry.

475
00:42:15,540 --> 00:42:19,320
Could you talk a little bit about what an on-demand service broker is or what, what was the status

476
00:42:19,320 --> 00:42:20,760
quo that this changes?

477
00:42:21,280 --> 00:42:26,920
Yeah, we've, uh, talked a lot about how, uh, pivotal cloud foundry is, uh, an opinionated,

478
00:42:26,920 --> 00:42:27,840
you know, platform.

479
00:42:27,840 --> 00:42:33,040
And I think one of the really, you know, uh, linchpin, uh, opinions that we have is about,

480
00:42:33,040 --> 00:42:37,980
you know, service brokers and, and how those are, uh, how those enable, you know, the wide

481
00:42:37,980 --> 00:42:42,600
range of applications on the platform to, to talk to third party services, doing it in

482
00:42:42,600 --> 00:42:45,380
a very, uh, flexible, uh, extensible way.

483
00:42:45,580 --> 00:42:50,280
Um, and, and previously what we had was, you know, multi-tenant, you know, service brokers,

484
00:42:50,280 --> 00:42:52,100
which were okay for some scenarios.

485
00:42:52,640 --> 00:42:56,260
Um, but it was, uh, there'd be some, you know, noisy neighbor things that would come up every

486
00:42:56,260 --> 00:43:00,820
once in a while, a few other drawbacks in terms of the operator developer workflow would

487
00:43:00,820 --> 00:43:02,900
need to be pre-provisioned and so on.

488
00:43:03,040 --> 00:43:08,440
And so thinking about, you know, on-demand service brokers as, as a way to, um, alleviate

489
00:43:08,440 --> 00:43:12,900
some of those, uh, behaviors that we had seen in the past and have a much more flexible

490
00:43:12,900 --> 00:43:18,460
model where services could just be, um, created on the fly, instances of those services could

491
00:43:18,460 --> 00:43:23,280
be created on the fly and bound to an application, um, when they were, you know, really required

492
00:43:23,280 --> 00:43:25,740
at the, at the, at the time that it was really needed.

493
00:43:25,980 --> 00:43:28,640
So there's a couple of things there that offer a little bit more of, you know, flexibility

494
00:43:28,640 --> 00:43:29,740
for, for customers.

495
00:43:30,080 --> 00:43:34,460
Um, I think the other exciting thing is that this is something that will, uh, dramatically,

496
00:43:34,460 --> 00:43:38,560
uh, lower the bar for getting new tiles into Pivotal Cloud Foundry.

497
00:43:38,640 --> 00:43:42,620
This is something that we had heard a lot from our partners, people wanting to add their

498
00:43:42,620 --> 00:43:47,460
own third-party tech on top of Pivotal Cloud Foundry and this on-demand approach, um, will

499
00:43:47,460 --> 00:43:51,960
really open up the, the floodgates, I think, for a lot of additional, um, tiles to come

500
00:43:51,960 --> 00:43:55,300
onto the platform, which is, uh, a nice win for the, for the ecosystem.

501
00:43:55,820 --> 00:43:56,540
Yeah, that's great.

502
00:43:56,680 --> 00:43:59,240
The single instance stuff, the current model's fine.

503
00:43:59,340 --> 00:44:02,160
Again, as you mentioned, a lot of cases, they're multi-tenant, but single instance.

504
00:44:02,160 --> 00:44:06,080
So if somebody wants to beat up the RabbitMQ environment, it would be nice to be able to

505
00:44:06,080 --> 00:44:08,240
just on-demand spin up my own environment.

506
00:44:08,340 --> 00:44:09,300
So that, that's huge stuff.

507
00:44:09,360 --> 00:44:13,060
So we have the framework there now, and then we're going to see more and more services adopt

508
00:44:13,060 --> 00:44:13,460
that, right?

509
00:44:13,900 --> 00:44:14,540
Yeah, that's right.

510
00:44:14,580 --> 00:44:18,280
And there'll be a lot of, I think, exciting things to come as we start to get, um, additional

511
00:44:18,280 --> 00:44:22,080
tooling around how this, uh, how this simplify, how this process will be simplified.

512
00:44:22,280 --> 00:44:25,400
And we start to see some additional third parties come on, come online.

513
00:44:25,520 --> 00:44:26,760
So, so watch this space.

514
00:44:27,320 --> 00:44:27,480
Yeah.

515
00:44:27,620 --> 00:44:33,600
So last week you, uh, published a provocative blog post about opinions and everyone has

516
00:44:33,600 --> 00:44:33,820
them.

517
00:44:33,880 --> 00:44:37,720
And specifically it kind of came out from, well, I guess tell us where this came from and

518
00:44:37,720 --> 00:44:39,600
what the spirit of the post was about.

519
00:44:40,080 --> 00:44:40,200
Yeah.

520
00:44:40,220 --> 00:44:43,380
You can't really have a bland, uh, blog topic about opinions.

521
00:44:43,500 --> 00:44:45,280
It would be a little, a little weird to have that.

522
00:44:45,280 --> 00:44:49,420
Um, but I think that, yeah, back to this opinions idea, I think that we have these opinions about,

523
00:44:49,420 --> 00:44:54,140
um, you know, Pivotal Cloud Foundry and that, um, you know, strong opinions help you go, go

524
00:44:54,140 --> 00:44:54,640
faster.

525
00:44:55,000 --> 00:44:59,860
And a little bit of the, of the origin from it was, um, that we've, we've seen a lot of

526
00:44:59,860 --> 00:45:04,640
people with the, the do it yourself route, um, not really go with an unopinionated type

527
00:45:04,640 --> 00:45:05,320
of platform.

528
00:45:05,520 --> 00:45:09,220
Um, and then they kind of, you know, have the, the, the slog, uh, there, which I know,

529
00:45:09,220 --> 00:45:13,940
uh, Coté and Richard, you talked with, uh, uh, uh, Walburn about, uh, the other day.

530
00:45:14,400 --> 00:45:19,540
Um, but there's also starting to see this notion of the opinions being adopted by some other

531
00:45:19,540 --> 00:45:23,300
open source communities, which is always great to see when there are others that are kind

532
00:45:23,300 --> 00:45:26,240
of, you know, thinking about the patterns that we've built in the Cloud Foundry and kind

533
00:45:26,240 --> 00:45:28,160
of, you know, taking that, taking that on.

534
00:45:28,240 --> 00:45:30,400
I think there's, um, some news that's been out there.

535
00:45:30,460 --> 00:45:33,980
There's a nice piece in the, in the new stack about, uh, the service broker work that

536
00:45:33,980 --> 00:45:38,040
the Cloud Foundry Foundation has been doing with some other open source products with,

537
00:45:38,060 --> 00:45:42,160
you know, Kubernetes and thinking about how we can extend the service broker API models,

538
00:45:42,260 --> 00:45:43,960
some of these other type of type of projects.

539
00:45:43,960 --> 00:45:49,660
And, uh, also very recently we've seen how, um, other projects are wanting to, to do containers

540
00:45:49,660 --> 00:45:54,540
and get some of those benefits, um, but not necessarily tied to a specific, you know, proprietary

541
00:45:54,540 --> 00:45:55,400
container format.

542
00:45:55,640 --> 00:46:00,520
So thinking about what, you know, Cloud Foundry has done with, you know, garden and run C and

543
00:46:00,520 --> 00:46:05,020
thinking about that container tooling versus specific vendor distribution, people are starting

544
00:46:05,020 --> 00:46:08,860
to kind of, you know, come, come online with, uh, opinions that we've had for quite a while.

545
00:46:08,940 --> 00:46:12,380
And I think that's just kind of your goodness for, for the industry when people start to think

546
00:46:12,380 --> 00:46:15,960
in, in similar ways that have been validated, you know, technically to be really successful.

547
00:46:16,140 --> 00:46:21,020
And it also helps, um, our customers as well, see the opinions that Cloud Foundry has, how

548
00:46:21,020 --> 00:46:25,020
it's gaining momentum from other places and how they can in turn, you know, use that to help

549
00:46:25,020 --> 00:46:26,220
with our digital transformation.

550
00:46:26,720 --> 00:46:32,300
So, so on, on, on this topic, what do you think, uh, what do you think people's hesitation

551
00:46:32,300 --> 00:46:35,240
is about buying into a platform?

552
00:46:35,240 --> 00:46:38,420
And let me do the thing where I ask a question and then talk for a little bit.

553
00:46:38,800 --> 00:46:44,760
Uh, like, like, it seems like no one, as, as they say, their debates are tonight, so I

554
00:46:44,760 --> 00:46:46,360
can use all this posturing, right?

555
00:46:46,500 --> 00:46:50,520
No one would agree that like, you should write your own operating system.

556
00:46:50,860 --> 00:46:54,740
And very few people would say you should write a file system and on and on and on.

557
00:46:54,820 --> 00:47:00,980
But then the, uh, as, as, as we know, as a, uh, as a purveyor of platforms, there's a

558
00:47:00,980 --> 00:47:03,360
lot of people who are like, I should build my own platform.

559
00:47:03,480 --> 00:47:04,400
And, and I don't know.

560
00:47:04,460 --> 00:47:06,180
I mean, obviously you've thought about this.

561
00:47:06,180 --> 00:47:09,760
Like, what do you think, uh, what do you, what do you think their, their thinking is

562
00:47:09,760 --> 00:47:11,720
in, in, uh, in an empathetic way?

563
00:47:11,720 --> 00:47:15,240
I mean, obviously their thinking is totally wrong and they just need to call up their local

564
00:47:15,240 --> 00:47:18,200
pivotal rep and buy from us to be snarky about it.

565
00:47:18,200 --> 00:47:21,300
But like, what, uh, like, where are they coming from with that?

566
00:47:22,820 --> 00:47:23,420
Yeah, yeah.

567
00:47:23,420 --> 00:47:27,740
I think a lot of it is kind of the, the, the maker culture that I know that you guys have

568
00:47:27,740 --> 00:47:28,860
touched on in the past.

569
00:47:29,080 --> 00:47:33,340
Um, I think there's also a lot of excitement around, you know, some of the, the open source

570
00:47:33,340 --> 00:47:39,260
tooling that's available now with, with containers and infrastructure as code and all the things

571
00:47:39,260 --> 00:47:43,220
you talked about in the, in the recent podcast is that you've got, you know, dozens and dozens

572
00:47:43,220 --> 00:47:47,960
of products now you can stitch together and as a, as a, as a developer that is, you know,

573
00:47:47,960 --> 00:47:51,940
in this full stack way of thinking, you get really excited about thinking, oh wow, I could,

574
00:47:52,000 --> 00:47:55,020
I could really build, build this and really help our, help our business.

575
00:47:55,580 --> 00:48:00,040
Um, but there's really that, that reality of the, the day two operations that come into

576
00:48:00,040 --> 00:48:03,820
play, where if you build a platform, even if you're successful, a couple of years down

577
00:48:03,820 --> 00:48:08,160
the line, several million dollars into it, you still have a business to, to get on with,

578
00:48:08,160 --> 00:48:12,640
with transforming, you know, so I think it really is this kind of, you know, maker, maker

579
00:48:12,640 --> 00:48:17,120
desire that exists inside a lot of, a lot of companies, um, where they get a lot of, uh,

580
00:48:17,120 --> 00:48:20,860
enthusiasm about some of these new tools that have made it far easier than ever before to

581
00:48:20,860 --> 00:48:22,220
experiment with some of these things.

582
00:48:22,720 --> 00:48:27,520
But, you know, a little bit of this experimentation, um, gives the idea of possibility that doesn't

583
00:48:27,520 --> 00:48:31,160
necessarily mean that you should, you know, go through and you'll fully fund it from a business

584
00:48:31,160 --> 00:48:31,800
point of view.

585
00:48:32,000 --> 00:48:36,240
And as you know, Matt, Matt will tell you, it's now 2016 and there's a lot more polish.

586
00:48:36,240 --> 00:48:40,600
There's a lot more options now, um, than there was even a couple of years ago for something

587
00:48:40,600 --> 00:48:41,220
like this.

588
00:48:41,360 --> 00:48:46,740
So, um, it's kind of this, I think, enthusiasm for, for building and making, um, but fixated

589
00:48:46,740 --> 00:48:49,880
at the, at the platform level rather than kind of the, the application level.

590
00:48:50,200 --> 00:48:50,300
Yeah.

591
00:48:50,420 --> 00:48:55,820
No, you, you know, I, I, this past weekend, and this shows you how exciting my, uh, my inner

592
00:48:55,820 --> 00:48:57,160
thoughts in life are.

593
00:48:57,180 --> 00:49:00,120
I was thinking like, you know, what would I do if I had any choice?

594
00:49:00,140 --> 00:49:01,820
I should go get an economics degree.

595
00:49:01,820 --> 00:49:04,780
That seems fascinating, even though it's called the dismal science.

596
00:49:04,780 --> 00:49:08,420
And then, you know, like most people, what I'm really interested in, I guess is what you

597
00:49:08,420 --> 00:49:11,400
might call like the, uh, the micro micro economics, right?

598
00:49:11,400 --> 00:49:14,480
Like how incentives work and how people decide to do things.

599
00:49:14,480 --> 00:49:17,120
And I don't even know if that's economics, but that's all that's interesting.

600
00:49:17,120 --> 00:49:21,480
Like, I, I, I don't know what to do with interest rates and stuff like that, but it seems like,

601
00:49:21,600 --> 00:49:27,260
uh, it'd be interesting to have like a sort of like super micro economics of software development

602
00:49:27,260 --> 00:49:27,700
design.

603
00:49:27,700 --> 00:49:32,240
And speaking of like snoozers and being fun at parties, but it'd be fun to study like

604
00:49:32,240 --> 00:49:36,520
the, the way that people think and the decisions that they make about their, their code and

605
00:49:36,520 --> 00:49:37,840
architecture and things like that.

606
00:49:37,840 --> 00:49:43,380
Cause I think, I think as always, a lot of it is sort of like fashion driven and just

607
00:49:43,380 --> 00:49:47,880
sort of like, not that that's a bad way of putting it, but the incentives are not always

608
00:49:47,880 --> 00:49:48,420
straightforward.

609
00:49:48,420 --> 00:49:51,360
Just like you were saying, it's like you put it a very nice way.

610
00:49:51,360 --> 00:49:55,960
Like, uh, to put it another way, like, well, what do you expect programmers to do?

611
00:49:56,180 --> 00:49:57,020
They program.

612
00:49:57,520 --> 00:50:03,140
So if, if you put a problem in front of them, their first thing is like, let's program, which,

613
00:50:03,220 --> 00:50:07,520
uh, but then it's, it's the interesting question is like, but then there's these other things

614
00:50:07,520 --> 00:50:08,680
that they don't program.

615
00:50:08,680 --> 00:50:12,920
Like they don't sit down and write a string tokenizer if they're a moderately good programmer.

616
00:50:12,920 --> 00:50:16,720
So like what, when does that switch happen and how, what is that thinking?

617
00:50:16,720 --> 00:50:22,180
So, uh, I'll write that down on my list of, uh, things to do when I win the lottery to,

618
00:50:22,180 --> 00:50:25,080
uh, how to spend my time anyhow.

619
00:50:25,380 --> 00:50:25,660
Nice.

620
00:50:25,780 --> 00:50:25,940
Yeah.

621
00:50:25,960 --> 00:50:28,940
I think we should, we should really get a GoFundMe going for you, Coté, to get that,

622
00:50:28,940 --> 00:50:30,260
uh, micro, micro economics.

623
00:50:30,880 --> 00:50:36,080
I would, I would love to see, seriously, I'd love to see some of the data and the output

624
00:50:36,080 --> 00:50:41,900
around companies with this do it yourself approach versus the, the, uh, the, the buy approach.

625
00:50:41,900 --> 00:50:44,660
And that's a little bit of that ROI kind of conversation you're talking about a little

626
00:50:44,660 --> 00:50:45,780
bit earlier, you know, Coté.

627
00:50:45,780 --> 00:50:50,020
But yeah, I, it's fascinating to see what that economic, you know, data is, what that

628
00:50:50,020 --> 00:50:53,440
output, what that output actually would be for those two different scenarios.

629
00:50:53,640 --> 00:50:54,320
There you go.

630
00:50:54,420 --> 00:50:58,580
Well, on that note of the dismal science, it's a, it's rainy and overcast here.

631
00:50:58,660 --> 00:51:00,840
Are you guys sunny up there or is it rainy?

632
00:51:01,700 --> 00:51:04,120
No, it's going to be like 72 and sunny today.

633
00:51:04,120 --> 00:51:05,920
So don't tell people don't, don't move here.

634
00:51:06,060 --> 00:51:06,500
Very nice.

635
00:51:06,500 --> 00:51:06,820
Yeah.

636
00:51:07,020 --> 00:51:10,740
I, I have, and, and, and I, I'm trying to empathize with you guys.

637
00:51:10,740 --> 00:51:14,440
I've had this, uh, this feeling that I need to just nonstop drink coffee today.

638
00:51:14,440 --> 00:51:15,180
So I get it.

639
00:51:15,180 --> 00:51:17,480
I get why you guys are so big into coffee up there.

640
00:51:17,800 --> 00:51:21,100
It's, it's a, it's, it's a good protection against overcast skies.

641
00:51:21,100 --> 00:51:23,740
Now I guess they drink a lot of tea in London.

642
00:51:23,740 --> 00:51:27,640
So that's their, their fix, but man, you, you gotta, you gotta have coffee.

643
00:51:27,940 --> 00:51:29,860
So, uh, Hey, thanks for being a guest.

644
00:51:30,140 --> 00:51:35,200
Uh, this is fun where, where, if people want to, uh, you know, follow more stuff that you

645
00:51:35,200 --> 00:51:37,620
do or interested in finding out more, where, where should they go?

646
00:51:37,740 --> 00:51:38,480
What should they do?

647
00:51:39,360 --> 00:51:42,160
Uh, I guess maybe not go to my Yahoo email account.

648
00:51:42,380 --> 00:51:44,480
Um, best option.

649
00:51:44,720 --> 00:51:50,800
Uh, best bet is for me is on, uh, Twitter, uh, at Jared Ruckel, J A R E D R U C K L E.

650
00:51:51,180 --> 00:51:51,740
Uh, yeah.

651
00:51:51,740 --> 00:51:54,860
And hang out there, um, do a lot of blogging for pivotal and, uh, try and keep tabs on

652
00:51:54,860 --> 00:51:56,280
what's, uh, what's shaking in the industry.

653
00:51:56,280 --> 00:51:57,900
So I'd love to connect to people that way.

654
00:51:58,200 --> 00:52:01,820
Yeah, no, you're, you're, uh, you're, you've brought some really good posts to the blog.

655
00:52:01,920 --> 00:52:04,960
It's, it's always good to get like new people on and see what they post.

656
00:52:05,020 --> 00:52:07,180
It's, it's, uh, it's fun to have good stuff in the blog.

657
00:52:07,180 --> 00:52:09,540
So that's, uh, you can follow along in the pivotal blog as well.

658
00:52:09,620 --> 00:52:10,720
That's, that's good stuff.

659
00:52:10,720 --> 00:52:14,120
And as always, you can follow, uh, Richard and I in Twitter.

660
00:52:14,220 --> 00:52:14,620
I'm Coté.

661
00:52:14,860 --> 00:52:15,600
What are you, Richard?

662
00:52:16,240 --> 00:52:17,240
At R Saroder.

663
00:52:17,760 --> 00:52:19,940
And, and this has been, uh, thanks for listening.

664
00:52:20,080 --> 00:52:21,360
This has been Pivotal Conversations.

665
00:52:21,360 --> 00:52:26,340
It's always, as we were joking about earlier, it's always good to, uh, add in some, uh, some

666
00:52:26,340 --> 00:52:31,120
reviews on iTunes or just recommend it to your friends or just talk to us wherever and,

667
00:52:31,120 --> 00:52:32,620
and, and tell us that you're listening to it.

668
00:52:32,640 --> 00:52:33,520
It's, it's nice to hear.

669
00:52:33,560 --> 00:52:37,360
And if you want to find the, uh, the show notes, we'll put links to the, uh, the blog

670
00:52:37,360 --> 00:52:40,240
posts that we mentioned and, and, uh, and the news items.

671
00:52:40,340 --> 00:52:46,160
If you go to pivotal.io slash podcast, you can find us, uh, Pivotal Conversations there.

672
00:52:46,160 --> 00:52:50,880
And you can always go to SoundCloud as well to find the, the, uh, the secret backend where

673
00:52:50,880 --> 00:52:51,960
we host our podcast.

674
00:52:52,160 --> 00:52:54,940
It's soundcloud.com slash Pivotal Conversations.

675
00:52:54,940 --> 00:52:59,080
And you should just go ahead and subscribe and get it downloaded automatically.

676
00:52:59,400 --> 00:53:01,680
And with that, we'll see everyone next time.

677
00:53:01,880 --> 00:53:02,420
Bye-bye.