1
00:00:00,000 --> 00:00:02,760
Well, hey listeners, something was up with my microphone.

2
00:00:02,920 --> 00:00:05,220
So whenever I talk, it's a little clicky.

3
00:00:05,480 --> 00:00:08,440
Hopefully that doesn't drive you crazy because this was actually a pretty fun

4
00:00:08,440 --> 00:00:08,980
conversation.

5
00:00:09,120 --> 00:00:12,220
There are a lot of interesting ideas that came up that we didn't get to explore

6
00:00:12,220 --> 00:00:13,900
more, but let's go right into the introduction.

7
00:00:14,180 --> 00:00:16,440
Well, we have another interview that you've arranged, Cora.

8
00:00:16,920 --> 00:00:21,280
And this one, you know, I was reading the initial blog article about just like the

9
00:00:21,280 --> 00:00:22,520
attributes of DevOps stuff.

10
00:00:22,640 --> 00:00:24,400
And I got, I got to be honest.

11
00:00:24,460 --> 00:00:25,740
I was like, I don't know.

12
00:00:25,740 --> 00:00:30,080
It was just, just going to be about, you know, more obvious things that

13
00:00:30,080 --> 00:00:31,400
improve developer experience.

14
00:00:31,400 --> 00:00:37,420
But as, as I read it, it was actually like a very practical list of just like a

15
00:00:37,420 --> 00:00:38,060
punch list.

16
00:00:38,060 --> 00:00:41,540
And I mean that in a good way of just like, here's the minimum stuff to do.

17
00:00:41,540 --> 00:00:43,700
Like here's actual practical things.

18
00:00:43,700 --> 00:00:49,340
Cause a lot of the stuff I've read about DevOps over, DevOps, Dev X over the

19
00:00:49,340 --> 00:00:55,440
years and probably heard at DevOps conferences tends to be, um, I don't know

20
00:00:55,440 --> 00:00:59,060
how I would characterize it just sort of like, well, that would be great, right?

21
00:00:59,060 --> 00:01:01,820
Like just the, uh, the kind of happy land of talking about stuff.

22
00:01:01,820 --> 00:01:05,820
But, uh, this article you, you, you sent over was great because it's, uh, actual

23
00:01:05,820 --> 00:01:07,660
things that, that you can put into practice.

24
00:01:08,320 --> 00:01:09,180
Yeah, absolutely.

25
00:01:09,180 --> 00:01:13,940
It's, uh, it's written by Paul Kelly, who is, uh, one of our labs consultants.

26
00:01:13,940 --> 00:01:18,140
Our, our, our labs team is a team that goes and works, uh, side by side with

27
00:01:18,140 --> 00:01:21,280
developers at different enterprises to help modernize and move their

28
00:01:21,280 --> 00:01:26,780
applications to, uh, modern platforms, uh, whether it's tons of application

29
00:01:26,780 --> 00:01:31,160
service, formerly cloud foundry or, uh, tons of application platform, a

30
00:01:31,160 --> 00:01:32,280
Kubernetes based platform.

31
00:01:32,280 --> 00:01:37,360
But if they, uh, this team focuses a lot with on modernizing applications and, um, and

32
00:01:37,360 --> 00:01:40,660
through that, of course, they're exposed to a lot of different developer

33
00:01:40,660 --> 00:01:42,160
experiences at different enterprises.

34
00:01:42,160 --> 00:01:47,280
And so there's that, but talk, Paul also has a very, uh, a long background

35
00:01:47,280 --> 00:01:50,600
in technical writing as well as R and D.

36
00:01:50,600 --> 00:01:55,500
Um, so really well positioned to understand, uh, developer experience.

37
00:01:55,500 --> 00:01:57,780
And this article, uh, I really recommend it.

38
00:01:57,780 --> 00:01:59,500
We had a fascinating conversation with Paul.

39
00:01:59,860 --> 00:02:04,500
Um, but, uh, the article covers everything from a really solid definition of

40
00:02:04,500 --> 00:02:06,760
developer experience, what it means to the enterprise.

41
00:02:06,760 --> 00:02:12,540
Uh, so I think folks from all levels would benefit from reading the article and, uh, and

42
00:02:12,540 --> 00:02:16,820
as I mentioned, sort of at the end of the interview, this tension between security and,

43
00:02:16,820 --> 00:02:24,520
uh, developer innovation, uh, and, uh, freedom, I guess, and also tips to running your platform

44
00:02:24,520 --> 00:02:30,560
as a product so that you can lead towards a, um, a good developer experience and how important

45
00:02:30,560 --> 00:02:31,060
all of that is.

46
00:02:31,060 --> 00:02:33,100
So it's a great article and we had a great conversation.

47
00:02:33,100 --> 00:02:37,740
So yeah, take a listen and, uh, you know, naturally we start by talking about COBOL.

48
00:02:38,740 --> 00:02:43,440
Well, I, I wanna, I wanna have you introduce yourself here and a little bit guest, but reading

49
00:02:43,440 --> 00:02:50,240
through your background and I was, I was able to, uh, acquire the, the PDF of one of your books

50
00:02:50,360 --> 00:02:53,200
on COBOL thanks to the register and a form there.

51
00:02:53,200 --> 00:02:57,740
I went to micro focus and I tried to use their Legion form, but an error occurred both in Safari

52
00:02:57,740 --> 00:02:58,160
and Chrome.

53
00:02:58,160 --> 00:03:00,120
So I know it's not my, my blockers.

54
00:03:00,460 --> 00:03:03,940
I haven't gotten the chance to read it, but I was, I was like glancing through it.

55
00:03:04,320 --> 00:03:09,760
And, uh, I, I was thinking, you know, uh, you wrote, recently wrote an article on a developer

56
00:03:09,760 --> 00:03:11,260
experience, devX, which is great.

57
00:03:11,260 --> 00:03:17,180
It was like this list of like, how to make things nice for developers, right?

58
00:03:17,180 --> 00:03:18,500
Like almost like a checklist.

59
00:03:18,860 --> 00:03:24,200
Uh, but you know, the combination of all that stuff was making me think of like, like, so why

60
00:03:24,200 --> 00:03:25,660
did we need more than COBOL?

61
00:03:26,900 --> 00:03:28,320
Well, that's a good question, isn't it?

62
00:03:28,420 --> 00:03:34,920
Um, cause as old fashioned to be right in as COBOL is, it's, it's got some good points,

63
00:03:34,920 --> 00:03:40,600
which is that it's very performant and it's good at handling money, which most languages

64
00:03:40,600 --> 00:03:41,140
are not.

65
00:03:41,800 --> 00:03:43,620
Um, that's one of my favorite things to be good at.

66
00:03:43,620 --> 00:03:44,660
I like, I like that.

67
00:03:45,280 --> 00:03:50,760
So, but on the other hand, it is by modern standards, it's not an easy language to work

68
00:03:50,760 --> 00:03:51,060
with.

69
00:03:51,560 --> 00:03:51,960
Yeah.

70
00:03:52,120 --> 00:03:57,700
And, and, and do you think, well, well, first of all, what do you mean by it handles money?

71
00:03:57,700 --> 00:03:59,560
Well, that's an intriguing thing.

72
00:03:59,620 --> 00:04:05,860
Well, so most languages, their, their default for, for doing any kind of calculation would

73
00:04:05,860 --> 00:04:07,620
be a float or a double.

74
00:04:08,620 --> 00:04:15,720
And those are binary types and, um, they don't do money well because money is usually decimal.

75
00:04:16,180 --> 00:04:16,620
Yeah.

76
00:04:16,980 --> 00:04:20,980
And so you get rounding errors and that becomes particularly significant when you're doing

77
00:04:20,980 --> 00:04:22,020
interest calculations.

78
00:04:22,020 --> 00:04:24,260
Those errors can mount up really fast.

79
00:04:25,040 --> 00:04:33,820
COBOL has, um, has got a kind of decimal type, which is from memory, possibly comp three, but.

80
00:04:34,620 --> 00:04:36,020
Was it designed, you think?

81
00:04:36,100 --> 00:04:37,280
Was it designed for that purpose?

82
00:04:37,460 --> 00:04:41,520
It was designed for that purpose because the first thing it was used for was business applications

83
00:04:41,520 --> 00:04:44,380
and what you handle in business, you handle money.

84
00:04:45,120 --> 00:04:45,720
Oh, fascinating.

85
00:04:46,000 --> 00:04:49,860
So wait, what, how, what, where does your background in COBOL come from?

86
00:04:49,860 --> 00:04:59,460
It comes from the many years I worked at Microfocus, um, who were for a long time effectively

87
00:04:59,460 --> 00:05:01,240
known as the kind of the COBOL company.

88
00:05:01,380 --> 00:05:06,160
They were the, the, the first company to put COBOL actually on, on, uh, microprocessors

89
00:05:06,160 --> 00:05:07,720
on PCs.

90
00:05:07,720 --> 00:05:10,520
And I mean, they did that even before the IBM PCs.

91
00:05:10,520 --> 00:05:15,020
I think they were, I think their first product probably around something like a rare black box.

92
00:05:15,740 --> 00:05:22,640
If, uh, if anyone has that long a memory and I, I joined them in the, I guess the, the early

93
00:05:22,640 --> 00:05:23,280
nineties.

94
00:05:23,920 --> 00:05:30,020
Uh, and at that time their, their product was doing fabulously well because people had business

95
00:05:30,020 --> 00:05:36,120
applications and they wanted to run them on microcomputers and micro focus was pretty much

96
00:05:36,120 --> 00:05:37,920
the only game in town for that back then.

97
00:05:39,160 --> 00:05:45,920
And so, you know, you know, I'm like, like I'm, I'm interested in talking more about like

98
00:05:45,920 --> 00:05:51,100
the, the, the world of COBOL because like, I feel like we're in the middle of like, you

99
00:05:51,100 --> 00:05:52,700
know, within, in the DevOps world.

