1
00:00:00,000 --> 00:00:04,160
Well, hey everyone, this is Coté. For this episode of Tanzu Talk, I've got an interview

2
00:00:04,160 --> 00:00:09,120
that Alex Williams of the Newstack and I did back at VMware Explore. It wasn't that long ago

3
00:00:09,120 --> 00:00:14,180
as I sit here recording this. Anyways, it's with Solomon Hikes about Dagger.io,

4
00:00:14,600 --> 00:00:20,400
the new company that he and some of his, I don't know, past co-workers are working on,

5
00:00:20,700 --> 00:00:25,300
basically to work on pipelines or builds or continuous integration, continuous deployment,

6
00:00:25,300 --> 00:00:32,600
or secure software supply chains, as he mentions later. Anyways, he had just given a demo of

7
00:00:32,600 --> 00:00:39,060
a new way to use Dagger, basically opening it up to other programming languages. And then he came

8
00:00:39,060 --> 00:00:44,720
over to talk with Alex and I, and we talked more broadly about the idea of what Dagger is doing,

9
00:00:44,760 --> 00:00:51,420
a programmable pipeline, platform engineering. And as I was eager to get to kind of an idea of how

10
00:00:51,420 --> 00:00:58,980
Dagger wants you to think in the directed acyclical graph, as I recall. I'm no mathematics

11
00:00:58,980 --> 00:01:04,260
or geometry person, so I don't know if I use those words correctly. But, you know, there's a lot going

12
00:01:04,260 --> 00:01:09,760
on in the pipeline, the supply chain, the build space. We have a lot going on in VMware Tanzu land

13
00:01:09,760 --> 00:01:15,360
with various open source things like Cartographer and other stuff. And Dagger is figuring things out

14
00:01:15,360 --> 00:01:19,040
and many other companies. I think it's an area that's going to be pretty exciting for the next

15
00:01:19,040 --> 00:01:24,600
couple of years as people try to get to that programmable pipeline that we end up talking

16
00:01:24,600 --> 00:01:29,220
with, with Solomon. Well, before we get to that, if you're interested in these kinds of things,

17
00:01:29,220 --> 00:01:34,220
whether it's application development, DevOps, you fancy yourself a platform engineer, or you don't

18
00:01:34,220 --> 00:01:39,120
really fancy it, you are one, anything that you're doing there, including up to the executive and

19
00:01:39,120 --> 00:01:42,680
enterprise architect layer. If you're in a setup where you're just trying to get better at software,

20
00:01:42,680 --> 00:01:46,940
you should check out the conference we have coming up SpringOne, December 6th and 8th.

21
00:01:46,940 --> 00:01:52,500
This is our annual conference from the pivotal days. Now the VMware Tanzu days, all about programming

22
00:01:52,500 --> 00:01:59,840
from Java to.net, other languages, operating cloud native environments from passes to Kubernetes,

23
00:01:59,840 --> 00:02:05,360
things like the Tanzu application platform and the Tanzu Kubernetes for operators. And of course,

24
00:02:05,360 --> 00:02:10,340
the Tanzu application service case studies and tips and things like that to agile software development.

25
00:02:10,500 --> 00:02:14,820
Anyways, you should check it out. Go to SpringOne.io. I think in a week or two,

26
00:02:14,820 --> 00:02:19,200
we're going to have the full talk schedule posted. And when you register, which I'm sure you will,

27
00:02:19,380 --> 00:02:26,360
because it'll be great. You can use the code Coté 200, that's C O T E 200 to get $200 off.

28
00:02:26,620 --> 00:02:31,500
So go to SpringOne.io, check out what we have to offer there. Maybe look at some past talks,

29
00:02:31,500 --> 00:02:35,660
but I think it'll be well worth your time to go there to San Francisco, December 6th and 8th.

30
00:02:35,660 --> 00:02:43,340
And of course, use the code Coté 200 to get $200 off. Now with that, we jump in to the interview when

31
00:02:43,340 --> 00:02:48,680
you know what, I kind of forget what I was asking Solomon. So I'm just going to leave that in. And

32
00:02:48,680 --> 00:02:52,120
you can hear the question that I go through. You know, what's fun about this interview

33
00:02:52,120 --> 00:02:57,220
is you can hear some kind of long pauses and how Alex and I come up with questions to ask,