100
00:05:52,700 --> 00:05:57,580
Like one of my, one of my theories, I don't know if it's like me being snarky or, or not,

101
00:05:57,580 --> 00:06:04,240
but like, is like, you know, here we are in 2022 was last year, but now in 2023 and we're

102
00:06:04,240 --> 00:06:10,020
sort of like, uh, rediscovering and rebuilding a good developer stack, right?

103
00:06:10,020 --> 00:06:12,600
Like there's a lot of commentary and a lot of products doing that.

104
00:06:12,800 --> 00:06:19,440
And so I wonder in, in your like experience since then, and then through like, you know,

105
00:06:19,440 --> 00:06:22,460
let's say like the, the, the windows era of things.

106
00:06:22,460 --> 00:06:27,420
And then we had like the web and then there was this like rich internet application, like

107
00:06:27,420 --> 00:06:28,300
mobile thing.

108
00:06:28,480 --> 00:06:33,680
And I don't know what you would call after that where, where we are now cloud maybe, but

109
00:06:33,680 --> 00:06:40,400
like, yeah, like, like my, my sense is, and maybe this is just part of being an aging

110
00:06:40,400 --> 00:06:45,660
technologist is that like, I don't know, every five years, every five or 10 years, we just

111
00:06:45,660 --> 00:06:48,920
like rip everything down to the studs and totally rebuild it.

112
00:06:49,080 --> 00:06:49,380
Right.

113
00:06:49,740 --> 00:06:53,500
And, and hence the sort of like, why did we need more than COBOL?

114
00:06:53,560 --> 00:06:53,760
Right.

115
00:06:53,760 --> 00:07:01,320
And I think like, I don't know the COBOL space very well, but I would imagine like a lot of

116
00:07:01,320 --> 00:07:05,480
the kind of tools that, that we would be talking about for like developer experience nowadays

117
00:07:05,480 --> 00:07:10,380
for whatever type of development you're doing sort of like have existed in multiple

118
00:07:10,400 --> 00:07:11,660
times in the COBOL world.

119
00:07:11,660 --> 00:07:12,060
Right.

120
00:07:12,060 --> 00:07:17,160
To build up all the stuff beyond the languages that you would need and kind of the tools

121
00:07:17,160 --> 00:07:20,780
and integrating them together that like you would have that stack.

122
00:07:21,360 --> 00:07:27,680
So anyhow, I mean, it does seem like it, it, it does seem like it's, it's interesting, at

123
00:07:27,680 --> 00:07:32,780
least to me to think about like, at what point were we like, this thing handles cash really

124
00:07:32,780 --> 00:07:34,500
well, but we got to start over.

125
00:07:34,500 --> 00:07:34,860
Right.

126
00:07:34,860 --> 00:07:39,360
Like we can't, we can't pull it forward, like, and therefore we're going to have to

127
00:07:39,360 --> 00:07:42,240
like, get rid of everything and just kind of start from scratch.

128
00:07:42,780 --> 00:07:46,900
Cause it feels like we're kind of at the beginning of doing that with a lot of, with

129
00:07:46,900 --> 00:07:52,500
like the, we don't even have a name for it anymore, but with the DevX stack of things

130
00:07:52,500 --> 00:07:53,180
that we have.

131
00:07:53,700 --> 00:07:59,260
Well, it's always struck me that IT has got a lot in common with the fashion industry in

132
00:07:59,260 --> 00:08:04,780
the, you know, in the trends, the, the, the, the hemlines go up, the hemlines go down.

133
00:08:04,880 --> 00:08:06,340
Everyone gets very excited.

134
00:08:07,060 --> 00:08:11,000
Um, but to some extent, the same stuff comes around again and again.

135
00:08:11,660 --> 00:08:18,780
Um, one of the things that kind of, uh, struck people where at the beginning of the web thing,

136
00:08:18,860 --> 00:08:25,220
so web one zero was how much it looked like what IBM had built for, um, for mainframe

137
00:08:25,220 --> 00:08:28,880
applications, which was Kix, Kix is pseudo conversational.

138
00:08:29,460 --> 00:08:33,540
You have the illusion that you're interacting with the computer, but most of the time you're

139
00:08:33,540 --> 00:08:36,600
not, you're just sort of terminal and every so often it's going to send something off

140
00:08:36,600 --> 00:08:37,580
and you get a reply back.

141
00:08:37,960 --> 00:08:41,180
Well, that's exactly how the first web applications worked.

142
00:08:41,900 --> 00:08:44,840
They were exciting and Kix was, was dull.

143
00:08:45,580 --> 00:08:49,920
So everyone went through a kind of phase of how can we make our Kix applications look like

144
00:08:49,920 --> 00:08:53,900
web applications, whether or not that actually made sense.

145
00:08:54,400 --> 00:08:56,620
So there's that.

146
00:08:57,820 --> 00:09:00,900
Having said that, I guess there, you know, there are genuine improvements that have happened

147
00:09:00,900 --> 00:09:04,580
in the technology stack over the years, but I think when you're up close to it, it's hard

148
00:09:04,580 --> 00:09:05,640
to see what they are.

149
00:09:06,480 --> 00:09:10,060
And it's only when you look back, you think, yeah, that was an improvement or no, that was

150
00:09:10,060 --> 00:09:11,260
a really terrible idea.

151
00:09:12,240 --> 00:09:19,100
And those two books that you wrote about COBOL, um, they are, so they're written for Java and

152
00:09:19,100 --> 00:09:20,320
.NET developers.

153
00:09:20,600 --> 00:09:21,260
They were, yeah.

154
00:09:21,600 --> 00:09:28,100
And it's, um, and so they provide a guidance on how to, is it, are you actually converting the code?

155
00:09:28,100 --> 00:09:31,100
Is it automatically converted from COBOL to Java.NET?

156
00:09:31,100 --> 00:09:31,600
So, no.

157
00:09:31,600 --> 00:09:36,980
Well, so, um, I mean, I don't want to spend too long to have Microfocus's sort of

158
00:09:36,980 --> 00:09:39,980
proprietary technology, but they're probably happy if I do.

159
00:09:40,520 --> 00:09:47,120
Um, they have what they call the visual COBOL compiler and that will compile COBOL code, you know,

160
00:09:47,120 --> 00:09:53,620
genuine COBOL code written any time in the last, what, 60 years now, and they can compile that to

161
00:09:53,620 --> 00:09:56,800
either run on JVM or run on .NET.

162
00:09:57,600 --> 00:10:03,280
And then in addition, they added enough object-oriented features that you could actually make that code

163
00:10:03,280 --> 00:10:06,360
play nicely with those new languages.

164
00:10:06,360 --> 00:10:12,860
So, for people who have business logic, you know, a lot of, have invested a lot of money in, in business logic

165
00:10:12,860 --> 00:10:15,500
written in COBOL, it's a way to pull it forward.

166
00:10:16,900 --> 00:10:17,380
Interesting.

167
00:10:17,380 --> 00:10:20,440
By recompiling it and then making it talk to newer things.

168
00:10:20,740 --> 00:10:26,480
Does that actually make it, uh, like, have you ever seen these COBOL applications then even run in containers

169
00:10:26,480 --> 00:10:28,420
and, and run on Kubernetes?

170
00:10:28,580 --> 00:10:29,240
Is that a thing?

171
00:10:29,760 --> 00:10:30,460
It is a thing.

172
00:10:30,560 --> 00:10:37,840
Uh, in the second book that I wrote, I, uh, did a, uh, there, there's a kind of worked example of running a COBOL app in, in Kubernetes.

173
00:10:38,680 --> 00:10:50,080
And in fact, one of the things I did when I first started at Pivotal a few years back was I, I did a little demo of running a Spring Boot on, um, the, on Cloud Foundry.

174
00:10:51,820 --> 00:10:53,320
Spring Boot with COBOL code.

175
00:10:53,400 --> 00:10:54,760
Sorry, Spring Boot with a COBOL.

176
00:10:54,960 --> 00:10:55,420
COBOL code.

177
00:10:55,600 --> 00:11:04,500
COBOL business logic, but then effectively made that a jar consumed by a Spring Boot front end so that you could just package it and run it in Cloud Foundry.

178
00:11:04,500 --> 00:11:11,560
And hey, Presto, you were doing, you know, interest calculations using, um, using COBOL, but running on Cloud Foundry.

179
00:11:11,820 --> 00:11:12,180
Wow.

180
00:11:12,240 --> 00:11:13,280
You could finally handle money.

181
00:11:13,860 --> 00:11:15,120
And you could finally handle money.

182
00:11:15,580 --> 00:11:19,980
Because in Java, when you want to handle money, you have to use big decimal and that code is not easy to read.

183
00:11:20,720 --> 00:11:21,700
Best of both worlds.

184
00:11:22,740 --> 00:11:23,340
Yeah, exactly.

185
00:11:24,260 --> 00:11:33,840
So, wait, tell us a little bit about that transition into, um, into Pivotal and this sort of pivot in your own career, I guess, because I guess at that point you became more of a consultant.

186
00:11:34,340 --> 00:11:34,880
I did, yeah.

187
00:11:34,880 --> 00:11:35,140
I did, yeah.

188
00:11:35,140 --> 00:11:44,600
And that was kind of interesting to me because I spent my whole career up to then really in, in effectively R&D, doing package product.

189
00:11:45,240 --> 00:11:49,120
And working as a consultant was, was very different in lots of ways.

190
00:11:49,160 --> 00:12:01,120
One of the things it, it, it gave me a much better appreciation for the problems that people developing business applications have, because up to then I'd really been doing, I guess you call it more systems programming.

191
00:12:01,920 --> 00:12:14,220
But also it did, but also it did, the thing I liked about it was it did give me a chance to go and talk to people a bit, because when you're in R&D, you're kind of in the ivory tower and certainly micro focus.

192
00:12:14,220 --> 00:12:17,440
So, we got to speak to customers once a year at a user conference.

193
00:12:18,520 --> 00:12:29,920
Was that also your first experience doing things like paired programming and, and, um, and other such sort of, uh, collaboration techniques that Pivotal employed?

194
00:12:30,380 --> 00:12:37,400
We used a bit of pair programming at Microfocus, but it was never kind of part of our core programming model.

195
00:12:37,540 --> 00:12:40,680
We used to pair up mainly to solve difficult problems.

196
00:12:41,960 --> 00:12:43,880
So, it was a huge shift for you.

197
00:12:43,880 --> 00:12:45,420
It was a huge shift in every way.

198
00:12:45,660 --> 00:12:49,020
I, I definitely had culture shock for, for several weeks.

199
00:12:49,600 --> 00:13:00,360
And do you feel so, so you've written this article, um, so I guess just, you know, so the inspiration for this particular conversation, uh, was rooted in a, in a blog that you wrote.

200
00:13:00,380 --> 00:13:04,140
For the VMware Tanzu called the developer perspective on developer experience.

201
00:13:04,700 --> 00:13:04,900
Yeah.

202
00:13:05,040 --> 00:13:19,080
Um, and so I guess, uh, there's the experience, I guess, working as a consultant doing paired programming and guiding other developers into not improving, not just our code, but also their, their methodologies.

203
00:13:19,680 --> 00:13:30,000
Um, as well as I guess this whole revolution that we're experiencing in terms of DevOps and the kinds of automation systems that we are now capable of creating.

204
00:13:30,780 --> 00:13:44,200
Um, so I guess, I, I, it seems to me that those two would be the biggest sort of influencers in terms of, uh, tuning in, I guess, to this, to what exactly might make a developer experience good.

205
00:13:44,200 --> 00:13:46,500
Or, or is that not, is it broader than that?

206
00:13:46,500 --> 00:13:58,680
Well, to be honest, it was broader than that in that, again, when you work at, um, you know, when you work at a software vendor, they treat their programmers really well for obvious reasons.

207
00:13:59,520 --> 00:14:04,980
And they make sure they have all the equipment they need to work and that they can find out what they need to know and everything else.

208
00:14:05,620 --> 00:14:17,460
Working as a consultant and working particularly with a lot of banks and a lot of telcos, those organizations don't really see themselves in the business of developing software.

209
00:14:18,180 --> 00:14:22,580
But they absolutely are that's now the core of their business.

210
00:14:23,620 --> 00:14:29,600
And I think they're kind of waking up to that now, but for a long time, they saw it as just another thing that had to get done.

211
00:14:30,320 --> 00:14:32,240
And they don't treat their developers well.

212
00:14:33,300 --> 00:14:55,940
Um, you know, the book, the, the, um, the new king makers, that's that, which basically talked about how, uh, the combination of, I guess, public cloud and the explosion of open source software really shifted who had the, the power to sort of crown any kind of technology, uh, as, as more, more successful.

213
00:14:55,940 --> 00:15:02,120
And how, you know, it was more, it was increasingly important to make sure that developers were happy, that they were productive.

214
00:15:02,120 --> 00:15:07,920
And it feels like, I don't, I don't remember what year that book was written, but I feel like it's at least, could it be 50, 15 years?

215
00:15:08,640 --> 00:15:09,580
Something like that.

216
00:15:09,640 --> 00:15:11,300
It's a, it's surprising, I guess.

217
00:15:11,300 --> 00:15:13,320
I mean, it is, and it isn't surprising, right.

218
00:15:13,320 --> 00:15:25,860
To hear that, um, developers are still maybe in some places under a model that, that really like, uh, I think if you're, if you don't see it

219
00:15:25,860 --> 00:15:38,380
in person, often, if you're not exposed to it by working with enterprises, it's easy to assume that, that most of the world has, uh, sort of modernized their ways to, to prioritize developer.

220
00:15:38,620 --> 00:15:40,380
No, they're a cost center.

221
00:15:41,500 --> 00:15:43,160
And that's really the root of the problem.

222
00:15:43,160 --> 00:15:44,020
They're a cost center.

223
00:15:44,540 --> 00:15:52,640
And even if you can treat them as a cost center, I don't think they, my feeling is that these large enterprises are not thinking about it rationally.

224
00:15:53,560 --> 00:16:03,800
So one of the things that I've seen, uh, uh, especially at banks is that they went through a big outsourcing phase back in the nineties and noughties.

225
00:16:04,560 --> 00:16:10,400
So they're outsourced a lot of their development and now effectively, some of their development seems to be outsourced to other outsourcers.

226
00:16:10,400 --> 00:16:21,640
I'm not sure how it works, but effectively you, you could be at a large retail bank and half their, or maybe more than half their developers not only aren't employed directly by the bank.

227
00:16:22,580 --> 00:16:26,720
Um, they're employed by some kind of third party outsourcer.

228
00:16:26,720 --> 00:16:34,580
But that third party outsourcer is the, the person determining what laptop they have and all the rest of it.

229
00:16:34,900 --> 00:16:37,580
And their priority presumably is profit.

230
00:16:38,220 --> 00:16:48,420
So I have worked, I've paired with developers who have such poor equipment that we are waiting for half an hour for them to boot up their machine and start Eclipse.

231
00:16:48,840 --> 00:16:49,360
Wow.

232
00:16:49,800 --> 00:16:54,580
Now, in terms of, you know, at the end of it, all the bank is paying for that.

233
00:16:55,460 --> 00:17:09,180
The money that's been saved by giving that developer a cheap, crappy computer, I would, I would suggest is, is wasted in, in a few weeks by the amount of time that they are not productive.

234
00:17:10,560 --> 00:17:11,080
Wow.

235
00:17:11,480 --> 00:17:18,860
One kind of example where this kind of cost center mentality where, well, why would we want to give them nice equipment?

236
00:17:19,140 --> 00:17:21,360
It's very short sighted.

237
00:17:21,420 --> 00:17:23,260
You're, you're throwing money down the drain.

238
00:17:23,580 --> 00:17:28,440
So again, when you're, you know, banks, obviously they can, they can lease their own employees.

239
00:17:28,580 --> 00:17:44,480
They could say, well, we'll give you decent laptops, but possibly with their outsourcing contracts, they need to be more specific about not only do you give me, you know, 50 developer bodies to do this work, but I want them equipped in this way.

240
00:17:45,000 --> 00:17:53,860
It's, it's ironic because they're, they're trying to do more with less, more, you know, more, more, more, I guess, more work with, with, uh, wherever salaries and costs are lower.

241
00:17:54,060 --> 00:17:54,460
Yeah.

242
00:17:54,460 --> 00:18:03,920
In reality, they, they're, they're kicking, they're shooting themselves in the foot because they're, they're paying less, but they're also getting less efficiency because developers are blocked.

243
00:18:04,000 --> 00:18:07,920
And so developers are blocked, um, communication is difficult.

244
00:18:07,920 --> 00:18:15,320
I think, I think you're starting to see, and again, I don't have any statistics or anything to pack this up.

245
00:18:15,360 --> 00:18:25,260
This is purely anecdotal, but I've certainly, we, we've had conversations with, with organizations who are now kind of wanting to start bring, bringing more back in house again.

246
00:18:26,000 --> 00:18:34,760
Um, because of the problems of distance, um, time zones, all those things that make, make the outsourcing model difficult.

247
00:18:35,000 --> 00:18:41,380
And then on top of that, as I say, you've got this kind of thing, the outsourcers themselves, they want to maximize their profit naturally.

248
00:18:42,040 --> 00:18:42,520
Right.

249
00:18:42,580 --> 00:18:53,860
You make, and you make it very clear, actually, in your article that the two things that developer experience tight or two of the big, big things that build a good developer experience are tied to is, um, growth for the company and also retention.

250
00:18:54,040 --> 00:18:54,520
Yeah.

251
00:18:54,520 --> 00:19:13,180
So if you're kind of, you know, if, if working for, you know, even if working as a kind of an outsource contractor for bank X means that you get treated better than the other people in an outsourcing organization, I suspect you'll probably find that the good talent will gravitate towards bank X.

252
00:19:14,840 --> 00:19:15,840
It must be, yeah.

253
00:19:15,840 --> 00:19:24,460
So what, what, you know, what, what, what we're talking about here is, is, uh, it's making me think like, like, you know, when I was reading through your article,

254
00:19:24,520 --> 00:19:38,740
well, of course I was, I was, uh, agreeing and just like, you know, as, as Cora was reacting to like the situation, uh, you're talking about, like, well, I, I think, I think the three of us having kind of the role, like you're saying, we go out and talk with a lot of people.

255
00:19:38,740 --> 00:19:45,320
It's, it's, it's, it's still shocking, but not incredibly surprising, right.

256
00:19:45,320 --> 00:19:47,280
That, that like, there's this craziness going.

257
00:19:47,280 --> 00:19:54,500
So what, one of the things I was wondering and that I struggle with is like, so who needs to hear this, right?

258
00:19:54,500 --> 00:19:58,780
Like, like, like who is it in the organizations who's like, oh, right.

259
00:19:59,400 --> 00:20:05,620
I never thought of that before or, or something like there's, there's some kind of like disconnect somewhere.

260
00:20:05,620 --> 00:20:16,540
Like, like, and just to pile on as, as is my, uh, my habit, like, you know, one of the, one of the things linked off from your article was, uh, uh, like a Forrester consulting thing that, that we have available.

261
00:20:16,760 --> 00:20:24,200
And it was, uh, you know, I didn't look up the methodology for the survey, but like, you know, 75% of executives agree that software is important.

262
00:20:24,280 --> 00:20:24,680
Right.

263
00:20:24,720 --> 00:20:32,260
And so there is like, kind of, as you were saying, everyone agrees with that 2010 software is eating the world thing.

264
00:20:32,720 --> 00:20:37,860
And yet, like, it's to use my favorite kind of gross analogy, right.