34
00:02:57,260 --> 00:03:02,280
especially me, where I just kind of like, I have this technique when I listen to myself where I just

35
00:03:02,280 --> 00:03:06,500
kind of like make mouth noises and babble about stuff as I'm thinking of the question to ask,

36
00:03:06,900 --> 00:03:10,800
which I don't know, it's kind of annoying to listen to, I guess, but that's how it works.

37
00:03:10,960 --> 00:03:11,780
Enjoy the interview.

38
00:03:12,460 --> 00:03:16,780
Well, you know, when, when, when we've been talking about this, uh, we were talking last week about it

39
00:03:16,780 --> 00:03:21,800
and to, to, to modify like a discussion that we had a little bit, it was, it was, well,

40
00:03:21,880 --> 00:03:26,620
to some, to add some context, like, uh, I don't know, maybe, I don't know if it's fair to say,

41
00:03:26,620 --> 00:03:31,640
but like y'all are trying to make the pipeline more programmable, kind of apply, like,

42
00:03:32,180 --> 00:03:35,000
application development ideas to, to a pipeline.

43
00:03:35,040 --> 00:03:39,620
And I wonder being here at VMware Explorer, I should make sure to say it the right way.

44
00:03:39,740 --> 00:03:48,180
Like, how would you explain what y'all are up to, to like an operations person who's like

45
00:03:48,180 --> 00:03:52,420
more, maybe not so steeped in the idea of like, how would we make something programmable?

46
00:03:52,420 --> 00:03:55,060
But how do you, how do you kind of think it layers onto their mindset?

47
00:03:56,100 --> 00:03:58,760
Yeah, I think, is this, is this a good, is this, okay.

48
00:03:59,240 --> 00:04:01,140
Yeah, I, we're, that's definitely what we're doing.

49
00:04:01,380 --> 00:04:07,600
Um, I mean, I, I think, I mean, there's a, there's a big change going on and, and, you know,

50
00:04:07,600 --> 00:04:13,360
that the, the, the, the work of shipping software is getting so complicated that it needs to be

51
00:04:13,360 --> 00:04:13,800
automated.

52
00:04:13,800 --> 00:04:19,840
The, the bar is rising, you know, it needs to be automated in a more and more sophisticated way.

53
00:04:20,120 --> 00:04:20,480
Yeah.

54
00:04:20,560 --> 00:04:23,460
To the point where a script here and there is no longer enough.

55
00:04:24,060 --> 00:04:33,040
You need to think of your supply chain, the, the supply chain of your software project as a software project of its own.

56
00:04:33,040 --> 00:04:38,260
So, you know, it's the code that ships your code, it's the robot that builds the robot, that kind of stuff.

57
00:04:38,380 --> 00:04:43,500
So, I mean, if you're involved in the operations of that supply chain in any way, whether it's, you know,

58
00:04:43,760 --> 00:04:49,180
all the way from, I guess, the, the racking the servers part, I think everyone kind of is on board with,

59
00:04:49,300 --> 00:04:50,160
okay, that's automated.

60
00:04:50,380 --> 00:04:58,140
But, you know, the next layer on top of that, um, it's got to be fully automated from the, the code is ready to go.

61
00:04:58,560 --> 00:05:04,180
Next version of the code is ready to, okay, it's online, everything else, it needs to be automated as much as possible.

62
00:05:04,180 --> 00:05:10,860
So, a lot of, you know, there's a whole community, I, you know, let's call it the DevOps community,

63
00:05:11,660 --> 00:05:19,980
the people helping developers ship more productively, that community is transforming into a developer community of its own.

64
00:05:20,780 --> 00:05:26,380
Yeah, yeah, it's kind of, kind of like the, uh, I was just discussing this, but there's a, kind of a lack of a phrase for that at the moment.

65
00:05:26,600 --> 00:05:33,060
Like, I mean, the, the most recent thing that's kind of, you know, you hear with platform engineer a lot and people kind of using that term for it.

66
00:05:33,360 --> 00:05:34,280
Yeah, that's definitely part of it.

67
00:05:34,440 --> 00:05:34,900
Yeah, yeah.

68
00:05:35,080 --> 00:05:42,920
And so, so exactly who would own is always a weird word, but be in charge of that, that tool change is, uh, emerging as they say.

69
00:05:42,920 --> 00:05:43,120
Yeah.