265
00:20:37,880 --> 00:20:42,400
It's like, everyone says flossing your teeth is good, but probably not everyone does it.

266
00:20:42,400 --> 00:20:50,460
So there's like someone in your head that, that hasn't decided to, uh, to, to get a better laptop basically for developers.

267
00:20:50,820 --> 00:20:51,220
Yeah.

268
00:20:51,220 --> 00:20:52,400
And it's a good question.

269
00:20:52,400 --> 00:21:09,100
I mean, I, I kind of, I was hoping this, this particular blog would, would, would reach people in the C-suite because in the end they're the people who make the big decisions, but that kind of, we always blame accountants.

270
00:21:10,600 --> 00:21:16,760
Which isn't, I don't think entirely fair because presumably accountants also work within a framework and they have their own goals to hit.

271
00:21:16,920 --> 00:21:21,260
Their, their laptop might take 45 minutes to compute an Excel macro.

272
00:21:21,820 --> 00:21:34,600
But the point is, whoever it is who's kind of making those budgetary decisions, it needs to be kind of within that framework that says, well, if we save money here, is it costing us money over there?

273
00:21:34,980 --> 00:21:40,680
And I, I'd say that it is, but I don't think that those decisions are always taken like that.

274
00:21:40,680 --> 00:21:48,240
They're kind of very much a kind of, you know, we, we have a budget of this, this year for, for, for hardware or whatever it happens to be.

275
00:21:48,280 --> 00:21:49,360
And we're not going to go over that.

276
00:21:50,980 --> 00:22:07,920
I mean, one thing that really struck me as I was reading your article is that the, you know, the term, anytime you have something like a term like developer experience, at least for me, like the, the first time I hear that term, my sort of gut instinct is to go towards the, it's, it's a term that implies sort of a human, it's a human experience.

277
00:22:07,920 --> 00:22:08,140
Right.

278
00:22:08,140 --> 00:22:12,480
So it's, so there's thoughts that it can elicit about like, are my developers happy?

279
00:22:12,660 --> 00:22:26,640
Are they, and it, and, and, and yes, those things might be part of it, but what I really liked about your article and where I think it would be really effective for a C-suite to see it is that it's, it's really, it, it really concentrates on the business decision of it.

280
00:22:26,640 --> 00:22:26,820
Right.

281
00:22:26,840 --> 00:22:38,540
It's, it is a business decision and developer experience is defined as the, the ease with which software can be created and sent down the workflow all the way to production.

282
00:22:38,540 --> 00:22:38,780
Right.

283
00:22:38,780 --> 00:22:47,600
So when people think about DevOps or automation, if they can get it all right, the, the end result of that is developer experience.

284
00:22:47,940 --> 00:22:56,560
It's not this other thing that you stick on the left-hand side of it so that, you know, developers are, with a goal of a developer being happy.

285
00:22:56,640 --> 00:23:05,760
It's the entire process that already exists in conversations under other terms, being a business, a benefit to your, to your bottom line.

286
00:23:06,280 --> 00:23:12,340
If you make those people happy in the first place, they're going to try harder to solve all the other problems for you.

287
00:23:12,380 --> 00:23:13,180
And that's what you want.

288
00:23:13,920 --> 00:23:26,500
And again, I think there's kind of, I don't know, again, I'm speculating, but some of this is kind of this, this idea that we have a production line and that therefore all the cogs in the machine

289
00:23:26,500 --> 00:23:32,500
are exactly the same will perform exactly the same given the same inputs, but people are not like that.

290
00:23:33,700 --> 00:23:35,520
And they're not like that to be honest.

291
00:23:35,520 --> 00:23:54,360
They're not like that even when they are on an old fashioned production line, assembling automobiles, because, you know, the, I think the, the, the Japanese showed us that having a less kind of, um, us and them kind of split between management and workers made for better productivity and better quality.

292
00:23:56,360 --> 00:24:07,360
And I, you know, I think it applies the same, uh, you know, but more so something like, um, software development, which is a kind of intellectual activity where you're being asked to sit and think all day.

293
00:24:08,080 --> 00:24:12,980
Right. And, and, and, and by smoothing everything else out, you allow space for that.

294
00:24:13,180 --> 00:24:13,580
Yeah.

295
00:24:13,660 --> 00:24:16,780
Right. Right. You're hiring talent. Give them, give them an opportunity.

296
00:24:17,240 --> 00:24:24,400
Yeah. And don't make it hard for them. Make it, you know, that's the other thing is make the on ramps such as easy for people to do the right thing.

297
00:24:25,180 --> 00:24:30,940
Because again, you see this kind of thing again and again, that you, you make it hard for people.

298
00:24:31,600 --> 00:24:38,120
So if you make it hard for people to get what they need, they either give up and they don't do anything.

299
00:24:38,240 --> 00:24:45,300
Or if they're motivated, they will find a workaround and now they're not using your guardrails at all.

300
00:24:46,240 --> 00:24:49,780
So you've lost control, but you've also wasted a lot of everyone's time.

301
00:24:50,940 --> 00:24:55,220
Make, make, make it easy for people to do the right thing. Give them the on ramps to get what they need.

302
00:24:56,600 --> 00:25:09,800
Well, well, as you know, you're, you're using the word there and that's, that's one thing that I think you mentioned quite a bit is the, not only like the on ramp to just doing development, but it's almost like the daily on ramp.

303
00:25:09,880 --> 00:25:10,120
Yeah.

304
00:25:10,480 --> 00:25:20,360
Right. Like the, and you know, I haven't, I haven't read, you know, stories and lore about this kind of thing for, for a while.

305
00:25:20,360 --> 00:25:31,160
But I remember when I was a younger developer, right. There was, there was a lot of time being spent talking about this word wasn't used, but as we would say nowadays, like achieving a state of flow.

306
00:25:31,160 --> 00:25:40,400
Right. Or I think to use maybe an older word concentration, right. And that, you know, there's all this other stuff associated with what flow is, but just like, you know, you got to sit.

307
00:25:40,480 --> 00:26:01,080
And concentrate and, and not be interrupted. And it seems like that seems like one of the more important, impactful things. Like how do you actually get the developer to just start coding, right. And, and maintain their concentration.

308
00:26:01,720 --> 00:26:26,900
But also one of the things that like, maybe is very difficult to do and care about. I, I don't know, but what's, what's, what's your thinking about how you like get people just to like, get to the part where they're typing and, and, you know, and to escape from the lines of code, like thing, like, sure. Sometimes not typing is good too, but you know, where you're like solving the problems and working on delivering that business value and stuff.

309
00:26:27,720 --> 00:26:30,220
Yeah. That's kind of, that's kind of, that's kind of, that's kind of quite a hard one.

310
00:26:32,320 --> 00:26:43,340
And again, the, the, the, the modern kind of desktop environment is not by default conducive to that, because unless you, unless you take the trouble to switch off, you know, email alerts and that thing.

311
00:26:43,340 --> 00:26:51,820
And again, I've paired with so many people, they've got an email alert popping in every 30 seconds and a Teams thing every 60 seconds.

312
00:26:52,240 --> 00:26:55,200
So how on earth do you concentrate with all that going on?

313
00:26:56,940 --> 00:26:57,700
Like you don't.

314
00:26:58,620 --> 00:26:58,900
Yeah.

315
00:26:59,140 --> 00:26:59,360
Yeah.

316
00:26:59,360 --> 00:27:18,660
I remember early, I get maybe way back in 2015 when I first started working at Pivotal, one of the, exactly this, one of the things that like was a little weird to wrap my head around is like, of course, in, in the, or as we say nowadays, Tanzu Labs, but formerly Pivotal Labs, like they, they would do pair programming on like a shared workstation.

317
00:27:18,660 --> 00:27:23,800
And I remember asking like, what's that laptop over on a podium for, and they're like, oh, that's where you can go check email.

318
00:27:24,520 --> 00:27:27,080
But there's just like this very much.

319
00:27:27,080 --> 00:27:33,060
So a separation of like, here's the coding keyboard and there's the farting around keyboard over there.

320
00:27:33,320 --> 00:27:34,920
But it does seem like that.

321
00:27:35,740 --> 00:27:41,420
And, and, and, and the, the other thing is like, that's just, it's not even a tip of an iceberg.

322
00:27:41,540 --> 00:27:46,020
That's just like a particle floating in the air of like the stack of stuff to worry about.

323
00:27:46,020 --> 00:27:46,280
Right.

324
00:27:46,280 --> 00:27:51,740
Like it goes on and on and on just to like, focus on like, here's us coding.

325
00:27:51,740 --> 00:27:54,740
There's so many other things to, to, to stress out about.

326
00:27:56,040 --> 00:27:56,520
Yeah.

327
00:27:56,960 --> 00:28:08,600
When you go in for these engagements and you're working with developers, sort of side by side pair programming to either, you know, I guess, move applications, maybe from traditional VMs into some sort of platform.

328
00:28:09,600 --> 00:28:23,080
I mean, obviously you're, you're then experiencing the same, either, you know, pain or obstacles that they do when they face the entire automation, I guess, yeah, pipeline that may be available to them.

329
00:28:23,380 --> 00:28:37,060
Do you, like, how often do you find that in your role, pair programming with the developers to move applications that you can make a significant impact on the rest of the organization that is responsible for the automation?

330
00:28:37,880 --> 00:28:43,680
And I guess, and also, do you see that getting better over time with technology changing?

331
00:28:44,140 --> 00:28:51,600
That's a good question because, I mean, the, the, the sort of the, the labs model of working is that engagement tends to be quite short.

332
00:28:52,360 --> 00:29:06,640
So we usually leave a report at the end and we'll say, well, that these are the things you might want to think about if you really want to get stuff done, but we don't always get the chance to go back and, and see how much of an impact it's made.

333
00:29:06,740 --> 00:29:12,540
I mean, I think, I think, I think over time, you know, there's a kind of drip drip, maybe they gradually get the message.

334
00:29:14,040 --> 00:29:15,180
Well, that's important, right?

335
00:29:15,240 --> 00:29:27,000
I mean, just somebody coming in with fresh eyes and, and being able to summarize it and document it and get it into the right hands of the right people should make an impact.

336
00:29:27,400 --> 00:29:27,980
You would hope.

337
00:29:28,240 --> 00:29:34,500
I mean, at the end of it all, they, they kind of, these organizations pay us because they say they want help to improve their process.

338
00:29:34,680 --> 00:29:40,420
So you would hope that they would listen and we say, Hey, there are other things in your process that you haven't even thought about.

339
00:29:41,120 --> 00:29:41,480
Right.

340
00:29:41,560 --> 00:29:43,040
That haven't, that have ramifications.

341
00:29:43,320 --> 00:29:44,600
And they're having a real impact.

342
00:29:44,860 --> 00:29:45,160
Right.

343
00:29:45,500 --> 00:29:45,700
Right.

344
00:29:45,760 --> 00:29:55,640
I mean, you also mentioned in your article, this tension between security and, you know, really letting your developers be a little bit more free and experiment.

345
00:29:56,820 --> 00:29:57,260
Yeah.

346
00:29:57,540 --> 00:29:57,940
Yeah.

347
00:29:58,220 --> 00:29:59,640
And trying to reach a middle ground there.

348
00:29:59,640 --> 00:29:59,820
Right.

349
00:29:59,860 --> 00:30:03,840
And I guess not, not, not to compromise security and production, but to reach a middle ground.

350
00:30:04,920 --> 00:30:05,320
Yeah.

351
00:30:05,700 --> 00:30:14,360
And again, you see, you see too often that even in the kind of development platforms, if you want a resource, it's a ticket process.

352
00:30:15,160 --> 00:30:19,560
And you not only have to raise a ticket, you have to say what your expected traffic is.

353
00:30:20,240 --> 00:30:20,980
Well, I don't know.

354
00:30:21,000 --> 00:30:21,880
I haven't built it yet.

355
00:30:22,380 --> 00:30:29,840
You know, it's kind of, some of this, some of these processes, they, they kind of, they are, they're very heavy.

356
00:30:29,860 --> 00:30:35,480
But anyway, in the design for, we are now, we are now standing up a big heavy duty production system.

357
00:30:36,060 --> 00:30:41,180
And you're using that same process for someone who's just trying to get something set up quickly in dev to do a prototype.

358
00:30:41,820 --> 00:30:42,020
Yeah.

359
00:30:42,920 --> 00:30:53,960
I, I spent, I mean, part of, you know, before I joined Pivotal as well, I had done a lot of consulting and, and hands-on work and, you know, worked for different companies with different kinds of computers.

360
00:30:53,960 --> 00:31:03,960
And I found it always a bit, you know, speaking of security, like, you know, part of my brain under understands security, but part of me was always also very demoralized.

361
00:31:04,700 --> 00:31:13,820
Whenever I would encounter a situation where either I didn't have administrative privileges to install something basic, or I would try to help somebody who didn't have administrative privileges.

362
00:31:13,820 --> 00:31:16,820
Because I just, I really find it, yeah, it's, it's just demoralizing.

363
00:31:16,940 --> 00:31:17,800
It really is.

364
00:31:18,020 --> 00:31:23,320
And again, you see it again and again, that they, they're kind of developers on Windows laptops.

365
00:31:24,580 --> 00:31:39,860
And either they can't install anything, although that's rarer for developers, but even the developers, they have to go through this kind of tedious process of requesting admin rights that they will then get for 24 hours.

366
00:31:40,560 --> 00:31:47,800
So they can install something, you know, it's, and it's demoralizing, especially when you have to do that every day of the week.

367
00:31:49,540 --> 00:31:57,540
And I mean, I worked with a, again, with a telco, we were working with people who are being expected to containerize an application.

368
00:32:00,720 --> 00:32:06,160
But their laptops weren't really powerful enough to run containers, they were just too slow to run Docker.

369
00:32:06,800 --> 00:32:13,500
And then I said, hey, if we could use the Windows system subsystem for Linux, that would be great, because we could install some useful tools.

370
00:32:13,880 --> 00:32:17,600
But we couldn't get that working on their laptop, even with the administrative privileges.

371
00:32:18,700 --> 00:32:28,780
They'd kind of lock down stuff so that effectively, I don't know if you ever tried to get set up WSL on a Windows machine, but you have to kind of enable some stuff in the OS.

372
00:32:29,180 --> 00:32:33,380
And then you have to get Windows distribution from the Windows marketplace.

373
00:32:34,200 --> 00:32:39,300
This particular organization, we managed to get through all the early stages, we managed to enable it in the OS.

374
00:32:39,980 --> 00:32:46,120
But then you go to the marketplace, and you discover that there's a special lockdown one for the telco.

375
00:32:46,760 --> 00:32:50,280
And there's no Linux distribution in there, you can't do it.

376
00:32:50,760 --> 00:32:51,120
Wow.

377
00:32:52,840 --> 00:33:06,540
Yeah, you know, you're making me think that, like tying a lot of this stuff together, I mean, you know, we work at a software company that, like yourself, does a lot of consulting and working with people, but also sells a lot of products.

378
00:33:06,540 --> 00:33:16,940
So we get, we spend a lot of time paying attention to the products that we want to get people to buy from us and to use and make their life better and improve the world.

379
00:33:17,560 --> 00:33:36,920
But there's almost, if you were to think of a, how do we, if going back to my thing, like, if most all the executives or managers and all the way up to probably like shareholders of companies are like, software is really important, and that's how we're going to survive and thrive.

380
00:33:37,380 --> 00:33:46,800
And, and you kind of work down from that, probably there's a, maturity model is the wrong thing, but there's probably a path of questions to go through.

381
00:33:47,000 --> 00:33:55,840
And like the first one is like, when I fill out a ticket to like get a, get, get a machine, do I have to say the expected load on it?

382
00:33:55,940 --> 00:33:56,380
Right.

383
00:33:56,380 --> 00:34:03,600
And, and like, even, even before that, I mean, there, there, there could even be like, just looking at the full, like, you know, we're always emphasizing.

384
00:34:04,340 --> 00:34:14,220
If you want to improve your software, you have to look at like everything from like idea to a user clicking on the software in production, your, your path to production.

385
00:34:14,220 --> 00:34:27,420
And yeah, whether it's gold or platinum or whatever metallurgical color, the path is today and part, maybe there's even a, a, a, a bigger picture, which is like, you've just hired a developer, right?

386
00:34:27,420 --> 00:34:38,100
And one of the questions could be, so when you ship them a laptop, is it a developer laptop or a, we don't trust you employee laptop and like spend the first week fixing that.

387
00:34:38,100 --> 00:34:54,940
And then we'll come back and just like, kind of like a series of things where kind of like the, the, the, the, um, you know, the, the position that you were saying where like us in the tech world are used to getting a developer laptop.

388
00:34:54,940 --> 00:35:05,080
Although when I started at Dell, I did have to file a ticket to get the, you can actually do things, but that's a hardware company, uh, which kind of makes a little more sense or not.

389
00:35:05,420 --> 00:35:21,000
Uh, but like, it does seem like there's this series of things that once you have management in a company wanting to have developers, I'm trying not to call it like remedial to be kind of pejorative about it, but it's just like, yeah, this is a brand new thing that you're doing.

390
00:35:21,000 --> 00:35:26,780
Like, and here's the way it goes through the same way that I would imagine, hopefully this doesn't have to happen too much anymore.

391
00:35:26,980 --> 00:35:34,960
And, but I would imagine in like, you know, the late eighties and nineties people, car manufacturers are probably like, yeah, we'd love to have high quality and sell lots of cars.

392
00:35:35,440 --> 00:35:38,060
And I read that lean book and I don't know what's going on.

393
00:35:38,060 --> 00:35:38,440
Right.

394
00:35:38,460 --> 00:35:42,220
Like, and so it's sort of like, well, let's go through all the steps, right?

395
00:35:42,220 --> 00:35:52,840
First, you got to put socks on, then you put shoes on, like, and all, all the things until you get to the actual practices of it, uh, which probably is helpful to do for people.

396
00:35:53,080 --> 00:36:00,820
Organizations who treat their developers like a cost center instead of like a, um, valuable cog in, in the drive train.

397
00:36:01,360 --> 00:36:01,640
Yeah.

398
00:36:01,840 --> 00:36:05,560
I mean, maybe crazy idea.

399
00:36:05,640 --> 00:36:15,740
Maybe one of the things is to, is to put some people with actual development experience in, in that C-suite and I would say, look, this is why you're making these guys miserable.

400
00:36:17,300 --> 00:36:17,700
Yeah.

401
00:36:17,700 --> 00:36:21,140
They may not, they may not fully understand the, the ramifications of it.

402
00:36:21,140 --> 00:36:31,340
And because at the end of the day, like you can spend a lot of time trying to improve your corporate culture, but you know, if you do give developers, uh, limited permissions and resources and, and make them feel comfortable.

403
00:36:31,360 --> 00:36:35,840
And if you feel too restricted, then that is, that it's another way of establishing culture, right?

404
00:36:35,840 --> 00:36:37,960
You're there's a statement in that.

405
00:36:38,340 --> 00:36:38,580
Yeah.

406
00:36:38,720 --> 00:36:39,660
I don't trust you.

407
00:36:40,420 --> 00:36:40,880
I don't trust you.

408
00:36:40,880 --> 00:36:41,620
It's the statement.

409
00:36:43,000 --> 00:36:43,440
Yeah.

410
00:36:43,560 --> 00:36:45,000
You know, that's, that's an interesting thought.

411
00:36:45,000 --> 00:37:01,000
And be, it'd be interesting to hear what, what, what y'all both think about this is, is, you know, as at least, at least when I was kind of like taught as a developer, one of the principles is to have a very strong separation, like causal separation.