70
00:05:43,340 --> 00:05:47,740
I mean, in our experience, I mean, we like, we are drawn to pain.

71
00:05:48,280 --> 00:05:55,060
That's a weird thing to say, but, like, you're basically, our, as a team, we just like to find painful problems and solve them.

72
00:05:55,280 --> 00:05:55,460
Right.

73
00:05:55,540 --> 00:05:56,800
Within our area of, uh.

74
00:05:56,800 --> 00:05:57,840
Have a useful solution.

75
00:05:58,060 --> 00:05:58,260
Right.

76
00:05:58,520 --> 00:06:01,400
And so, that involves talking to people a lot and listening to their problems.

77
00:06:01,480 --> 00:06:04,460
Otherwise, you, you, you're, you're just randomly building stuff.

78
00:06:04,600 --> 00:06:04,940
Right, right.

79
00:06:04,940 --> 00:06:11,940
And so, one thing we ask is about that, where, okay, who's trying to do this and where are they in the org?

80
00:06:12,020 --> 00:06:12,760
Like, how is it organized?

81
00:06:13,060 --> 00:06:14,260
And it's all over the place.

82
00:06:14,400 --> 00:06:15,380
Titles change.

83
00:06:16,000 --> 00:06:16,820
Titles are different.

84
00:06:17,340 --> 00:06:18,220
Org charts are different.

85
00:06:18,720 --> 00:06:31,960
Um, but there's always, I mean, it starts, there's a moment in the life cycle of a project, you know, that, where one person has to be dedicated full time to just helping everyone else ship.

86
00:06:32,860 --> 00:06:32,960
Right.

87
00:06:33,000 --> 00:06:41,660
And, you know, the title could be anything, really anything, you know, DevOps engineer, CICD, uh, sometimes it's just, you're the lead and that's what you do, but you do it full time.

88
00:06:41,660 --> 00:06:50,820
Um, so the label on the hat is, you know, varies, but the hat is, is, is always there as soon as you reach a point where your project is growing.

89
00:06:51,120 --> 00:06:51,200
Right.

90
00:06:51,280 --> 00:06:53,640
It's, it's like there's often the accidental build person.

91
00:06:54,120 --> 00:06:56,680
Like, they, they just happen to be the one that they started doing the build.

92
00:06:56,780 --> 00:06:58,780
You say yes one time and then you get pulled into it.

93
00:06:58,900 --> 00:06:59,120
Right.

94
00:06:59,460 --> 00:07:10,840
Uh, but eventually, you know, at the end of the road, I mean, you, you, you, you reach a point where you have this dilemma that we were talking about where we got scripts and that's what we need now, but we need a platform, you know, sometime next year.

95
00:07:11,100 --> 00:07:24,720
And there's a, there's a huge gap and we, you know, it's really hard to bridge that gap and it usually fails, you know, sometimes the failure gets hidden, you know, but, but it's usually, it's, it's really painful.

96
00:07:25,040 --> 00:07:25,440
So, yeah.

97
00:07:25,440 --> 00:07:30,100
You know, I was thinking about kind of the terms you use, like incremental revolution.

98
00:07:30,780 --> 00:07:49,720
And I also think about what I'm reminded of back from your earliest days at Docker, where, what I really loved about Docker in its beginnings was how it served as a way to almost embody your philosophy about programming the internet.

99
00:07:49,720 --> 00:07:57,000
Like there's this capability that we all have and there was a certain amount of, I think, minimalism in it too.

100
00:07:57,100 --> 00:08:02,080
And I think, I think of Kelsey out here who's here to talk, who's a real minimalist himself.

101
00:08:02,080 --> 00:08:07,980
And I'm curious how you're trying to embody that in what we're seeing today and what you're building.

102
00:08:08,380 --> 00:08:16,040
Yeah, it's, it's, it's a design, I think it's a design, it's, it's a design problem.

103
00:08:16,720 --> 00:08:22,460
You know, I mean, we like, we like to make things really simple to use and get to the essence of it, but it's really hard.

104
00:08:23,740 --> 00:08:32,220
Personally, I'm attracted to it because it seems so effortless once it, once it's done, but the process of getting there is just so painful.

105
00:08:33,020 --> 00:08:47,680
And each increment, yeah, each increment of simplicity, of extra simplicity, you know, it just gets, it's, you know, it's like the, the, the, in physics, you know, the closer you get to the, the speed of light, the more energy you have to spend to get just a little bit closer.