412
00:37:01,360 --> 00:37:05,600
Between like tools and process and culture, right?

413
00:37:05,600 --> 00:37:11,560
Like, you don't, you don't want your tools driving, forcing you to do something or limiting you.

414
00:37:12,100 --> 00:37:20,700
However, it does seem like your tools determine your process and culture and kind of vice versa.

415
00:37:20,760 --> 00:37:21,160
Right.

416
00:37:21,160 --> 00:37:33,100
Like, I don't know, like, I don't quite have the relationship figured out between like, how important tools actually are for the type of process or culture that you want to do.

417
00:37:33,400 --> 00:37:40,760
And, and in the other direction, like it's, it gets a little confusing because people are very obsessed with like phrases like, you know, technology isn't hard.

418
00:37:40,860 --> 00:37:44,000
People are hard, but it seems like they're both very hard.

419
00:37:44,000 --> 00:37:46,260
And then you combine them together and they're impossible.

420
00:37:48,940 --> 00:38:04,000
Yeah, I mean, you mentioned that also somewhere in your article, you spoke about, you know, having a good developer portal, it doesn't mean that you just add like another thing alongside, I think you mentioned like Confluence and SharePoint, like you already have all these things.

421
00:38:04,000 --> 00:38:08,000
It's not a question of like slabbing on another one, like you really have to consolidate.

422
00:38:08,440 --> 00:38:18,680
Yeah, because again, everything in that article I've seen somewhere, and you'll notice I didn't name any guilty parties, but everybody's guilty.

423
00:38:19,160 --> 00:38:28,440
Yeah, everybody's guilty, but you know, they kind of, there's this kind of realization, hey, people can't find the need and the thing is, we'll do a developer portal.

424
00:38:28,860 --> 00:38:30,280
So are you going to get rid of the other stuff?

425
00:38:31,220 --> 00:38:31,660
No.

426
00:38:33,440 --> 00:38:38,480
Well, no, it's all you've, now I've got three places to look in and I still can't find what I want.

427
00:38:38,740 --> 00:38:39,380
You know, it's.

428
00:38:39,940 --> 00:38:50,940
It always astounds me that, you know, you can go to the internet and go to, you know, any, choose your favorite search engine and type something in and the results are, it's so easy to work with the results.

429
00:38:51,060 --> 00:38:59,060
And yet you go into an internal corporate search engine or search site and it's, you know, it's like, what is, what's going on here?

430
00:38:59,080 --> 00:39:00,160
I don't understand this.

431
00:39:00,680 --> 00:39:02,960
Weirdly, I mean, someone explained this to me once.

432
00:39:03,440 --> 00:39:09,500
That actually enterprise search is much harder problem than internet search.

433
00:39:10,220 --> 00:39:15,100
Because PageRank, you know, the famous Google algorithm works at internet scale.

434
00:39:15,800 --> 00:39:24,540
It doesn't really work at corporate scale because you haven't got enough kind of people doing things and linking to other things and all the kind of signals.

435
00:39:24,760 --> 00:39:25,580
How interesting.

436
00:39:25,760 --> 00:39:29,000
That you can use to build your, your rank index that you have on the internet.

437
00:39:29,100 --> 00:39:33,220
And that's why, yeah, corporate searches is a disaster all the time.

438
00:39:33,220 --> 00:39:37,800
And it has been for as long as I, as for as long as it's existed that I've seen it.

439
00:39:37,940 --> 00:39:39,120
It's, it's never worked.

440
00:39:39,520 --> 00:39:41,340
I've never seen one that works well.

441
00:39:42,000 --> 00:39:58,260
There's probably also, there's probably also a lot of that, that lack of trust of just, you know, like governance and security and like the idea of, like, I remember, I remember in the, back when I was a programmer, like the, that Google mini search, mini search appliance came out.

442
00:39:58,380 --> 00:40:05,380
And I remember we got one and plugged it in and there were several people who were like, oh my God, I didn't realize people could find that.

443
00:40:05,740 --> 00:40:15,660
Like, you know, and so there is, there is a certain amount of governance that probably nowadays, thanks to like SharePoint and other things, people have gone through a decade or so of worrying about it and thinking about it.

444
00:40:15,700 --> 00:40:21,240
But it is, uh, that, that, that, that, that is an issue, but the point you two are raising is, is, is right.

445
00:40:21,240 --> 00:40:25,500
It's just like, I mean, it goes back to just the basics of just like, well, does search work?

446
00:40:27,360 --> 00:40:39,680
And I think to be honest, you know, maybe people aren't ready to face up to it, but there's, there's only really, if you want search to work in that kind of environment, somebody has to do some curation to make it work.

447
00:40:40,360 --> 00:40:44,400
And I mean, maybe, maybe that's something that AI might be useful for.

448
00:40:45,120 --> 00:40:45,880
Yeah, hopefully.

449
00:40:46,340 --> 00:40:46,740
Yeah.

450
00:40:46,760 --> 00:40:50,520
But you know, at the moment, search just doesn't seem to work in those environments.

451
00:40:50,640 --> 00:40:59,220
And, and the only way I can see to make it work is that somebody actually tells a search engine, hey, this one is important and this one isn't so important.

452
00:41:01,300 --> 00:41:01,660
Yeah.

453
00:41:01,720 --> 00:41:04,700
I mean, I, yeah, I see what you're saying in terms of like the ranking.

454
00:41:04,700 --> 00:41:10,500
I, I can see that and I can see how it's kind of like a catch 22, right?

455
00:41:10,520 --> 00:41:18,100
Like if you don't have, if you, if you can't, if it can't be trained based on like just people searching and linking, then it's hard to have the same end result.

456
00:41:18,300 --> 00:41:24,080
But I also feel like a lot of these search engines don't, they don't even have a lot of hits to begin with.

457
00:41:24,080 --> 00:41:27,300
Like there's other stuff there that they don't seem to find.

458
00:41:27,960 --> 00:41:32,340
Maybe it's, I don't know that it's the same technical explanation for why those things don't show up.

459
00:41:32,480 --> 00:41:33,200
I don't know.

460
00:41:33,300 --> 00:41:41,680
I mean, my, my experience generally is usually the opposite that I can see a million results and not one of them that's coming near the top is the one I want.

461
00:41:41,720 --> 00:41:43,960
The one I want might be there, but it's so far down.

462
00:41:44,040 --> 00:41:45,520
I'm never, ever going to find it.

463
00:41:45,780 --> 00:41:46,520
So it's more of a real.

464
00:41:46,560 --> 00:41:46,560
Yeah.

465
00:41:46,560 --> 00:41:47,300
Sometimes you're right.

466
00:41:47,380 --> 00:41:49,860
There's stuff that you search for and you know, it must be there.

467
00:41:50,680 --> 00:41:51,040
Nothing.

468
00:41:53,200 --> 00:41:53,720
That's fast.

469
00:41:53,760 --> 00:41:54,900
I never thought about it that way.

470
00:41:54,940 --> 00:41:56,380
That is a fascinating way to think about it.

471
00:41:56,400 --> 00:41:57,200
But yeah, it's true.

472
00:41:57,260 --> 00:42:00,800
Like AI, AI can probably help us.

473
00:42:00,800 --> 00:42:01,060
Yeah.

474
00:42:01,240 --> 00:42:05,360
I mean, certainly that's my experience with the, with, with searching on source.

475
00:42:06,760 --> 00:42:12,560
But you know, VMware is that I will get a million hits, but unless I'm very lucky, it's not the one I was looking for.

476
00:42:12,800 --> 00:42:13,200
Right.

477
00:42:13,280 --> 00:42:13,500
Right.

478
00:42:14,120 --> 00:42:14,380
Right.

479
00:42:14,880 --> 00:42:18,000
Speaking of AI, are you seeing that yet in your work?

480
00:42:18,920 --> 00:42:19,720
Not yet.

481
00:42:20,040 --> 00:42:22,080
No, I'm sure it will come.

482
00:42:22,300 --> 00:42:25,860
I'm, I'm, I'm not sure what I think about AI, to be honest.

483
00:42:25,860 --> 00:42:30,240
I'm kind of still very skeptical and sitting on the fence a bit because it feels like.

484
00:42:32,540 --> 00:42:36,340
There's been incredible progress over the last couple of years, obviously.

485
00:42:36,560 --> 00:42:43,780
And I'm astonished at how well something like chat GPT understands and parses my sentence and comes back with something.

486
00:42:44,400 --> 00:42:54,440
But it feels like they're kind of, they're hitting now the hard problems that are still really hard to solve when the machine doesn't really still understand anything.

487
00:42:55,060 --> 00:43:17,700
And you kind of wonder, well, is it, is there going to be a way to get past that and make this stuff genuine, genuinely useful and not hallucinate and not make things up and all the other problems it's prone to right now and also be, you know, eminently hackable because you can't defend against prompt injection the way you can against SQL injection.

488
00:43:19,200 --> 00:43:27,120
So are those problems going to be solvable or is it going to be another kind of blind alley like all the others with AI that we've seen?

489
00:43:27,200 --> 00:43:32,560
Because for as long as I can remember, AI and nuclear fusion have been about two decades away.

490
00:43:34,480 --> 00:43:34,880
Yeah.

491
00:43:37,360 --> 00:43:40,960
It's, there's no, yeah, there's no real system of checks and balances, right?

492
00:43:41,040 --> 00:43:47,280
I mean, even today on the internet, like the best you can do these fact checkers, I assume it's mostly manual work, right?

493
00:43:48,120 --> 00:43:55,640
Yeah, so there's, I guess we're lacking a, we have to somehow automate a system of checks and balances if that's possible.

494
00:43:56,080 --> 00:43:58,540
But it startled me how easy it was.

495
00:43:58,540 --> 00:44:11,600
Well, I mean, I've been told chat GPT-4 is better, but I had a conversation a few months ago with chat GPT-3.5 and I was talking to it about Bing because Microsoft were experimenting with putting it into Bing.