106
00:08:47,800 --> 00:08:58,640
It's the same thing, you know, like the closer you get to the, just the perfectly simple design where there's everything you need and nothing else, the, the, the harder it gets to advance.

107
00:08:58,900 --> 00:09:06,380
So that's, that's, we went through that process with Docker with some success, but with also, you know, some, some, we stumbled along the way.

108
00:09:06,500 --> 00:09:10,040
And so we're, we're trying to, we're like, we're starting over basically.

109
00:09:10,040 --> 00:09:10,720
So that's fun.

110
00:09:10,900 --> 00:09:11,320
Interesting.

111
00:09:12,160 --> 00:09:15,220
And so you're starting over in some respects.

112
00:09:16,000 --> 00:09:22,680
So what did you learn then that you're thinking about developing in this incremental manner?

113
00:09:22,880 --> 00:09:28,380
So I could see how their incremental revolution kind of concept comes by like trying to do things more and more simple, right?

114
00:09:28,440 --> 00:09:31,280
Trying to like, and there's a pain in that, right?

115
00:09:31,560 --> 00:09:40,120
Revolutions can be very painful no matter if it's, you know, happens, you know, at its peaks and valleys, wherever that revolution is.

116
00:09:40,120 --> 00:09:48,360
So, yeah, um, well, I think the one, one thing is that what did we learn, right?

117
00:09:48,580 --> 00:09:49,540
Uh, in that process?

118
00:09:49,540 --> 00:09:49,720
Yeah.

119
00:09:50,000 --> 00:09:59,740
Well, one thing that we, we kind of had our sights on with in the early days with Docker, but, um, I think didn't realize all the way.

120
00:09:59,740 --> 00:10:07,200
Uh, well, we ended up following another path, which is fine, but I think there's something really magical about platforms.

121
00:10:08,800 --> 00:10:21,520
Um, if you can build them right, and I think the, the, the term is really overused, obviously, when I think of a platform, I think of something that you write code for, like an operating system is a platform, you know what I mean?

122
00:10:21,700 --> 00:10:40,240
Yeah, and, and, and, and so I think to solve this particular problem, you need to sort of somehow come up with a new platform so that this community of people we were talking about that are, that are trying to automate the supply chain, you know, DevOps, that community, they actually have a platform that they can write software for.

123
00:10:40,480 --> 00:10:52,780
And it's actually a, a proper platform, you know, you can re, which means mostly you can reuse each other's work and trust that it's going to, trust that you can reuse each other's work safely.

124
00:10:53,560 --> 00:10:55,940
Um, and, and we don't really have that.

125
00:10:55,940 --> 00:11:04,440
I mean, we tried with Docker, you know, with Docker images, and then later with Docker compose files, and it's kind of in the uncanny valley where it's almost soft, it's almost code.

126
00:11:04,700 --> 00:11:08,520
And so the thing running it is almost a platform, but just not, it's not quite.

127
00:11:10,480 --> 00:11:25,480
Yeah, I, it, it, it, it piques my curiosity because here at the show, we're hearing a lot about platforms and platform engineering and my colleague here, Michael Coté, knows a lot about this topic on platform engineering.

128
00:11:25,480 --> 00:11:34,320
I know he spent some time on this, but a lot of it comes down to all those tools, right?

129
00:11:34,400 --> 00:11:38,760
And then that, and then that whole tool chain, but a lot of it is process, isn't it?

130
00:11:39,080 --> 00:11:40,220
And a lot of it is workflow.

131
00:11:41,420 --> 00:11:50,680
And, and so how do you, how do you like settle, you know, how do you settle process and workflow, you know, with, you know, with platforms?

132
00:11:51,060 --> 00:11:54,380
Because if you don't have that process and workflow, it's just a bag of tools.

133
00:11:55,380 --> 00:11:55,620
Yeah.

134
00:11:55,620 --> 00:12:08,220
I mean, the, I think all those things like workflows, run books, whatever it is that you have to do to, to ship, as long as it's not software that you can hand to someone and say, run this, then you're not done basically.

135
00:12:08,640 --> 00:12:13,020
And I think that's what's, what's happening right now, you know, like the, the whole software is eating the world.