496
00:44:12,820 --> 00:44:23,300
And apparently there'd been some, the internal code name for it was Sydney, for the Bing bot or whatever they were going to call it.

497
00:44:23,720 --> 00:44:30,000
And there'd been problems with it kind of really having quite deranged conversations with people who got widely reported.

498
00:44:30,520 --> 00:44:33,180
And I thought, I talked to chat GPT about that.

499
00:44:33,540 --> 00:44:35,580
And I said, do you know about the problems with Sydney?

500
00:44:36,180 --> 00:44:45,200
And it probably, probably made up this whole story about the development scene in Sydney, Australia, getting messages from people, getting abusive messages.

501
00:44:45,200 --> 00:44:48,020
And it was kind of like, you made that up.

502
00:44:48,620 --> 00:44:50,220
You literally made that up.

503
00:44:50,220 --> 00:44:55,360
Yeah, I think we're still a ways away, I guess.

504
00:44:56,780 --> 00:45:14,020
Well, the last little cluster of things from your article, I mean, you know, in addition to the rest of the world that I was curious to ask about, especially with, as you're saying, the kind of perspective of going to different companies or organizations in,

505
00:45:15,220 --> 00:45:26,000
often in an early stage of wanting to do how they do software or improve it is like, what, what is the state of like having a, like a, like a pipeline in place?

506
00:45:26,000 --> 00:45:41,060
You know, not only, you know, it's easy to say CICD, but like when I've looked at surveys over the years, like a lot of people have continuous integration, like maybe 50% and very few have the delivery or deployment where you can do it at will.

507
00:45:41,060 --> 00:45:47,140
And so, like, I mean, what's, what's your general sense of like where everyone is with that?

508
00:45:47,140 --> 00:45:57,180
Because it seems like, this seems like another one of those fundamental things that like, if you don't even have continuous integration, start with that, right?

509
00:45:57,280 --> 00:45:59,700
Like, like get, get your build pipeline fixed up.

510
00:46:00,460 --> 00:46:07,760
So, I mean, mostly, most of the, the, the projects I've worked on, they, they, they have had, they have had CI.

511
00:46:09,380 --> 00:46:18,860
At least some, so having said that we, when we wanted to set, set one up for a modernization project, it was really hard because we couldn't find the resource.

512
00:46:19,680 --> 00:46:23,480
And literally, we couldn't find the machine to run it on, you know.

513
00:46:23,660 --> 00:46:24,020
Right.

514
00:46:24,500 --> 00:46:25,400
Kind of endless problems.

515
00:46:25,520 --> 00:46:32,260
And we were told, oh, there's this big, super centralized project that is providing pipelines for everyone.

516
00:46:32,500 --> 00:46:36,280
So, you go and look at that and it's kind of, yeah, but we're really overloaded.

517
00:46:36,320 --> 00:46:37,620
We can't help you right now.

518
00:46:38,780 --> 00:46:50,920
So, it's kind of, there's obviously a belief that this stuff is important, but again, companies, again, big enterprises, like kind of, if this stuff is important, we must have a centralized group who will manage it for everyone.

519
00:46:52,420 --> 00:46:58,560
And then you're back in tickets and silos and chucking stuff over the wall again.

520
00:46:58,560 --> 00:47:06,780
Wouldn't it be better if you had a smaller group of people who just come and help everyone set up their pipeline in the best way and let them look after it themselves?

521
00:47:07,700 --> 00:47:20,500
Yeah, it seems, I mean, there's definitely this whole idea of like running a platform as a product that, and sort of like, especially the angle of like, you should build, so this platform that would automate this pipeline for you, right?

522
00:47:20,500 --> 00:47:34,700
Like, you should build it, part of running it as a product means that you're doing it a bit more organically because you have to, you want it to be optional, right?

523
00:47:34,800 --> 00:47:36,920
Like, it's not mandated that everybody must use it.

524
00:47:36,960 --> 00:47:42,000
And so, therefore, automatically, you have to build a product that people will want to use.

525
00:47:42,080 --> 00:47:56,920
And that implies that you have a feedback loop where you can show it to people, have people who recognize that it's the better alternative of the ones available, begin to use it, give you feedback, and then you can begin to improve your own, the platform that you're managing in this way.

526
00:47:56,920 --> 00:48:04,720
So, it has to, almost by definition, if you're going to run your platform as a product, it sort of can't be the central silo, kind of waterfall approach.

527
00:48:04,860 --> 00:48:07,840
It has to be an organic one where they are talking to developers.

528
00:48:08,600 --> 00:48:13,840
Yeah, and that's interesting because, again, I'm on an engagement at the moment with another bank.

529
00:48:14,880 --> 00:48:16,120
I seem to get all the banks.

530
00:48:17,960 --> 00:48:24,680
And they've actually built, or someone in the organization has actually built what looks like a pretty nice platform internally.

531
00:48:26,860 --> 00:48:29,820
But they don't really want to talk to the developers.

532
00:48:30,500 --> 00:48:32,360
They're just saying, well, here's the platform.

533
00:48:33,500 --> 00:48:35,520
So, what should we, how should we use it?

534
00:48:35,800 --> 00:48:36,820
It's your application.

535
00:48:36,980 --> 00:48:37,440
You decide.

536
00:48:37,520 --> 00:48:38,300
These are the features.

537
00:48:39,760 --> 00:48:41,680
And, yeah, that's great.

538
00:48:41,760 --> 00:48:45,420
But you kind of think, well, actually, even Amazon don't do that.

539
00:48:45,920 --> 00:48:51,740
If you go to Amazon and say, hey, I want to run my application on your platform, they're going to help you.

540
00:48:52,940 --> 00:48:55,380
They're not going to say, here's our platform, go get on with it.

541
00:48:57,100 --> 00:49:06,140
They're going to try, you know, depending on how much money you've got to spend, they're either going to point you at some resources or, you know, if you think you're going to be a big customer, they're going to send someone on to speak to you and help you draw the diagrams.

542
00:49:06,580 --> 00:49:16,420
Right, which kind of, like, speaks to probably the way that companies define the incentives and the metrics around that platform team.

543
00:49:16,420 --> 00:49:21,500
They're somehow not structuring that incentivized.

544
00:49:22,940 --> 00:49:26,400
You know, Amazon is probably the first platform as a product.

545
00:49:26,940 --> 00:49:28,160
That's literally what it was.

546
00:49:29,400 --> 00:49:38,160
And, you know, I don't think everything they do is fabulous, but I think if you don't kind of look at some of the lessons they've learned the hard way, you're making a mistake.

547
00:49:38,980 --> 00:49:41,060
Yeah, you know, I never actually thought about it that way.

548
00:49:41,280 --> 00:49:44,360
I wouldn't have thought to put it in those words, but you're right, right?

549
00:49:44,360 --> 00:49:48,280
That is, because that's, after all, that is what public cloud was.

550
00:49:48,400 --> 00:49:50,300
It was literally platform.

551
00:49:50,300 --> 00:49:51,420
Literally the first one.

552
00:49:51,540 --> 00:49:54,960
And we're going to put this stuff up and we're going to get people to pay for it.

553
00:49:55,580 --> 00:49:55,800
Yeah.

554
00:49:55,960 --> 00:49:57,460
And hopefully they, yes.

555
00:49:57,840 --> 00:50:12,000
And although I guess the road from giving you the car pieces so that you can build your own car to actually, like, the DevX, it is a platform as a product, but it's not a DevX-focused one.

556
00:50:12,340 --> 00:50:23,440
It's not, I mean, it's, and it's kind of interesting because I started working with AWS, I guess, in about 2011, 2012.

557
00:50:23,440 --> 00:50:26,900
So, not right at the beginning, but fairly early on.

558
00:50:27,460 --> 00:50:34,980
And it was interesting watching how fast it matured and how kind of Azure, Microsoft started at the other end.

559
00:50:35,060 --> 00:50:42,160
Because they did start with kind of, we want a developer experience and you will build your applications in this way and they will run brilliant on our platform.

560
00:50:42,580 --> 00:50:47,900
And they were forced to gradually head down the stack and start offering more and more infrastructure as a service.

561
00:50:48,380 --> 00:50:50,680
And Amazon kind of went in the wrong, opposite direction.

562
00:50:50,800 --> 00:50:55,980
They started off with the infrastructure as a service, but realized actually people were going to want a platform.

563
00:50:56,600 --> 00:51:07,300
Well, the other thing about these companies offering their infrastructure as, it's a form of platform as a product, because the other challenge that they have is that they have so many different customers.

564
00:51:07,300 --> 00:51:13,080
Whereas, if you're in an organization, your use case is much more specific.

565
00:51:13,740 --> 00:51:18,160
And so, there's also this idea of platform, this whole idea of golden path, right?

566
00:51:18,220 --> 00:51:26,800
That has become sort of the new phrase with Spotify and Backstage, where you want to provide a default, a sensible default.

567
00:51:27,200 --> 00:51:30,080
Like, you know, some options, but it should be more obvious.

568
00:51:30,080 --> 00:51:36,320
Like, what is the one that this organization wants you to follow or something more opinionated and simplified?

569
00:51:36,960 --> 00:51:37,920
Yeah, make it easy.

570
00:51:38,660 --> 00:51:39,220
Make it easy.

571
00:51:39,460 --> 00:51:46,360
Again, the problem with a lot of these, you know, getting the kind of the, if you like, more mature organizations that I'm working with,

572
00:51:46,760 --> 00:51:54,000
their software stack goes back probably quite often to the 1980s and everything since then.

573
00:51:54,420 --> 00:52:00,420
You know, again, if you look at, if you look at a bank, a typical retail bank, certainly in the UK,

574
00:52:01,060 --> 00:52:04,420
they built their, what is now their core banking system.

575
00:52:04,580 --> 00:52:09,320
The core of that, they probably built back in the 1980s on an IBM mainframe using COBOL.