136
00:12:13,020 --> 00:12:15,060
Like right now software is eating the supply chain.

137
00:12:15,780 --> 00:12:21,540
So those workflows, those policies, you know, they're going to be code and that code is going to have to run somewhere.

138
00:12:21,840 --> 00:12:29,280
And right now writing that code and getting it to run somewhere and everywhere it needs to run and collaborating on it is, it's just a mess.

139
00:12:29,340 --> 00:12:36,600
You know, it's like the early days of, you know, I don't know, the, the web platform or early days of personal computing.

140
00:12:36,600 --> 00:12:47,260
You know, if you're, if you're writing that software now, you're like a pioneer, you got to glue stuff together and you got to know 50 technologies inside out and you got to be an absolute expert.

141
00:12:47,520 --> 00:12:52,780
But, you know, hopefully five years, 10 years from now, let's say things move slower than I used to think they do.

142
00:12:53,860 --> 00:12:55,000
Hopefully that won't be the case.

143
00:12:55,000 --> 00:13:09,540
You won't need to be an expert in all these crazy tools and technologies to write, you know, to say, here's our, here's our supply chain, you know, here's our workflow for this part of our compliance problem or whatever it is, you know.

144
00:13:11,300 --> 00:13:17,560
So to pull together a few things there, I mean, we were talking about making your pipelines programmable.

145
00:13:18,040 --> 00:13:18,280
Yes.

146
00:13:18,280 --> 00:13:29,260
And, and kind of like one of the things you were saying is a platform is a place you put code and, and like what, what y'all are kind of putting together here is putting code into a pipeline.

147
00:13:29,520 --> 00:13:33,780
So that sort of makes a pipeline, a platform to, to some extent.

148
00:13:33,780 --> 00:13:38,660
And so to that end, like, I mean, anytime a platform emerges, there's kind of, I always think of, there's two things.

149
00:13:38,660 --> 00:13:47,840
There's one, like to anthropomorphize it, like the platform wants you to think some way or it's easier to use if you think some way, like, like the model on top of it.

150
00:13:47,840 --> 00:13:54,320
And then also, even though it's extremely early, like you kind of find some best practices and worst practices along the way.

151
00:13:54,400 --> 00:13:54,920
So I don't know.

152
00:13:55,220 --> 00:14:03,060
I mean, I'm curious, like what, how, how does this platform want you to think about a build and like, like what's the model in the head and the behavior?

153
00:14:03,060 --> 00:14:11,880
Yeah, yeah, that's, that's a really good point because I think, I mean, there's a cost to a new platform, you know, you, oh, okay, I got to learn this new API and I got to write code for it, you know.

154
00:14:11,880 --> 00:14:23,920
So I think there's a sweet spot where to be useful, like to add value, it's, you know, that it's got to bring some sort of new opinion on how you're supposed to do things.

155
00:14:23,920 --> 00:14:29,100
You know, oh, you got to structure, just structure it this way and you'll see, it'll be great and we'll help you.

156
00:14:29,560 --> 00:14:33,380
But at the same time, it's got to, it's got to be, there's got to be a path to doing that.

157
00:14:34,440 --> 00:14:48,480
And so, like if you're too prescriptive and then it restricts the flexibility that you need in a given area, then you're just going to be, you're going to be less adopted because it's harder to use it.

158
00:14:48,480 --> 00:14:57,400
So the sweet spot here is that if your software supply chain is itself becoming software and we're talking about, okay, what's the platform to run that?

159
00:14:57,940 --> 00:15:04,880
Well, everyone's software supply chain is different, but everyone's software supply chain kind of looks the same.

160
00:15:05,740 --> 00:15:09,700
It's a graph, you know, you got nodes and you got lines between them.

161
00:15:10,020 --> 00:15:15,820
Specifically, it's a DAG, you know, it's a graph where everything goes in a specific direction and there's no cycles.

162
00:15:15,820 --> 00:15:18,260
That's what a DAG is. That's what we're called DAG, by the way.

163
00:15:18,500 --> 00:15:20,740
So how are you managing that underlying graph?

164
00:15:21,280 --> 00:15:23,780
Well, so that's where we bake in an opinion.

165
00:15:24,020 --> 00:15:36,280
If you use the, you know, the Cloak API or the DAG API to encode your supply chain and software, you know, your pipelines are going to be nodes in a graph.

166
00:15:36,380 --> 00:15:37,500
They're all interconnected in a graph.

167
00:15:37,720 --> 00:15:38,760
We have that opinion.

168
00:15:38,760 --> 00:15:46,160
And we say, if you're encoding your supply chain software, organize it like a graph, and here is a platform for doing that.

169
00:15:46,620 --> 00:15:50,320
And so that's where, that's the trick for adding value.

170
00:15:50,480 --> 00:15:55,480
We can have an opinion about how your supply chain is going to be shaped because we know it's going to be a graph.

171
00:15:55,940 --> 00:15:59,700
Therefore, we can narrow down the focus of our platform on just that problem.

172
00:15:59,880 --> 00:16:05,280
So it doesn't, then what you're going to do is just swap out the nodes in your graph.

173
00:16:05,420 --> 00:16:06,800
You know, oh, I build with this tool.

174
00:16:07,080 --> 00:16:08,880
Well, my keys are in hash core vault.

175
00:16:09,140 --> 00:16:11,360
Well, I host on Kubernetes on this thing, whatever.

176
00:16:11,780 --> 00:16:12,920
You know, you just swap it out.

177
00:16:13,540 --> 00:16:16,760
You know, you're just reorganizing your graph, but it's still a graph.

178
00:16:17,200 --> 00:16:27,200
And if under the hood, the API lets you just reuse someone else's components into your graph and then, or take a whole area of your graph and wrap it in a box and say, take all of that.

179
00:16:27,360 --> 00:16:29,460
You know, that's one node in your mega graph.

180
00:16:29,940 --> 00:16:36,220
Then you have potentially an amazing level of collaboration and innovation, which is what's missing.

181
00:16:36,220 --> 00:16:44,580
So we just, what's missing is like a platform that's actually capable of doing that in code and it actually works.

182
00:16:45,260 --> 00:16:48,200
You know, it's, so it's a design, again, it's an engineering design problem.

183
00:16:48,600 --> 00:16:54,240
The way Lego is an engineering and design problem, you know, it boils down to the individual brick.

184
00:16:54,780 --> 00:17:00,780
You know, you got to engineer in a way that it's simple enough to snap together, but it actually like holds.

185
00:17:00,780 --> 00:17:06,660
You know, you can stack it up and you can break records in height with your super tower or something and it still somehow works.

186
00:17:07,040 --> 00:17:08,460
That's an amazing feat of engineering.

187
00:17:09,040 --> 00:17:10,660
That's, that's the hard part of what we're doing.

188
00:17:10,940 --> 00:17:16,560
You know, saying, okay, you know, we're obsessing over tiny little details so that you can just stack up, up and up and up and up and up.

189
00:17:17,120 --> 00:17:22,800
And one day run, you know, a giant supply chain on over it and it, and it just, it works and you can trust it.

190
00:17:23,100 --> 00:17:23,260
Right.

191
00:17:23,260 --> 00:17:30,620
So it seems like, I mean, there's at very, at least, I'm sure there's more like two ways of thinking that are going on here.

192
00:17:30,620 --> 00:17:43,880
One is that you should think of, I mean, whether you want to call it a build or a pipeline or a supply chain, it's always fun to come up with a phrase that the most fundamental thing you need to do is think of it as, as a graph full of nodes.

193
00:17:44,080 --> 00:17:49,820
And if, if your pipeline doesn't think that way, that's what it should do, right?

194
00:17:49,840 --> 00:17:50,000
Right.

195
00:17:50,000 --> 00:17:59,600
And then the second thing is basically like, and then you need to think about it as not so much configurable or scriptable, but programmable.

196
00:17:59,740 --> 00:17:59,880
Right.

197
00:18:00,000 --> 00:18:02,580
And, and you'll be coming in from, with a programmer's mindset.

198
00:18:02,700 --> 00:18:12,760
And then that brings you being able to reuse and share and swap things in and out, which is, again, much different than I think the majority of pipelines are thought of and going through.

199
00:18:12,920 --> 00:18:15,300
Yeah. What's interesting is just finding a way to ease into it.

200
00:18:15,340 --> 00:18:19,260
We talk a lot about scripts because that's where, that's what exists today.

201
00:18:19,260 --> 00:18:33,540
So being able to embed something more powerful inside an existing script and kind of give you a way to gradually adopt this programming model on your own terms, you, you need that.