576
00:52:09,900 --> 00:52:11,140
And that's still running.

577
00:52:11,740 --> 00:52:12,980
That's still at the heart of the business.

578
00:52:13,060 --> 00:52:16,380
And everything else kind of has to be fitted around that.

579
00:52:16,380 --> 00:52:24,140
It does, it does mean they have peculiar challenges of their own that, you know, companies like Spotify just don't have.

580
00:52:24,360 --> 00:52:26,560
Also, Spotify goes down for a couple of days.

581
00:52:26,660 --> 00:52:27,680
People are going to be upset.

582
00:52:28,400 --> 00:52:38,640
But when a bank goes down for a couple of days, and we've, we've had that in this country, we've had, I know NatWest had a big outage about 10, 15 years ago.

583
00:52:40,100 --> 00:52:47,940
And there was another of the retail banks, I think it was HSBC or Lloyd's also had big outages that went on for two or three days.

584
00:52:47,940 --> 00:52:52,900
Because people are not just inconvenienced, they're furious, and they can't get their money.

585
00:52:53,960 --> 00:52:54,860
Right, right.

586
00:52:54,980 --> 00:52:55,820
And it has, yeah.

587
00:52:56,260 --> 00:53:02,780
So banks, from that point of view, I understand why they tend to be a little more conservative in their approach.

588
00:53:03,320 --> 00:53:03,640
Correct.

589
00:53:03,840 --> 00:53:04,960
Yeah, but they're, yeah, yeah.

590
00:53:05,020 --> 00:53:13,240
I think the ask is, from a dev experience perspective, it's to differentiate sort of an experimentation area from production.

591
00:53:13,240 --> 00:53:13,780
Yes, absolutely.

592
00:53:14,100 --> 00:53:18,000
Give us a play pit, but we treat production seriously.

593
00:53:19,360 --> 00:53:19,840
Exactly.

594
00:53:21,020 --> 00:53:21,380
Well, great.

595
00:53:21,560 --> 00:53:29,200
Well, that, that was, that was, well, I, I, I, I came up with a bunch of questions, which is always good.

596
00:53:29,620 --> 00:53:30,380
Mysteries to solve.

597
00:53:30,380 --> 00:53:41,620
Like, like, for example, like, we kind of hit on the other mystery, which I often forget is a mystery out there, which is, you know, you're talking about, like, Azure starting out as a platform as a service.

598
00:53:41,620 --> 00:53:43,320
And then Google was the same thing, right?

599
00:53:43,400 --> 00:53:48,540
Like, I mean, famously, I think the people who built Kubernetes had built App Engine or something like that.

600
00:53:48,900 --> 00:53:56,640
And, and then, of course, we have the old Heroku and then, you know, recently, like all the passes and the, the pre, kind of pre Docker, pre Kubernetes era.

601
00:53:56,640 --> 00:54:04,580
And there is like, there's this constant thing of like, I don't know if developers actually want a platform because we keep giving it to them.

602
00:54:04,640 --> 00:54:10,620
And just like, just like kids who, you know, say they want some food for dinner and then they don't, they keep sending it back.

603
00:54:10,840 --> 00:54:12,400
And I don't, I don't know what to give them.

604
00:54:12,980 --> 00:54:18,280
I mean, I, I, so I, my first experience with, with Cloud Foundry was when I joined Pivotal.

605
00:54:18,840 --> 00:54:22,180
And I kind of, after a kind of initial, well, why would you want this?

606
00:54:22,260 --> 00:54:29,360
Once you actually touch it and use it, you think, actually, I don't ever want to do anything else other than this ever again, frankly.

607
00:54:31,020 --> 00:54:34,460
It's the, it's the thing of like, once you can get the kid to try the food.

608
00:54:34,620 --> 00:54:35,480
Yeah, exactly.

609
00:54:35,480 --> 00:54:36,380
Maybe they'll eat it.

610
00:54:36,960 --> 00:54:45,620
This is back to my, my, my, my, my theory that, that, you know, the, this, this IT industry, the tech industry is like the fashion industry.

611
00:54:46,260 --> 00:54:49,720
Kubernetes is terribly fashionable and sexy and everybody wants it.

612
00:54:50,060 --> 00:54:54,760
Even though actually, I mean, frankly, it's a pain to use.

613
00:54:54,760 --> 00:54:55,360
I think.

614
00:54:55,920 --> 00:54:59,580
I've been forced to move from Cloud Foundry to Kubernetes.

615
00:54:59,800 --> 00:55:01,320
I have not found that enjoyable.

616
00:55:01,860 --> 00:55:02,300
Yeah.

617
00:55:02,560 --> 00:55:02,700
Yeah.

618
00:55:02,700 --> 00:55:03,440
It's very interesting.

619
00:55:03,620 --> 00:55:11,120
It's lots of fun and I can build interesting things, but it's like, if I could not do it, I'd be happy not to do it.

620
00:55:11,120 --> 00:55:19,800
And, and, you know, going all the way back to the beginning, right before the end here, you know, that's, that's part of what drives the, why did we need more than COBOL question.

621
00:55:19,860 --> 00:55:22,120
It's sort of like, it seemed fine.

622
00:55:22,120 --> 00:55:37,820
And now here we are, but I mean, and obviously, you know, the, the, the, it's not only a rhetorical question, this, whatever this, how can we can never, not never, that shouldn't be hyperbolic, but how come it's so difficult to get a platform into the industry?

623
00:55:37,820 --> 00:55:48,140
But it also, the, the positive side of that is, as you were alluding to, is there are these like incremental improvements in how things are done when you move technologies over.

624
00:55:48,560 --> 00:55:50,920
And, uh, it's always, I, I don't know.

625
00:55:50,940 --> 00:55:59,800
I don't, I don't think in, in software development, we have a good understanding of, I don't even have phrases for it, but like, it's not like creative destruction.

626
00:55:59,800 --> 00:56:11,220
It's creative, some other word of like, how do you, how do you evolve something and moving it, move it forward without it being like, let's just knock it all down and build up from the beginning.

627
00:56:11,220 --> 00:56:16,160
Or, or maybe it does happen, but it is a, uh, a strange evolution of, of things.

628
00:56:17,160 --> 00:56:23,200
But anyhow, speaking of strange evolutions, this conversation has evolved in exciting, fun ways.

629
00:56:24,000 --> 00:56:30,560
And, uh, if, if someone wanted to, uh, you know, we'll put a link to the, uh, the article we've been talking about and, uh, links to other things.

630
00:56:30,560 --> 00:56:43,000
But, uh, is there a place that you would point people to if they're interested in hearing about more, whether it was about your illustrious career in Cobalt land, what you do in, in consulting, uh, you know, nowadays.

631
00:56:43,300 --> 00:56:47,720
You can find me on LinkedIn, but that's a bit bare, to be honest.

632
00:56:47,940 --> 00:56:55,660
Um, although that does, that my LinkedIn profile does at least now have links to, to most of the things I've written over the last few years.

633
00:56:55,800 --> 00:57:00,840
Well, that's good. And, and we'll put in, uh, we'll put in the links of things we know about because it's, uh, it's good stuff.

634
00:57:00,900 --> 00:57:08,040
Like it's, it's a good span of things to, to, to, to, to, if you want to Google me, you will not find me as Paul Kelly.

635
00:57:08,880 --> 00:57:14,900
Paul Kelly is an ungoogleable name because there are so many Paul Kellys and they're nearly all more famous than I am.

636
00:57:14,900 --> 00:57:19,720
Which is the most important, Paul? We have to, we have to tell, we have to let Google know that you are the most important.

637
00:57:20,380 --> 00:57:26,820
Well, if you, if you add the word Cobalt to the search term, Paul Kelly, there's a good chance you'll hit something to do with me.

638
00:57:27,180 --> 00:57:27,580
Exactly.

639
00:57:27,980 --> 00:57:29,300
On the first page or so.

640
00:57:29,420 --> 00:57:31,060
Or I guess VMware at this point.

641
00:57:31,360 --> 00:57:33,020
And possibly VMware as well, yeah.

642
00:57:33,620 --> 00:57:33,940
Yeah.

643
00:57:33,940 --> 00:57:50,440
If you do, uh, yeah, we will link it, but if you do Google Paul Kelly VMware, you should, uh, get the hit to his article published in April, actually a developer perspective on developer experience, which touches on all these ideas of what exactly is developer experience.

644
00:57:50,440 --> 00:57:51,600
What does it mean to the business?

645
00:57:51,600 --> 00:57:53,240
What is the tension with security?

646
00:57:53,240 --> 00:57:55,880
What is, uh, running your platform as a product?

647
00:57:55,880 --> 00:58:00,280
A lot of really great material covered in this, uh, in this read.

648
00:58:00,280 --> 00:58:03,820
So I would definitely recommend that folks go through that.

649
00:58:04,960 --> 00:58:05,560
Well, great.

650
00:58:05,620 --> 00:58:06,200
Well, thanks again.

651
00:58:06,200 --> 00:58:19,880
And, and, uh, for, for people listening, if you want to find all of that, you just go to, uh, tonsutalk.com and, uh, you can find the show notes for this episode, or if you want to watch it in YouTube or whatever, you can look it up there, but it's all over the place.

652
00:58:19,960 --> 00:58:22,100
So, uh, with that, we'll see everyone next time.

653
00:58:22,400 --> 00:58:22,460
Bye.

654
00:58:22,460 --> 00:58:22,720
Yeah.

655
00:58:22,720 --> 00:58:23,840
Oh, thank you so much.

656
00:58:24,200 --> 00:58:24,720
Thanks for sending.

657
00:58:24,980 --> 00:58:26,020
Thank you for having me.

658
00:58:26,020 --> 00:58:27,540
It's been, uh, it's been a pleasure.

659
00:58:28,040 --> 00:58:28,320
Our pleasure.

660
00:58:28,320 --> 00:58:28,840
Yeah, it was great.