202
00:18:33,600 --> 00:18:36,060
Otherwise, you know, it's really hard to adopt.

203
00:18:36,060 --> 00:18:36,340
Transition is difficult.

204
00:18:36,340 --> 00:18:36,520
Yeah.

205
00:18:36,620 --> 00:18:36,840
Yeah.

206
00:18:37,040 --> 00:18:46,600
That's why, I mean, that's why Docker files work so well, because they met you where, they didn't force you to, to become a better human being, to, to be worthy of using the tool.

207
00:18:46,760 --> 00:18:49,280
Just the tool, just, you know, it's, it, you do it this way.

208
00:18:49,320 --> 00:18:49,720
Okay, cool.

209
00:18:49,880 --> 00:18:50,720
Write this Docker file.

210
00:18:50,780 --> 00:18:51,080
It works.

211
00:18:51,220 --> 00:19:01,160
I just got the sign that we got to wrap up, but maybe in conclusion, you can talk to us about how you're looking to build out the community platform.

212
00:19:01,320 --> 00:19:04,540
I know you built it initially on Q, the programming language.

213
00:19:05,040 --> 00:19:06,720
What else are you doing now to help build it up?

214
00:19:06,720 --> 00:19:09,860
So basically this prototype we showed, you know, we, we haven't launched it yet.

215
00:19:09,860 --> 00:19:16,760
It's not ready, but you know, it's, we're, we're adding the support for doing this in any language.

216
00:19:16,860 --> 00:19:22,220
And Q is one of those languages, but it's going to be one of many, and we're going to open all of it.

217
00:19:22,760 --> 00:19:28,820
And hopefully you'll see people reusing each other's components through this common API across any language.

218
00:19:28,980 --> 00:19:34,320
So you get an element of cross-language collaboration and code reuse that's very exciting.

219
00:19:35,400 --> 00:19:37,220
We'll have to learn more about that another time.

220
00:19:37,940 --> 00:19:38,160
All right.

221
00:19:38,200 --> 00:19:38,540
Well, thanks.

222
00:19:38,720 --> 00:19:39,540
Yeah, it was fun talking to you.

223
00:19:39,540 --> 00:19:39,540
Thanks so much.

224
00:19:39,660 --> 00:19:39,740
Yeah.

225
00:19:39,940 --> 00:19:40,920
And thanks for the demo.

226
00:19:41,000 --> 00:19:41,680
You did a good job.

227
00:19:42,100 --> 00:19:42,980
Thanks for the motions.

228
00:19:43,780 --> 00:19:44,020
Thanks.

229
00:19:44,080 --> 00:19:45,040
Well, thanks for listening.

230
00:19:45,220 --> 00:19:50,320
If you're interested in the show notes for that, you can always go to tanzutalk.com and find them listed there.

231
00:19:50,460 --> 00:19:52,360
There's a video version of this interview.

232
00:19:52,360 --> 00:19:56,500
If you're interested, which also includes a demo of those new features and dagger.

233
00:19:56,800 --> 00:20:00,220
If you go to tanzutalk.com, you can find that video interview as well.

234
00:20:00,220 --> 00:20:02,760
And as a reminder, you should check out the conference.

235
00:20:02,920 --> 00:20:06,540
We have SpringOne coming up December 6th and 8th in San Francisco.

236
00:20:06,940 --> 00:20:11,100
It's all about software development, platform engineering, Kubernetes operations.

237
00:20:11,420 --> 00:20:19,260
And also, if you fancy this kind of thing, digital transformation, the sort of management and executive and business value and outcomes focus things.

238
00:20:19,420 --> 00:20:26,320
But if you go to SpringOne.io, you can use the code COTE200 to register and get $200 off.

239
00:20:27,080 --> 00:20:28,540
Because, you know, why not?

240
00:20:28,600 --> 00:20:36,940
And you can use that $200 to, I don't know, have a little party or something or just have a nice meal.

241
00:20:37,100 --> 00:20:44,760
If you end up going, I only know a few restaurants nowadays, but I'll recommend a place where you could spend much less than $200 and have a good meal.

242
00:20:45,120 --> 00:20:46,600
And with that, we'll see you next time.

243
00:20:46,740 --> 00:20:47,140
Bye-bye.

244
00:20:47,140 --> 00:20:47,360
Bye-bye.