1
00:00:06,320 --> 00:00:11,499
[Music]

2
00:00:15,360 --> 00:00:21,520
now in 2005 david foster wallace

3
00:00:19,119 --> 00:00:22,960
delivered this talk in kenyan community

4
00:00:21,520 --> 00:00:26,240
college

5
00:00:22,960 --> 00:00:28,480
and he started the talk with a parable

6
00:00:26,240 --> 00:00:32,399
the parable goes like this

7
00:00:28,480 --> 00:00:33,760
there are two fish swimming in the water

8
00:00:32,399 --> 00:00:36,320
all right

9
00:00:33,760 --> 00:00:39,600
and upon their travels they meet an

10
00:00:36,320 --> 00:00:42,160
older more tired fish and the tired fish

11
00:00:39,600 --> 00:00:44,960
goes up to them and says hey watch the

12
00:00:42,160 --> 00:00:47,440
water out there

13
00:00:44,960 --> 00:00:49,680
a moment passes

14
00:00:47,440 --> 00:00:52,320
and eventually they start parting ways

15
00:00:49,680 --> 00:00:54,160
and uh after

16
00:00:52,320 --> 00:00:59,480
after some time the two fish go to each

17
00:00:54,160 --> 00:00:59,480
other and say hey what the hell is water

18
00:01:00,640 --> 00:01:04,159
welcome to this talk this talk uh was

19
00:01:02,879 --> 00:01:05,280
called engineering kindness but in

20
00:01:04,159 --> 00:01:07,520
hindsight i should have called it

21
00:01:05,280 --> 00:01:09,520
community gardening in tech

22
00:01:07,520 --> 00:01:12,159
i just forgot to change the title my

23
00:01:09,520 --> 00:01:14,720
name is john conted content

24
00:01:12,159 --> 00:01:16,960
i've spent 17 years in sysadmin and

25
00:01:14,720 --> 00:01:19,920
devops 12 of those years contributing

26
00:01:16,960 --> 00:01:24,720
directly in five years in a various mix

27
00:01:19,920 --> 00:01:26,080
from platform to api to enablement teams

28
00:01:24,720 --> 00:01:28,640
i'm currently in service of open

29
00:01:26,080 --> 00:01:31,119
universities australia which is a

30
00:01:28,640 --> 00:01:33,439
non-profit which is a job that i really

31
00:01:31,119 --> 00:01:36,799
really like at the moment i've put some

32
00:01:33,439 --> 00:01:39,360
markers of video games released

33
00:01:36,799 --> 00:01:40,960
around this career milestones

34
00:01:39,360 --> 00:01:44,399
so i started work at around the time

35
00:01:40,960 --> 00:01:46,960
that name 10 dogs came out and yes zelda

36
00:01:44,399 --> 00:01:50,960
was five years ago i'm really sorry if

37
00:01:46,960 --> 00:01:52,720
that causes an existential angst um

38
00:01:50,960 --> 00:01:55,680
yeah i promise there's gonna be only a

39
00:01:52,720 --> 00:01:56,960
few more

40
00:01:55,680 --> 00:01:58,399
what am i going to be talking about

41
00:01:56,960 --> 00:01:59,600
today

42
00:01:58,399 --> 00:02:01,680
i'm going to be talking about a couple

43
00:01:59,600 --> 00:02:03,759
of things

44
00:02:01,680 --> 00:02:06,000
but mainly the stack

45
00:02:03,759 --> 00:02:07,360
of the issues around modern software

46
00:02:06,000 --> 00:02:09,360
development life

47
00:02:07,360 --> 00:02:11,280
the problems that we get with getting

48
00:02:09,360 --> 00:02:13,440
alignment with other people

49
00:02:11,280 --> 00:02:14,720
dealing with a lot of dependencies and

50
00:02:13,440 --> 00:02:17,760
what people

51
00:02:14,720 --> 00:02:22,360
sometimes mean when they talk and say

52
00:02:17,760 --> 00:02:22,360
hey i left because of the politics

53
00:02:22,800 --> 00:02:26,720
i'm going to be proposing a couple of

54
00:02:24,400 --> 00:02:30,160
mitigations to those issues framed

55
00:02:26,720 --> 00:02:32,959
around um the metaphors of gardening

56
00:02:30,160 --> 00:02:34,879
right and finally if there's any part of

57
00:02:32,959 --> 00:02:36,879
this talk that i hope stays with you i

58
00:02:34,879 --> 00:02:39,680
think it's the last part i'm going to be

59
00:02:36,879 --> 00:02:41,760
talking about why this matters

60
00:02:39,680 --> 00:02:44,560
maybe to you as a person

61
00:02:41,760 --> 00:02:49,959
not from productivity or better

62
00:02:44,560 --> 00:02:49,959
communities perspective but just to you

63
00:02:50,800 --> 00:02:55,440
but we're going to start with a little

64
00:02:52,319 --> 00:02:58,159
bit of a thought experiment um so and

65
00:02:55,440 --> 00:03:00,080
the talk experiment goes like this um

66
00:02:58,159 --> 00:03:01,440
let's say you and a friend right in

67
00:03:00,080 --> 00:03:03,200
software development

68
00:03:01,440 --> 00:03:05,200
um

69
00:03:03,200 --> 00:03:07,680
you have different sensibilities things

70
00:03:05,200 --> 00:03:08,720
that you believe to be true

71
00:03:07,680 --> 00:03:10,959
um

72
00:03:08,720 --> 00:03:12,800
and we placed you in a similar team

73
00:03:10,959 --> 00:03:14,560
right in the same team actually for an

74
00:03:12,800 --> 00:03:17,519
arbitrary amount of time let's say three

75
00:03:14,560 --> 00:03:20,560
years and in those three years

76
00:03:17,519 --> 00:03:22,239
you experienced similar things

77
00:03:20,560 --> 00:03:24,239
you had you came in and there was a

78
00:03:22,239 --> 00:03:25,760
really slow

79
00:03:24,239 --> 00:03:28,400
testing suite that took about a couple

80
00:03:25,760 --> 00:03:30,400
of hours to finish you had a bug you had

81
00:03:28,400 --> 00:03:33,120
an incident together

82
00:03:30,400 --> 00:03:35,599
i would pause it that by the end of that

83
00:03:33,120 --> 00:03:37,599
exercise

84
00:03:35,599 --> 00:03:39,280
you would have similar not completely

85
00:03:37,599 --> 00:03:40,879
but similar

86
00:03:39,280 --> 00:03:42,640
sensibilities about

87
00:03:40,879 --> 00:03:45,040
how to do certain things or what's

88
00:03:42,640 --> 00:03:45,040
correct

89
00:03:45,280 --> 00:03:49,200
now let's say we flip it to the opposite

90
00:03:47,760 --> 00:03:50,560
there's now

91
00:03:49,200 --> 00:03:52,319
instead of two different people there's

92
00:03:50,560 --> 00:03:54,720
two copies of you as

93
00:03:52,319 --> 00:03:56,720
derived from the snapshot of you right

94
00:03:54,720 --> 00:03:58,000
now everything that you believe in

95
00:03:56,720 --> 00:04:00,560
everything that you've experienced

96
00:03:58,000 --> 00:04:02,879
everything that you hold to be true

97
00:04:00,560 --> 00:04:04,400
and we placed those two people into

98
00:04:02,879 --> 00:04:06,640
different teams

99
00:04:04,400 --> 00:04:08,400
for the same three years and

100
00:04:06,640 --> 00:04:11,599
those two teams had different

101
00:04:08,400 --> 00:04:14,799
experiences one of you had a incredibly

102
00:04:11,599 --> 00:04:17,040
slow testing suite one had a lot of time

103
00:04:14,799 --> 00:04:20,720
to ship and

104
00:04:17,040 --> 00:04:22,240
the other you had a delivery crash where

105
00:04:20,720 --> 00:04:24,720
people were just like hey we have this

106
00:04:22,240 --> 00:04:26,840
deadline and we gotta hit it and um we

107
00:04:24,720 --> 00:04:28,639
gotta work at it

108
00:04:26,840 --> 00:04:29,440
right

109
00:04:28,639 --> 00:04:31,280
and

110
00:04:29,440 --> 00:04:33,680
only one of you had information

111
00:04:31,280 --> 00:04:36,800
disclosure issues i would pause it that

112
00:04:33,680 --> 00:04:38,320
by the end of that exercise

113
00:04:36,800 --> 00:04:39,440
would be two slightly different

114
00:04:38,320 --> 00:04:41,600
developers

115
00:04:39,440 --> 00:04:44,880
maybe even completely depending on which

116
00:04:41,600 --> 00:04:44,880
cool of thought you follow

117
00:04:46,240 --> 00:04:50,080
and what i'm trying to kind of say here

118
00:04:48,320 --> 00:04:52,320
is a lot of the things that we believe

119
00:04:50,080 --> 00:04:54,080
in are derived from the externalities or

120
00:04:52,320 --> 00:04:56,720
the things that we kind of experience in

121
00:04:54,080 --> 00:04:57,680
fact there's a thing that gets bandied

122
00:04:56,720 --> 00:05:00,080
about

123
00:04:57,680 --> 00:05:01,840
lindsay holmwood if you can hear this

124
00:05:00,080 --> 00:05:02,960
thank you i think you delivered this

125
00:05:01,840 --> 00:05:04,479
about like

126
00:05:02,960 --> 00:05:06,720
uh three years ago and they still

127
00:05:04,479 --> 00:05:07,680
remember it but basically what it talks

128
00:05:06,720 --> 00:05:08,800
about

129
00:05:07,680 --> 00:05:11,840
is

130
00:05:08,800 --> 00:05:13,919
um the fact that the artifacts that an

131
00:05:11,840 --> 00:05:16,320
organization creates the processes or

132
00:05:13,919 --> 00:05:18,240
like the software right

133
00:05:16,320 --> 00:05:20,080
are influenced by the inherent values of

134
00:05:18,240 --> 00:05:22,320
the people that make them and those

135
00:05:20,080 --> 00:05:24,800
values are derived from the basic

136
00:05:22,320 --> 00:05:26,880
assumptions that people have

137
00:05:24,800 --> 00:05:29,199
all right and vice versa

138
00:05:26,880 --> 00:05:30,880
it can flow one of two ways now for

139
00:05:29,199 --> 00:05:34,479
example if you have blameless post

140
00:05:30,880 --> 00:05:36,960
mortems inside a company right um

141
00:05:34,479 --> 00:05:38,479
people can derive the value that it

142
00:05:36,960 --> 00:05:40,320
should be a learning opportunity because

143
00:05:38,479 --> 00:05:42,639
blame is not really useful because the

144
00:05:40,320 --> 00:05:44,639
base assumption is that all software

145
00:05:42,639 --> 00:05:48,240
will go down

146
00:05:44,639 --> 00:05:48,240
it flows the other way and

147
00:05:48,320 --> 00:05:52,240
the artifacts can manifest themselves

148
00:05:50,560 --> 00:05:54,080
differently depending on who's

149
00:05:52,240 --> 00:05:55,120
interpreting that particular set of

150
00:05:54,080 --> 00:05:56,400
values

151
00:05:55,120 --> 00:05:58,400
for example

152
00:05:56,400 --> 00:06:01,280
being safe to fail can mean

153
00:05:58,400 --> 00:06:03,440
comprehensive and long test cases or

154
00:06:01,280 --> 00:06:07,840
quick feedbacks

155
00:06:03,440 --> 00:06:07,840
it just depends on who's parsing it

156
00:06:08,080 --> 00:06:12,880
now i love this this is great um i use

157
00:06:10,880 --> 00:06:15,680
it every time but there's a key

158
00:06:12,880 --> 00:06:17,600
component that's kind of missing here

159
00:06:15,680 --> 00:06:21,039
because it's not as if the basic

160
00:06:17,600 --> 00:06:23,120
assumptions that we have are hard coded

161
00:06:21,039 --> 00:06:25,199
at birth or derived from thin air or

162
00:06:23,120 --> 00:06:27,360
just materialized out of nowhere they

163
00:06:25,199 --> 00:06:28,960
come from experiences

164
00:06:27,360 --> 00:06:30,960
things that we saw

165
00:06:28,960 --> 00:06:33,120
things that have been taught to us

166
00:06:30,960 --> 00:06:35,840
things that we've experienced in other

167
00:06:33,120 --> 00:06:35,840
companies

168
00:06:36,880 --> 00:06:40,400
and so the stack kind of like looks like

169
00:06:38,479 --> 00:06:42,160
this artifacts

170
00:06:40,400 --> 00:06:45,120
are derived from values or derived from

171
00:06:42,160 --> 00:06:47,280
assumptions or derived from experiences

172
00:06:45,120 --> 00:06:49,039
i'm going to be referring to this as the

173
00:06:47,280 --> 00:06:51,680
stack for the rest of the talk just for

174
00:06:49,039 --> 00:06:51,680
simplicity

175
00:06:52,639 --> 00:06:56,960
now the difficulty of course is that

176
00:06:54,560 --> 00:06:58,639
software is made of diverse groups of

177
00:06:56,960 --> 00:07:00,560
people with different

178
00:06:58,639 --> 00:07:03,120
stacks different

179
00:07:00,560 --> 00:07:04,720
contents and

180
00:07:03,120 --> 00:07:06,479
different things that they value and

181
00:07:04,720 --> 00:07:08,560
believe in and we have

182
00:07:06,479 --> 00:07:11,360
a lot of exercises

183
00:07:08,560 --> 00:07:13,120
to navigate those we have a lot of ways

184
00:07:11,360 --> 00:07:15,759
to do those some of them low effort and

185
00:07:13,120 --> 00:07:18,800
some of them really really hard and

186
00:07:15,759 --> 00:07:21,120
sometimes we just take

187
00:07:18,800 --> 00:07:22,960
an intermediary step

188
00:07:21,120 --> 00:07:25,199
just to say hey you know what this is

189
00:07:22,960 --> 00:07:27,360
not what i 100

190
00:07:25,199 --> 00:07:30,360
buy into but this is what's good for the

191
00:07:27,360 --> 00:07:30,360
team

192
00:07:31,120 --> 00:07:36,560
but again a lot of software development

193
00:07:34,479 --> 00:07:38,479
doesn't just rely on the work of one

194
00:07:36,560 --> 00:07:40,080
team in fact a lot of it relies on the

195
00:07:38,479 --> 00:07:42,800
work of multiple teams as part of a

196
00:07:40,080 --> 00:07:44,319
superset each of them having settled on

197
00:07:42,800 --> 00:07:45,520
their own particular trade-offs and

198
00:07:44,319 --> 00:07:48,080
cadences

199
00:07:45,520 --> 00:07:50,560
and some a lot of the time it's actually

200
00:07:48,080 --> 00:07:52,400
supersets of supersets

201
00:07:50,560 --> 00:07:54,720
of which many

202
00:07:52,400 --> 00:07:59,840
are actually highly interconnected and

203
00:07:54,720 --> 00:07:59,840
very dependent on each other

204
00:08:01,280 --> 00:08:05,440
and it really doesn't help

205
00:08:03,199 --> 00:08:05,440
that

206
00:08:06,479 --> 00:08:10,720
the mores that we have for interacting

207
00:08:09,199 --> 00:08:14,080
or unpacking this

208
00:08:10,720 --> 00:08:16,800
stacks of other people within other

209
00:08:14,080 --> 00:08:18,319
teams aren't that well developed because

210
00:08:16,800 --> 00:08:20,960
for all intents and purposes as a

211
00:08:18,319 --> 00:08:24,720
default as a default right when we talk

212
00:08:20,960 --> 00:08:26,879
about things we only uncover a part of

213
00:08:24,720 --> 00:08:29,520
that stack for the other person why do

214
00:08:26,879 --> 00:08:31,919
you believe in this particular thing why

215
00:08:29,520 --> 00:08:33,680
do you create this particular thing what

216
00:08:31,919 --> 00:08:35,839
underlying experiences have informed

217
00:08:33,680 --> 00:08:35,839
that

218
00:08:36,080 --> 00:08:42,240
and so often it breaks down

219
00:08:38,839 --> 00:08:45,519
and sometimes expresses itself in

220
00:08:42,240 --> 00:08:47,680
differences in um software patterns or

221
00:08:45,519 --> 00:08:49,440
even like applications um we're

222
00:08:47,680 --> 00:08:52,800
basically talking about conway's law

223
00:08:49,440 --> 00:08:55,279
here um which isn't all that bad in fact

224
00:08:52,800 --> 00:08:56,320
i think the move to microservice was an

225
00:08:55,279 --> 00:08:59,920
attempt

226
00:08:56,320 --> 00:09:01,920
to remedy some of that but where it gets

227
00:08:59,920 --> 00:09:03,680
kind of dangerous and

228
00:09:01,920 --> 00:09:05,279
a little bit important to watch out for

229
00:09:03,680 --> 00:09:09,120
is when it results in social

230
00:09:05,279 --> 00:09:11,760
bifurcations over time um

231
00:09:09,120 --> 00:09:13,839
people having a default set of beliefs

232
00:09:11,760 --> 00:09:15,279
about a certain group of people mainly

233
00:09:13,839 --> 00:09:17,760
because of the limited amount of

234
00:09:15,279 --> 00:09:19,839
interactions that you have

235
00:09:17,760 --> 00:09:22,560
and this causes friction and it gets

236
00:09:19,839 --> 00:09:24,640
harder and harder to talk

237
00:09:22,560 --> 00:09:26,240
to people who have developed certain

238
00:09:24,640 --> 00:09:27,760
assumptions about you and this is a

239
00:09:26,240 --> 00:09:29,519
thing that will happen

240
00:09:27,760 --> 00:09:32,000
again and again

241
00:09:29,519 --> 00:09:32,000
and again

242
00:09:35,279 --> 00:09:39,040
now i don't need to say that this is

243
00:09:37,120 --> 00:09:41,360
incredibly exhausting

244
00:09:39,040 --> 00:09:41,360
um

245
00:09:41,600 --> 00:09:45,279
and i'm going to be talking about a

246
00:09:43,200 --> 00:09:47,680
couple of mitigations

247
00:09:45,279 --> 00:09:47,680
about

248
00:09:47,839 --> 00:09:52,399
bridging the gap between groups of

249
00:09:50,320 --> 00:09:54,399
people disparate groups of people that

250
00:09:52,399 --> 00:09:56,480
believe in different things within the

251
00:09:54,399 --> 00:09:57,680
software community and it's formed

252
00:09:56,480 --> 00:10:01,120
around the

253
00:09:57,680 --> 00:10:04,160
central hypothesis on and because of the

254
00:10:01,120 --> 00:10:05,760
interconnectedness of the the outputs

255
00:10:04,160 --> 00:10:08,160
that people have to the values and the

256
00:10:05,760 --> 00:10:10,880
experiences the base assumptions that we

257
00:10:08,160 --> 00:10:14,560
have it is entirely possible

258
00:10:10,880 --> 00:10:16,800
to construct better culture

259
00:10:14,560 --> 00:10:19,800
through better artifacts

260
00:10:16,800 --> 00:10:19,800
right

261
00:10:22,079 --> 00:10:24,640
cool

262
00:10:23,440 --> 00:10:27,680
so i'm going to be talking about

263
00:10:24,640 --> 00:10:29,440
community gardening um so what what are

264
00:10:27,680 --> 00:10:30,959
the many ways that we can kind of like

265
00:10:29,440 --> 00:10:32,800
tackle this issue

266
00:10:30,959 --> 00:10:34,079
i'm going to be using a lot of practical

267
00:10:32,800 --> 00:10:35,839
um

268
00:10:34,079 --> 00:10:37,120
things a lot of things actually derived

269
00:10:35,839 --> 00:10:38,959
from real life so there's going to be a

270
00:10:37,120 --> 00:10:41,440
lot of screenshots and a lot of them are

271
00:10:38,959 --> 00:10:44,079
going to be redacted so i i hope that's

272
00:10:41,440 --> 00:10:47,040
not incredibly annoying

273
00:10:44,079 --> 00:10:49,519
i'm also going to be using uh gardening

274
00:10:47,040 --> 00:10:52,640
as a metaphor because like many people

275
00:10:49,519 --> 00:10:54,880
in lockdown um i've over indexed on

276
00:10:52,640 --> 00:10:57,600
buying a lot of plants just to see

277
00:10:54,880 --> 00:11:01,200
something alive

278
00:10:57,600 --> 00:11:04,000
so which is great um so what do i talk

279
00:11:01,200 --> 00:11:05,200
about when i talk about seeding um

280
00:11:04,000 --> 00:11:07,279
when i talk about seeding i'm talking

281
00:11:05,200 --> 00:11:09,040
about positive feedback loops what are

282
00:11:07,279 --> 00:11:10,640
the things that we can do to make more

283
00:11:09,040 --> 00:11:11,839
things similar to that kind of like

284
00:11:10,640 --> 00:11:13,760
happen

285
00:11:11,839 --> 00:11:15,360
and effectively with the target state of

286
00:11:13,760 --> 00:11:17,680
creating inter-team

287
00:11:15,360 --> 00:11:19,839
patterns or formats for inter-team

288
00:11:17,680 --> 00:11:20,800
communications within a shared space

289
00:11:19,839 --> 00:11:22,160
right

290
00:11:20,800 --> 00:11:23,760
um

291
00:11:22,160 --> 00:11:26,160
because for all intents and purposes

292
00:11:23,760 --> 00:11:27,839
slack is kind of like an artifact right

293
00:11:26,160 --> 00:11:30,000
if you think about it it functions

294
00:11:27,839 --> 00:11:32,399
similarly to an event stream where

295
00:11:30,000 --> 00:11:33,680
there's multiple subscribers trying to

296
00:11:32,399 --> 00:11:36,160
pull data

297
00:11:33,680 --> 00:11:40,079
right and actioning it

298
00:11:36,160 --> 00:11:40,079
within their own role or capability

299
00:11:40,399 --> 00:11:44,480
and if you think about it um what a lot

300
00:11:42,880 --> 00:11:47,440
of new people actually do within a

301
00:11:44,480 --> 00:11:49,360
company is that they look at how people

302
00:11:47,440 --> 00:11:51,440
talk to each other what's the patterns

303
00:11:49,360 --> 00:11:53,120
how do i engage support how do i talk to

304
00:11:51,440 --> 00:11:56,079
other people how do i ask questions for

305
00:11:53,120 --> 00:11:58,240
the api team and then they copy it right

306
00:11:56,079 --> 00:11:59,839
um so a lot of the patterns that we have

307
00:11:58,240 --> 00:12:01,360
talking to each other kind of propagate

308
00:11:59,839 --> 00:12:03,200
by itself

309
00:12:01,360 --> 00:12:04,800
and we do this kind of thing

310
00:12:03,200 --> 00:12:05,680
unconsciously

311
00:12:04,800 --> 00:12:07,680
right

312
00:12:05,680 --> 00:12:08,880
through the things that we choose to

313
00:12:07,680 --> 00:12:11,120
surface

314
00:12:08,880 --> 00:12:13,040
or the way we ask questions for even the

315
00:12:11,120 --> 00:12:15,040
way that we respond

316
00:12:13,040 --> 00:12:19,839
right this gets copied by other people

317
00:12:15,040 --> 00:12:19,839
and propagated again and again and again

318
00:12:21,839 --> 00:12:26,639
so here's the question what's possible

319
00:12:24,079 --> 00:12:28,399
if we inspect and create these patterns

320
00:12:26,639 --> 00:12:29,519
with a full awareness

321
00:12:28,399 --> 00:12:32,240
that

322
00:12:29,519 --> 00:12:33,680
they should have a particular intent

323
00:12:32,240 --> 00:12:35,040
and i'm going to use incident reporting

324
00:12:33,680 --> 00:12:37,440
because it's one of the first things

325
00:12:35,040 --> 00:12:39,040
that i personally do

326
00:12:37,440 --> 00:12:41,279
where do you see the stuff that's broken

327
00:12:39,040 --> 00:12:42,639
how do people talk about the stuff

328
00:12:41,279 --> 00:12:44,240
that's broken

329
00:12:42,639 --> 00:12:46,079
nice and easy

330
00:12:44,240 --> 00:12:47,760
um

331
00:12:46,079 --> 00:12:48,639
the

332
00:12:47,760 --> 00:12:50,320
so

333
00:12:48,639 --> 00:12:53,440
here's a question right like you come

334
00:12:50,320 --> 00:12:55,279
into a company you're new it's day one

335
00:12:53,440 --> 00:12:57,760
and you go to the incidents channel and

336
00:12:55,279 --> 00:12:59,760
it's a bunch of posts like this people

337
00:12:57,760 --> 00:13:01,519
just posting screenshots without any

338
00:12:59,760 --> 00:13:03,600
particular contacts and threads and just

339
00:13:01,519 --> 00:13:04,800
indexing on reactions what would you

340
00:13:03,600 --> 00:13:06,959
derive

341
00:13:04,800 --> 00:13:08,480
about the particular values what's

342
00:13:06,959 --> 00:13:10,480
important

343
00:13:08,480 --> 00:13:12,480
to the people

344
00:13:10,480 --> 00:13:15,760
that have created this messaging pattern

345
00:13:12,480 --> 00:13:15,760
about things that are broken

346
00:13:16,959 --> 00:13:19,959
right

347
00:13:23,519 --> 00:13:28,480
example two

348
00:13:26,000 --> 00:13:31,360
you're over the new company um and

349
00:13:28,480 --> 00:13:33,440
instead of seeing that big spray of like

350
00:13:31,360 --> 00:13:34,399
um messages you have this highly

351
00:13:33,440 --> 00:13:36,240
structured

352
00:13:34,399 --> 00:13:37,680
um kind of like format and there's

353
00:13:36,240 --> 00:13:40,000
actually a forum

354
00:13:37,680 --> 00:13:42,240
um on the topic and when when you click

355
00:13:40,000 --> 00:13:43,760
on the topic it prompts you for like

356
00:13:42,240 --> 00:13:48,680
nine different fields that you have to

357
00:13:43,760 --> 00:13:48,680
fill in to be able to interact with it

358
00:13:50,639 --> 00:13:54,959
i'll tell you what i kind of like derive

359
00:13:52,399 --> 00:13:56,959
from it right i would my basic

360
00:13:54,959 --> 00:13:59,040
assumption is that the person who made

361
00:13:56,959 --> 00:14:01,279
this probably has seen their share of

362
00:13:59,040 --> 00:14:03,920
incidents and probably

363
00:14:01,279 --> 00:14:05,519
values a lot of the information points

364
00:14:03,920 --> 00:14:06,880
that is over here

365
00:14:05,519 --> 00:14:08,720
right

366
00:14:06,880 --> 00:14:11,040
there's not a lot

367
00:14:08,720 --> 00:14:12,800
here as an artifact in terms of like how

368
00:14:11,040 --> 00:14:14,560
do you talk to other people or who do

369
00:14:12,800 --> 00:14:17,440
you reach out to which means it's

370
00:14:14,560 --> 00:14:21,680
probably secondary as a priority it's

371
00:14:17,440 --> 00:14:21,680
more there as an announcement piece

372
00:14:23,519 --> 00:14:27,600
this is what i personally kind of like

373
00:14:25,040 --> 00:14:28,959
start with as an artifact

374
00:14:27,600 --> 00:14:31,040
so there's a couple of things kind of

375
00:14:28,959 --> 00:14:33,199
like going on here in that the incident

376
00:14:31,040 --> 00:14:36,000
one the incident channel is separate

377
00:14:33,199 --> 00:14:38,480
because i would like to separate

378
00:14:36,000 --> 00:14:40,079
the use case of announcing and letting

379
00:14:38,480 --> 00:14:42,560
people know what they need to know about

380
00:14:40,079 --> 00:14:45,199
the incident versus the discussion about

381
00:14:42,560 --> 00:14:47,519
remediating it

382
00:14:45,199 --> 00:14:49,360
the second is that

383
00:14:47,519 --> 00:14:52,399
there's um

384
00:14:49,360 --> 00:14:54,240
there's a very very small

385
00:14:52,399 --> 00:14:57,120
set of fields because that's what i kind

386
00:14:54,240 --> 00:15:01,120
of index to do that's what i value

387
00:14:57,120 --> 00:15:01,120
i value simple rules

388
00:15:02,000 --> 00:15:06,959
right and those are implicit in that

389
00:15:04,079 --> 00:15:10,160
artifact but sometimes implicit doesn't

390
00:15:06,959 --> 00:15:12,880
quite cut it we need to be explicit

391
00:15:10,160 --> 00:15:15,199
here's another artifact a postmortem

392
00:15:12,880 --> 00:15:17,519
right um this is a screenshot from a

393
00:15:15,199 --> 00:15:20,800
postmortem that i just did a couple of

394
00:15:17,519 --> 00:15:23,440
weeks ago um and there's an explicit

395
00:15:20,800 --> 00:15:26,399
call out to a set of behaviors that

396
00:15:23,440 --> 00:15:28,560
everybody has to be able to do or

397
00:15:26,399 --> 00:15:30,560
basic assumptions for people who haven't

398
00:15:28,560 --> 00:15:33,199
done blameless postmortems before it's

399
00:15:30,560 --> 00:15:35,519
basically using root cause analyses to

400
00:15:33,199 --> 00:15:37,360
find out systemic

401
00:15:35,519 --> 00:15:38,480
issues that might have caused an

402
00:15:37,360 --> 00:15:41,360
incident

403
00:15:38,480 --> 00:15:44,000
with the very express requirement that

404
00:15:41,360 --> 00:15:46,320
we do not talk about human error as a

405
00:15:44,000 --> 00:15:48,639
root cause

406
00:15:46,320 --> 00:15:50,720
all right individual blame is not a

407
00:15:48,639 --> 00:15:54,560
useful artifact and sometimes you need

408
00:15:50,720 --> 00:15:56,800
to be really really explicit about it

409
00:15:54,560 --> 00:15:59,360
these implications also exist just in

410
00:15:56,800 --> 00:16:02,000
the way that we format um

411
00:15:59,360 --> 00:16:04,800
or the commonly agreed formats by how we

412
00:16:02,000 --> 00:16:06,560
talk to other people you probably have a

413
00:16:04,800 --> 00:16:08,639
support team in your company that you

414
00:16:06,560 --> 00:16:10,800
contact for particular needs for

415
00:16:08,639 --> 00:16:12,399
infrastructure maybe you don't but maybe

416
00:16:10,800 --> 00:16:15,360
you do and

417
00:16:12,399 --> 00:16:17,360
for example this artifact um

418
00:16:15,360 --> 00:16:19,759
this way of talking to other people has

419
00:16:17,360 --> 00:16:22,800
an implication that hey i emoji this

420
00:16:19,759 --> 00:16:26,079
someone owns your problem there's a

421
00:16:22,800 --> 00:16:28,160
thread here which means we value

422
00:16:26,079 --> 00:16:30,320
the attention economy of the other

423
00:16:28,160 --> 00:16:31,839
people in the channel by making sure

424
00:16:30,320 --> 00:16:35,959
they're not notified when it's not

425
00:16:31,839 --> 00:16:35,959
pertinent to them

426
00:16:36,320 --> 00:16:38,560
right

427
00:16:41,279 --> 00:16:46,160
and and this

428
00:16:43,199 --> 00:16:48,240
these small choices exist

429
00:16:46,160 --> 00:16:50,399
um these heading choices access

430
00:16:48,240 --> 00:16:52,880
throughout um just

431
00:16:50,399 --> 00:16:55,440
even the most banal of like interactions

432
00:16:52,880 --> 00:16:57,360
even and even in the most innocuous ones

433
00:16:55,440 --> 00:16:59,360
that we didn't think would have an

434
00:16:57,360 --> 00:17:02,279
impact it's there in the things that we

435
00:16:59,360 --> 00:17:05,280
choose to celebrate it's there in the

436
00:17:02,279 --> 00:17:07,120
conversations that we choose to surface

437
00:17:05,280 --> 00:17:09,039
with the rest of the organization what

438
00:17:07,120 --> 00:17:11,280
do we share

439
00:17:09,039 --> 00:17:11,280
right

440
00:17:11,360 --> 00:17:15,199
because for all intents and purposes the

441
00:17:13,120 --> 00:17:17,439
way that we structure our messages is an

442
00:17:15,199 --> 00:17:19,919
expression of intent it says

443
00:17:17,439 --> 00:17:22,160
a lot implicitly

444
00:17:19,919 --> 00:17:24,079
by

445
00:17:22,160 --> 00:17:26,079
just how it's set up or how it's

446
00:17:24,079 --> 00:17:30,039
structured or how how we think other

447
00:17:26,079 --> 00:17:30,039
people should consume it

448
00:17:32,000 --> 00:17:35,600
i'm going to be talking about um

449
00:17:33,200 --> 00:17:37,039
cultivation and trellises

450
00:17:35,600 --> 00:17:39,360
when i talk about cultivation and

451
00:17:37,039 --> 00:17:42,400
trellises what i mean is that now that

452
00:17:39,360 --> 00:17:44,400
we've set up a couple of norms about how

453
00:17:42,400 --> 00:17:46,160
people should talk to each other in a

454
00:17:44,400 --> 00:17:48,640
productive way how do we make it

455
00:17:46,160 --> 00:17:51,120
actually kind of productive um how do we

456
00:17:48,640 --> 00:17:53,919
make it have impact and the way that i'm

457
00:17:51,120 --> 00:17:56,000
going to frame this is with my favorite

458
00:17:53,919 --> 00:17:57,919
bug bears or least favorite bugbish

459
00:17:56,000 --> 00:18:01,360
which is this communication pattern that

460
00:17:57,919 --> 00:18:04,400
you see a lot in organizations

461
00:18:01,360 --> 00:18:07,360
someone needs to talk to another thing

462
00:18:04,400 --> 00:18:10,000
another team about a shared concern

463
00:18:07,360 --> 00:18:12,240
right person one escalates their issue

464
00:18:10,000 --> 00:18:14,480
to a manager manager passes it on to

465
00:18:12,240 --> 00:18:16,640
another manager and then it kind of gets

466
00:18:14,480 --> 00:18:18,640
passed on and

467
00:18:16,640 --> 00:18:20,480
i i loathe this

468
00:18:18,640 --> 00:18:23,440
um for for

469
00:18:20,480 --> 00:18:26,240
various reasons but mainly the fact that

470
00:18:23,440 --> 00:18:27,280
it's time consuming and it's also very

471
00:18:26,240 --> 00:18:28,720
lossy

472
00:18:27,280 --> 00:18:30,480
it's time consuming because you have to

473
00:18:28,720 --> 00:18:34,080
wait for multiple people to pass on the

474
00:18:30,480 --> 00:18:36,080
message it's lossly because the people

475
00:18:34,080 --> 00:18:37,760
who are relaying

476
00:18:36,080 --> 00:18:41,280
information about the context are not

477
00:18:37,760 --> 00:18:43,520
the ones closest to the problem space

478
00:18:41,280 --> 00:18:46,400
so i generally index a lot of like

479
00:18:43,520 --> 00:18:48,799
organizational communication structures

480
00:18:46,400 --> 00:18:50,880
to enable people closer to the problem

481
00:18:48,799 --> 00:18:52,000
space to be able to collaborate and make

482
00:18:50,880 --> 00:18:55,039
decisions

483
00:18:52,000 --> 00:18:55,039
right without

484
00:18:55,360 --> 00:18:59,760
anyone else being kind of like involved

485
00:18:57,520 --> 00:19:01,679
for example um

486
00:18:59,760 --> 00:19:03,200
in a lot of companies we frequently have

487
00:19:01,679 --> 00:19:06,240
questions of hey what should be the

488
00:19:03,200 --> 00:19:08,160
consistent way of like doing blah right

489
00:19:06,240 --> 00:19:11,840
not the standard but sort of like what's

490
00:19:08,160 --> 00:19:11,840
the default way that we do things

491
00:19:12,000 --> 00:19:16,480
one of the artifacts that i like to use

492
00:19:15,039 --> 00:19:17,440
is

493
00:19:16,480 --> 00:19:19,600
called

494
00:19:17,440 --> 00:19:22,320
sensible defaults

495
00:19:19,600 --> 00:19:23,600
so this is sensible default is basically

496
00:19:22,320 --> 00:19:26,000
repo

497
00:19:23,600 --> 00:19:28,000
and the repo

498
00:19:26,000 --> 00:19:29,840
has a couple of like folders that

499
00:19:28,000 --> 00:19:32,480
pertain to particular concerns and each

500
00:19:29,840 --> 00:19:34,880
of them contain an md file that says hey

501
00:19:32,480 --> 00:19:37,840
this is probably how we should do things

502
00:19:34,880 --> 00:19:39,360
by default in this particular area

503
00:19:37,840 --> 00:19:40,640
it starts with the readme and the readme

504
00:19:39,360 --> 00:19:42,480
looks like this

505
00:19:40,640 --> 00:19:44,080
right always looks like this when i've

506
00:19:42,480 --> 00:19:47,120
set this up across multiple companies

507
00:19:44,080 --> 00:19:48,240
and it kind of starts the same

508
00:19:47,120 --> 00:19:50,720
and

509
00:19:48,240 --> 00:19:53,600
side note whenever you're creating

510
00:19:50,720 --> 00:19:55,120
communication patterns for

511
00:19:53,600 --> 00:19:57,679
disparate groups of people within an

512
00:19:55,120 --> 00:20:00,320
organization it's really important that

513
00:19:57,679 --> 00:20:02,720
the rules are simple

514
00:20:00,320 --> 00:20:03,840
simple rules create complex intelligent

515
00:20:02,720 --> 00:20:06,559
behavior

516
00:20:03,840 --> 00:20:08,559
complex rules create [ __ ] so

517
00:20:06,559 --> 00:20:10,640
which is optimal

518
00:20:08,559 --> 00:20:13,520
um

519
00:20:10,640 --> 00:20:16,159
yeah so anyway yeah so p and and the

520
00:20:13,520 --> 00:20:17,520
rules here is that basically um people

521
00:20:16,159 --> 00:20:18,720
who care about a certain thing make a

522
00:20:17,520 --> 00:20:20,480
pull request

523
00:20:18,720 --> 00:20:22,480
other people discuss it and then sort of

524
00:20:20,480 --> 00:20:25,200
like if people agree they kind of merge

525
00:20:22,480 --> 00:20:27,120
it it looks a little bit like this

526
00:20:25,200 --> 00:20:28,880
it lets people who care about certain

527
00:20:27,120 --> 00:20:30,880
things or really really care about

528
00:20:28,880 --> 00:20:34,640
certain things

529
00:20:30,880 --> 00:20:35,679
drive policy or actually inform people

530
00:20:34,640 --> 00:20:38,159
or or

531
00:20:35,679 --> 00:20:40,000
pass along knowledge right hey this is

532
00:20:38,159 --> 00:20:41,600
probably the way we should consider

533
00:20:40,000 --> 00:20:44,960
doing things there's people who really

534
00:20:41,600 --> 00:20:46,799
care about security um last week

535
00:20:44,960 --> 00:20:49,039
i had the sensible people come through

536
00:20:46,799 --> 00:20:51,600
for accessibility which is awesome it's

537
00:20:49,039 --> 00:20:51,600
pretty sick

538
00:20:52,720 --> 00:20:57,760
it also lets people who

539
00:20:55,919 --> 00:20:59,520
care about the problem space but think

540
00:20:57,760 --> 00:21:04,080
differently

541
00:20:59,520 --> 00:21:06,240
be able to unpack their stack right

542
00:21:04,080 --> 00:21:08,240
why they believe differently and the

543
00:21:06,240 --> 00:21:10,640
underlying reasons for that and to be

544
00:21:08,240 --> 00:21:13,760
able to reason about it in a space

545
00:21:10,640 --> 00:21:17,640
that's reasonably open

546
00:21:13,760 --> 00:21:17,640
available to everybody

547
00:21:17,760 --> 00:21:20,960
and it kind of just grows by itself to

548
00:21:19,840 --> 00:21:22,720
be honest

549
00:21:20,960 --> 00:21:25,919
it's pretty cool um

550
00:21:22,720 --> 00:21:28,320
a couple of bonus points is it's uh

551
00:21:25,919 --> 00:21:31,120
um this is more of a side note it's

552
00:21:28,320 --> 00:21:33,600
given a lot of teams some ability to be

553
00:21:31,120 --> 00:21:35,600
able to like push back on like um

554
00:21:33,600 --> 00:21:38,000
things like hey we should do this as a

555
00:21:35,600 --> 00:21:39,760
tactical fix because um they've been

556
00:21:38,000 --> 00:21:41,120
able to rationalize that hey you know

557
00:21:39,760 --> 00:21:43,039
like this

558
00:21:41,120 --> 00:21:45,679
we have a set of standards pseudo

559
00:21:43,039 --> 00:21:47,760
standards around what constitutes

560
00:21:45,679 --> 00:21:49,840
production software so we really can't

561
00:21:47,760 --> 00:21:52,320
do that as much as we'd like to

562
00:21:49,840 --> 00:21:54,559
um it's also a great onboarding tool we

563
00:21:52,320 --> 00:21:57,600
just hand it to hr and then they they

564
00:21:54,559 --> 00:21:59,840
link it to newcomers and um who knew

565
00:21:57,600 --> 00:22:01,760
like um the default way of doing things

566
00:21:59,840 --> 00:22:03,600
is one of the most important

567
00:22:01,760 --> 00:22:07,200
things that people probably want to know

568
00:22:03,600 --> 00:22:07,200
when they join an org it's awesome

569
00:22:10,080 --> 00:22:15,600
second

570
00:22:11,280 --> 00:22:17,600
pattern um is um decision tech groups

571
00:22:15,600 --> 00:22:19,679
um and decision tech groups are very

572
00:22:17,600 --> 00:22:21,919
very similar to a guild you you

573
00:22:19,679 --> 00:22:24,000
basically have a couple of people

574
00:22:21,919 --> 00:22:25,600
representatives from a team it doesn't

575
00:22:24,000 --> 00:22:28,559
matter how senior they are they just

576
00:22:25,600 --> 00:22:31,360
have to care about it um and then we

577
00:22:28,559 --> 00:22:32,559
just talk about the shared space and

578
00:22:31,360 --> 00:22:34,320
you know it doesn't have to be

579
00:22:32,559 --> 00:22:36,080
synchronous it could just be like a

580
00:22:34,320 --> 00:22:37,679
couple of boards that happen every other

581
00:22:36,080 --> 00:22:41,120
week and talking about what's most

582
00:22:37,679 --> 00:22:43,360
important to everyone and their teams

583
00:22:41,120 --> 00:22:43,360
right

584
00:22:44,559 --> 00:22:48,000
and then we kind of like action those

585
00:22:46,080 --> 00:22:48,880
things um

586
00:22:48,000 --> 00:22:51,360
the

587
00:22:48,880 --> 00:22:51,360
it's it's

588
00:22:51,440 --> 00:22:54,480
different from a guild in that it

589
00:22:53,520 --> 00:22:56,720
focuses

590
00:22:54,480 --> 00:22:59,600
on making decisions about

591
00:22:56,720 --> 00:23:01,840
those things enabling people basically

592
00:22:59,600 --> 00:23:04,320
to make decisions

593
00:23:01,840 --> 00:23:05,919
people close to the problem space to

594
00:23:04,320 --> 00:23:08,880
make decisions about the thing that they

595
00:23:05,919 --> 00:23:12,559
care the most about um

596
00:23:08,880 --> 00:23:14,159
and when the the defaults need to change

597
00:23:12,559 --> 00:23:17,440
they're the ones who discuss it and

598
00:23:14,159 --> 00:23:20,159
discuss what constitutes success for

599
00:23:17,440 --> 00:23:23,039
like a successful spy hey if we want to

600
00:23:20,159 --> 00:23:24,080
add for example honeycomb to all of our

601
00:23:23,039 --> 00:23:27,440
stacks

602
00:23:24,080 --> 00:23:30,799
um this is probably what all of us would

603
00:23:27,440 --> 00:23:32,720
agree on is um is a minimum that we

604
00:23:30,799 --> 00:23:35,360
would like to have

605
00:23:32,720 --> 00:23:37,760
when we roll it out

606
00:23:35,360 --> 00:23:41,120
um it can be async and cheap it doesn't

607
00:23:37,760 --> 00:23:42,880
it doesn't need meetings um i definitely

608
00:23:41,120 --> 00:23:45,600
index on having less synchronous

609
00:23:42,880 --> 00:23:48,240
meetings as much as possible um

610
00:23:45,600 --> 00:23:50,000
it's also open to everyone regardless of

611
00:23:48,240 --> 00:23:52,000
seniority and there's some optionality

612
00:23:50,000 --> 00:23:54,320
and involvement not every problem needs

613
00:23:52,000 --> 00:23:57,039
to have everyone only the people who

614
00:23:54,320 --> 00:23:57,039
care about it

615
00:23:57,279 --> 00:24:00,960
a couple of like bonuses

616
00:23:58,960 --> 00:24:02,640
the fact that it's open right like

617
00:24:00,960 --> 00:24:05,039
people

618
00:24:02,640 --> 00:24:06,320
can attend any decision group that they

619
00:24:05,039 --> 00:24:08,320
want to be in

620
00:24:06,320 --> 00:24:10,000
um empowers people and gives them a

621
00:24:08,320 --> 00:24:12,400
sense that hey

622
00:24:10,000 --> 00:24:15,200
if i'm in this organization and i would

623
00:24:12,400 --> 00:24:17,360
like something to change i have very

624
00:24:15,200 --> 00:24:20,799
very clear mechanisms and groups of

625
00:24:17,360 --> 00:24:24,720
people that i can consult and it's

626
00:24:20,799 --> 00:24:26,400
a single hop it's not this multiple hob

627
00:24:24,720 --> 00:24:27,679
nightmare where we have to like navigate

628
00:24:26,400 --> 00:24:29,520
bureaucracy it's nice and

629
00:24:27,679 --> 00:24:31,520
straightforward

630
00:24:29,520 --> 00:24:33,360
it's empowering

631
00:24:31,520 --> 00:24:35,520
it's also a great pipeline for seniors

632
00:24:33,360 --> 00:24:38,640
because of what happens when people turn

633
00:24:35,520 --> 00:24:40,640
senior sister suddenly allocated a big

634
00:24:38,640 --> 00:24:43,200
amount of like

635
00:24:40,640 --> 00:24:44,960
high level problem sets and it's hard to

636
00:24:43,200 --> 00:24:46,720
navigate if like you're new to it and

637
00:24:44,960 --> 00:24:48,000
what it gives on

638
00:24:46,720 --> 00:24:50,880
people who are

639
00:24:48,000 --> 00:24:54,640
newer to the industry is the muscle

640
00:24:50,880 --> 00:24:58,320
memory to be able to unpack

641
00:24:54,640 --> 00:25:02,320
smaller but wider problem sets and gain

642
00:24:58,320 --> 00:25:05,360
more confidence um and and and and yeah

643
00:25:02,320 --> 00:25:08,000
just just to um have the space to be

644
00:25:05,360 --> 00:25:08,000
good at it

645
00:25:09,440 --> 00:25:14,799
now

646
00:25:11,279 --> 00:25:16,559
i'll talk about pruning um because um

647
00:25:14,799 --> 00:25:18,320
regardless of everything that we do if

648
00:25:16,559 --> 00:25:20,400
we have decision groups or sensible

649
00:25:18,320 --> 00:25:22,720
defaults or github or good norms and

650
00:25:20,400 --> 00:25:25,200
slack sometimes things go bad and

651
00:25:22,720 --> 00:25:27,039
unfortunately this is the thing i have

652
00:25:25,200 --> 00:25:29,440
the least amount of content on because

653
00:25:27,039 --> 00:25:30,559
i'm not even sure if i'm doing it right

654
00:25:29,440 --> 00:25:32,480
yet

655
00:25:30,559 --> 00:25:34,000
once i do i'll be i'll talk to you about

656
00:25:32,480 --> 00:25:36,000
it but

657
00:25:34,000 --> 00:25:37,520
right now i don't know i don't know if

658
00:25:36,000 --> 00:25:39,440
i'm doing this well i will say two

659
00:25:37,520 --> 00:25:41,919
things though um

660
00:25:39,440 --> 00:25:45,279
from a community gardening perspective

661
00:25:41,919 --> 00:25:47,600
if you take on that responsibility

662
00:25:45,279 --> 00:25:51,279
that's a very different responsibility

663
00:25:47,600 --> 00:25:51,279
from participating in

664
00:25:51,440 --> 00:25:56,000
what you call this in the community

665
00:25:53,760 --> 00:25:57,360
and to clarify that what i mean is that

666
00:25:56,000 --> 00:25:59,320
when you're participating in a

667
00:25:57,360 --> 00:26:01,919
conversation your set of

668
00:25:59,320 --> 00:26:04,240
responsibilities is uncovering the

669
00:26:01,919 --> 00:26:06,799
layers of your stack and making other

670
00:26:04,240 --> 00:26:07,600
people understand it or

671
00:26:06,799 --> 00:26:09,120
um

672
00:26:07,600 --> 00:26:11,039
under trying to understand other

673
00:26:09,120 --> 00:26:13,039
people's stack

674
00:26:11,039 --> 00:26:14,400
experiences and you know the underlying

675
00:26:13,039 --> 00:26:16,880
values that they have

676
00:26:14,400 --> 00:26:18,400
when you're moderating your focus is

677
00:26:16,880 --> 00:26:21,200
making sure

678
00:26:18,400 --> 00:26:24,559
that people have the means

679
00:26:21,200 --> 00:26:26,240
to do it and that they do it well um and

680
00:26:24,559 --> 00:26:30,240
asking the right questions and not

681
00:26:26,240 --> 00:26:30,240
making default assumptions about people

682
00:26:30,799 --> 00:26:34,559
the second is don't let things faster

683
00:26:35,120 --> 00:26:40,000
it's particularly important especially

684
00:26:37,840 --> 00:26:41,679
now that um

685
00:26:40,000 --> 00:26:43,039
uh what they call this

686
00:26:41,679 --> 00:26:44,240
um

687
00:26:43,039 --> 00:26:45,440
is

688
00:26:44,240 --> 00:26:47,120
that

689
00:26:45,440 --> 00:26:49,039
everyone's a little bit a tiny little

690
00:26:47,120 --> 00:26:52,799
bit more separated um

691
00:26:49,039 --> 00:26:55,520
when when things go bad or don't go well

692
00:26:52,799 --> 00:26:57,760
between like two people it's it festers

693
00:26:55,520 --> 00:26:59,360
very very quickly at an alarming rate

694
00:26:57,760 --> 00:27:02,400
that's honestly like a little bit

695
00:26:59,360 --> 00:27:05,440
surprising so as much as possible

696
00:27:02,400 --> 00:27:06,960
stamp it out before it gets bad um it

697
00:27:05,440 --> 00:27:08,559
very quickly

698
00:27:06,960 --> 00:27:11,360
gets to the point where it's very very

699
00:27:08,559 --> 00:27:11,360
difficult to repair

700
00:27:12,240 --> 00:27:17,919
now

701
00:27:13,679 --> 00:27:20,720
finally i'm i'm going to talk about

702
00:27:17,919 --> 00:27:22,320
why this matters to you as a person

703
00:27:20,720 --> 00:27:24,640
right kind of important to you as a

704
00:27:22,320 --> 00:27:24,640
person

705
00:27:24,960 --> 00:27:28,320
for

706
00:27:25,919 --> 00:27:30,000
all intents

707
00:27:28,320 --> 00:27:32,240
and purposes

708
00:27:30,000 --> 00:27:32,240
right

709
00:27:32,640 --> 00:27:38,320
trying to unpack or understand um what

710
00:27:35,840 --> 00:27:39,919
other people believe or sort of like why

711
00:27:38,320 --> 00:27:41,760
they why they think a certain way and

712
00:27:39,919 --> 00:27:44,559
trying to accommodate that is basically

713
00:27:41,760 --> 00:27:46,080
for all intents and purposes empathy um

714
00:27:44,559 --> 00:27:48,399
but

715
00:27:46,080 --> 00:27:50,559
while it may be good

716
00:27:48,399 --> 00:27:52,720
from a community gardening perspective

717
00:27:50,559 --> 00:27:55,279
or even facilitating conversations

718
00:27:52,720 --> 00:27:58,399
perspective the real value of it is

719
00:27:55,279 --> 00:27:58,399
actually for you

720
00:27:58,960 --> 00:28:03,440
um and i'm going to frame it like this

721
00:28:00,960 --> 00:28:04,960
let's say you had two systems in a

722
00:28:03,440 --> 00:28:06,880
company right your company had two

723
00:28:04,960 --> 00:28:09,200
servers and only one of them was

724
00:28:06,880 --> 00:28:10,159
publishing logs to your log indexer of

725
00:28:09,200 --> 00:28:14,000
choice

726
00:28:10,159 --> 00:28:14,000
splunk sumo logic what have you

727
00:28:14,240 --> 00:28:19,840
it is entirely possible for someone to

728
00:28:17,039 --> 00:28:21,279
come in to the company and come to the

729
00:28:19,840 --> 00:28:22,880
conclusion

730
00:28:21,279 --> 00:28:24,720
that

731
00:28:22,880 --> 00:28:25,760
the only system that exists is the one

732
00:28:24,720 --> 00:28:28,840
that's

733
00:28:25,760 --> 00:28:33,279
outputting the information

734
00:28:28,840 --> 00:28:33,279
right it's only that one system

735
00:28:34,159 --> 00:28:37,200
now i'm gonna say something a little bit

736
00:28:35,520 --> 00:28:39,520
uncomfortable um

737
00:28:37,200 --> 00:28:41,440
there there's in very much the same way

738
00:28:39,520 --> 00:28:43,679
there's a there's a very fundamental

739
00:28:41,440 --> 00:28:45,840
self-centeredness that comes with being

740
00:28:43,679 --> 00:28:45,840
alive

741
00:28:46,240 --> 00:28:49,840
if you think about it just actually

742
00:28:48,240 --> 00:28:52,320
think about it

743
00:28:49,840 --> 00:28:53,679
this talk is happening at your ears

744
00:28:52,320 --> 00:28:57,200
going through your headphones being

745
00:28:53,679 --> 00:28:59,840
parts per your brain seen by your eyes

746
00:28:57,200 --> 00:28:59,840
and

747
00:29:01,600 --> 00:29:05,679
if we're not careful the default

748
00:29:03,600 --> 00:29:07,760
assumption is that

749
00:29:05,679 --> 00:29:11,039
that that we we would derive from that

750
00:29:07,760 --> 00:29:13,840
is everything is all about me

751
00:29:11,039 --> 00:29:15,760
which seems innocuous and not that not

752
00:29:13,840 --> 00:29:18,880
that critical but let's

753
00:29:15,760 --> 00:29:20,880
frame it in real practical terms

754
00:29:18,880 --> 00:29:22,640
right um within the context of modern

755
00:29:20,880 --> 00:29:24,480
software development life let's say

756
00:29:22,640 --> 00:29:28,399
you're reasonably

757
00:29:24,480 --> 00:29:30,320
successful um ops person in a company

758
00:29:28,399 --> 00:29:32,640
and you know you're tired from the night

759
00:29:30,320 --> 00:29:34,720
before because you were working late for

760
00:29:32,640 --> 00:29:36,880
some reason that you can't even remember

761
00:29:34,720 --> 00:29:40,760
so you know you wake up at a respectable

762
00:29:36,880 --> 00:29:40,760
time let's say seven o'clock

763
00:29:41,600 --> 00:29:46,960
your phone rings

764
00:29:42,960 --> 00:29:48,720
and there's an alert on your pager duty

765
00:29:46,960 --> 00:29:51,279
and it's coming from a system that you

766
00:29:48,720 --> 00:29:52,559
haven't heard of before

767
00:29:51,279 --> 00:29:54,720
and you come to the conclusion

768
00:29:52,559 --> 00:29:56,880
immediately that it's probably a legacy

769
00:29:54,720 --> 00:29:59,520
system and like all

770
00:29:56,880 --> 00:30:02,320
of course like all legacy systems the

771
00:29:59,520 --> 00:30:04,320
alert doesn't specify any means of

772
00:30:02,320 --> 00:30:06,480
identifying where the problem is or

773
00:30:04,320 --> 00:30:08,799
where the documentation is so you say

774
00:30:06,480 --> 00:30:10,640
you have your coffee

775
00:30:08,799 --> 00:30:12,960
you prepare and then you sit down and

776
00:30:10,640 --> 00:30:14,640
you try to find the repository where it

777
00:30:12,960 --> 00:30:16,399
is and of course

778
00:30:14,640 --> 00:30:18,799
it's um

779
00:30:16,399 --> 00:30:20,320
the last commit was three years ago

780
00:30:18,799 --> 00:30:21,760
and the tests aren't there and it's

781
00:30:20,320 --> 00:30:24,159
written in a language that kind of

782
00:30:21,760 --> 00:30:27,279
annoys you by default so

783
00:30:24,159 --> 00:30:27,279
you try and fix it anyway

784
00:30:27,919 --> 00:30:32,880
nine o'clock comes in and your manager

785
00:30:30,559 --> 00:30:35,520
messages you images immediately on slack

786
00:30:32,880 --> 00:30:37,679
and they say hey you know i i saw that

787
00:30:35,520 --> 00:30:39,520
you were working late last night i think

788
00:30:37,679 --> 00:30:41,679
i'm gonna give you like a early day

789
00:30:39,520 --> 00:30:45,039
today you should look after yourself and

790
00:30:41,679 --> 00:30:45,039
say yeah that's cool that's cool

791
00:30:46,000 --> 00:30:49,279
and then they say hey what are you doing

792
00:30:47,760 --> 00:30:50,880
so you try to explain it and now you

793
00:30:49,279 --> 00:30:53,120
have to take the time away from trying

794
00:30:50,880 --> 00:30:54,640
to fix the problem to try to explain it

795
00:30:53,120 --> 00:30:56,880
to someone who probably can't do

796
00:30:54,640 --> 00:30:58,480
anything about the problem space and

797
00:30:56,880 --> 00:31:00,799
it's a little bit annoying but you do it

798
00:30:58,480 --> 00:31:00,799
anyway

799
00:31:00,960 --> 00:31:04,080
and then your manager says oh it's

800
00:31:02,720 --> 00:31:05,840
really great that you're working on this

801
00:31:04,080 --> 00:31:07,679
problem but

802
00:31:05,840 --> 00:31:11,039
we have a couple of cards that need to

803
00:31:07,679 --> 00:31:12,480
be delivered by the end of the week

804
00:31:11,039 --> 00:31:15,200
all right

805
00:31:12,480 --> 00:31:18,159
so you say hey is it a deadline

806
00:31:15,200 --> 00:31:21,200
and your manager says oh no um it's a

807
00:31:18,159 --> 00:31:21,200
but we really need it

808
00:31:21,679 --> 00:31:26,799
so now you're kind of salty that

809
00:31:24,480 --> 00:31:28,960
your manager is giving you a day off but

810
00:31:26,799 --> 00:31:31,279
at the same time asking for something to

811
00:31:28,960 --> 00:31:32,799
be delivered that you need extra hours

812
00:31:31,279 --> 00:31:35,360
to do but

813
00:31:32,799 --> 00:31:36,960
you don't say that of course

814
00:31:35,360 --> 00:31:39,760
and then you proceed the rest of your

815
00:31:36,960 --> 00:31:41,279
day and you finally figure out the uh

816
00:31:39,760 --> 00:31:42,640
the cause of the problem in its

817
00:31:41,279 --> 00:31:43,919
afternoon

818
00:31:42,640 --> 00:31:46,720
and um

819
00:31:43,919 --> 00:31:49,360
you know the card is assigned to you and

820
00:31:46,720 --> 00:31:51,279
you feel some sort of indebtedness to

821
00:31:49,360 --> 00:31:53,360
your teammates so you decide to work on

822
00:31:51,279 --> 00:31:55,279
it and maybe maybe just this one time

823
00:31:53,360 --> 00:31:56,399
i'll do one extra hour instead of going

824
00:31:55,279 --> 00:31:58,640
late

825
00:31:56,399 --> 00:32:00,080
but that doesn't happen

826
00:31:58,640 --> 00:32:02,399
and by the time you look at it it's

827
00:32:00,080 --> 00:32:04,240
already like 9 p.m

828
00:32:02,399 --> 00:32:06,000
and when you go to sleep

829
00:32:04,240 --> 00:32:09,760
it's

830
00:32:06,000 --> 00:32:12,080
your brain's still on so you can't sleep

831
00:32:09,760 --> 00:32:14,080
which leaves you more tired the next day

832
00:32:12,080 --> 00:32:17,039
and this happens again and again and

833
00:32:14,080 --> 00:32:20,080
again and again and within the lengths

834
00:32:17,039 --> 00:32:22,559
of self the lens of us

835
00:32:20,080 --> 00:32:25,440
by default by default having all those

836
00:32:22,559 --> 00:32:27,519
inputs only pertaining to us it is not

837
00:32:25,440 --> 00:32:30,720
impossible in fact it is blameless to

838
00:32:27,519 --> 00:32:33,120
think that hey you know about how deeply

839
00:32:30,720 --> 00:32:35,600
unfair it all is and how hurtful and

840
00:32:33,120 --> 00:32:38,000
tiring and how exhausting it is

841
00:32:35,600 --> 00:32:39,679
the things that are happening right now

842
00:32:38,000 --> 00:32:43,039
right

843
00:32:39,679 --> 00:32:44,559
every single day

844
00:32:43,039 --> 00:32:46,320
and i'm going to propose a different

845
00:32:44,559 --> 00:32:48,720
frame on that that doesn't come with

846
00:32:46,320 --> 00:32:50,960
that default the frame that comes around

847
00:32:48,720 --> 00:32:52,960
interrogating other people's stacks

848
00:32:50,960 --> 00:32:54,320
because it is entirely possible to think

849
00:32:52,960 --> 00:32:56,480
that hey

850
00:32:54,320 --> 00:32:59,120
the person who wrote those

851
00:32:56,480 --> 00:33:00,720
that that that particular alert or um

852
00:32:59,120 --> 00:33:02,000
the particular documentation that

853
00:33:00,720 --> 00:33:04,159
existed

854
00:33:02,000 --> 00:33:06,799
probably was under duress more

855
00:33:04,159 --> 00:33:08,640
significantly than you are and just did

856
00:33:06,799 --> 00:33:10,880
everything that they could with the

857
00:33:08,640 --> 00:33:11,679
information that they had during the

858
00:33:10,880 --> 00:33:14,320
time

859
00:33:11,679 --> 00:33:16,480
right the technology that existed three

860
00:33:14,320 --> 00:33:17,840
years ago and maybe your manager is just

861
00:33:16,480 --> 00:33:20,080
kind of like

862
00:33:17,840 --> 00:33:22,840
really awkward at navigating that space

863
00:33:20,080 --> 00:33:25,360
of reporting to shareholders and

864
00:33:22,840 --> 00:33:27,840
generating capital but at the same time

865
00:33:25,360 --> 00:33:29,679
really caring about you as a person

866
00:33:27,840 --> 00:33:32,159
and it's a little bit weird but you know

867
00:33:29,679 --> 00:33:34,960
fundamentally they really care

868
00:33:32,159 --> 00:33:36,960
or maybe it's a choice of thinking that

869
00:33:34,960 --> 00:33:39,600
hey um by

870
00:33:36,960 --> 00:33:43,039
by working late nights maybe i'm

871
00:33:39,600 --> 00:33:45,600
presenting a standard or a baseline that

872
00:33:43,039 --> 00:33:48,000
not everyone in the team is able to meet

873
00:33:45,600 --> 00:33:50,159
because they have real life

874
00:33:48,000 --> 00:33:53,600
obligations that they can't steer away

875
00:33:50,159 --> 00:33:55,919
from and maybe i shouldn't be doing this

876
00:33:53,600 --> 00:33:55,919
all right

877
00:33:57,440 --> 00:34:00,559
now

878
00:33:58,159 --> 00:34:02,240
none of that is maybe true it's entirely

879
00:34:00,559 --> 00:34:03,600
possible that your manager is just

880
00:34:02,240 --> 00:34:04,559
annoying

881
00:34:03,600 --> 00:34:06,320
but

882
00:34:04,559 --> 00:34:09,119
the only thing that's true is you get to

883
00:34:06,320 --> 00:34:11,119
make a choice on what by default to

884
00:34:09,119 --> 00:34:13,200
think about

885
00:34:11,119 --> 00:34:15,119
right

886
00:34:13,200 --> 00:34:16,720
and

887
00:34:15,119 --> 00:34:19,119
i want to take a step back here because

888
00:34:16,720 --> 00:34:21,040
i'm not moralizing and this is not i'm

889
00:34:19,119 --> 00:34:23,520
not the wise old fish or anything like

890
00:34:21,040 --> 00:34:26,480
that it's this is not coming from a

891
00:34:23,520 --> 00:34:28,960
space where i would like you to do it

892
00:34:26,480 --> 00:34:30,960
because it's good um

893
00:34:28,960 --> 00:34:33,520
this is

894
00:34:30,960 --> 00:34:35,919
because because a lot of times i

895
00:34:33,520 --> 00:34:39,440
actually forget to do this like and some

896
00:34:35,919 --> 00:34:39,440
days i actually don't want to

897
00:34:40,079 --> 00:34:44,079
but maybe just by the virtue of the

898
00:34:42,320 --> 00:34:46,000
awareness that there is a choice

899
00:34:44,079 --> 00:34:48,560
sometimes if you have the capacity for

900
00:34:46,000 --> 00:34:51,679
it the choice sometimes exists to

901
00:34:48,560 --> 00:34:54,159
interrogate other people's stacks

902
00:34:51,679 --> 00:34:55,919
right and to change that default frame

903
00:34:54,159 --> 00:34:56,800
by which we view

904
00:34:55,919 --> 00:34:59,119
um

905
00:34:56,800 --> 00:35:01,760
the outputs the experiences and the

906
00:34:59,119 --> 00:35:04,240
underlying values that kind of exist

907
00:35:01,760 --> 00:35:04,240
out there

908
00:35:05,280 --> 00:35:08,720
maybe

909
00:35:06,560 --> 00:35:11,599
that's more

910
00:35:08,720 --> 00:35:13,440
kind to us as human beings

911
00:35:11,599 --> 00:35:15,200
and maybe it's critical not from a

912
00:35:13,440 --> 00:35:17,920
software development context from a

913
00:35:15,200 --> 00:35:19,119
productivity or not even

914
00:35:17,920 --> 00:35:19,920
from

915
00:35:19,119 --> 00:35:22,160
a

916
00:35:19,920 --> 00:35:24,240
community kind of point of view but just

917
00:35:22,160 --> 00:35:27,440
us

918
00:35:24,240 --> 00:35:31,040
us people being to navigate the trenches

919
00:35:27,440 --> 00:35:32,480
of day-to-day life

920
00:35:31,040 --> 00:35:35,200
thank you so much these are the

921
00:35:32,480 --> 00:35:38,160
references um i'd love

922
00:35:35,200 --> 00:35:41,040
um i'm i'm yeah so that's that's all i

923
00:35:38,160 --> 00:35:42,560
have i i hope

924
00:35:41,040 --> 00:35:44,720
there was a set of things that i wanted

925
00:35:42,560 --> 00:35:47,040
to say and i hope that got through

926
00:35:44,720 --> 00:35:47,040
thank you

927
00:35:48,079 --> 00:35:51,280
hey john thank you so much for your talk

928
00:35:49,680 --> 00:35:54,160
there's so many amazing things in there

929
00:35:51,280 --> 00:35:55,760
that i went ouch oh i'm doing that i've

930
00:35:54,160 --> 00:35:57,599
stopped doing that i need to start doing

931
00:35:55,760 --> 00:35:59,200
that so thank you very much

932
00:35:57,599 --> 00:36:02,320
we did have a question to come through

933
00:35:59,200 --> 00:36:05,359
in the chat um is there a public example

934
00:36:02,320 --> 00:36:06,560
of your sensible default repo

935
00:36:05,359 --> 00:36:09,040
or similar

936
00:36:06,560 --> 00:36:10,560
anywhere you are aware of

937
00:36:09,040 --> 00:36:13,359
um

938
00:36:10,560 --> 00:36:15,520
no not quite um the um i can generate

939
00:36:13,359 --> 00:36:18,160
one actually it's um

940
00:36:15,520 --> 00:36:20,560
the the value of the repo isn't it's in

941
00:36:18,160 --> 00:36:23,280
the contents of the wrapper itself um as

942
00:36:20,560 --> 00:36:26,560
much as it's being able to relay to

943
00:36:23,280 --> 00:36:28,720
people that there is a way um to surface

944
00:36:26,560 --> 00:36:29,760
things that you really care about and

945
00:36:28,720 --> 00:36:32,160
have them

946
00:36:29,760 --> 00:36:34,480
be known across an organization and have

947
00:36:32,160 --> 00:36:37,280
it have impact instead of it just living

948
00:36:34,480 --> 00:36:37,280
in our own heads

949
00:36:37,920 --> 00:36:42,880
so um but i will post a link so yeah

950
00:36:40,720 --> 00:36:45,440
excellent thank you john one of my key

951
00:36:42,880 --> 00:36:47,040
takeaways from all these talks is that

952
00:36:45,440 --> 00:36:49,520
we're all still people

953
00:36:47,040 --> 00:36:51,359
if ai really did exist we wouldn't need

954
00:36:49,520 --> 00:36:53,119
a conference for humans we could just

955
00:36:51,359 --> 00:36:54,640
put the computers together and hey isn't

956
00:36:53,119 --> 00:36:57,040
that the matrix oops sorry cross

957
00:36:54,640 --> 00:36:58,720
promotion there but yes we're people and

958
00:36:57,040 --> 00:37:01,119
we need to remember that um everyone

959
00:36:58,720 --> 00:37:02,640
around us is still people

960
00:37:01,119 --> 00:37:05,359
oh we've got a question tell us about

961
00:37:02,640 --> 00:37:06,480
the guitars

962
00:37:05,359 --> 00:37:08,640
okay

963
00:37:06,480 --> 00:37:10,720
um you know what i love talking about

964
00:37:08,640 --> 00:37:10,720
this

965
00:37:11,119 --> 00:37:16,480
so so this is actually my my side hustle

966
00:37:13,200 --> 00:37:19,520
which is creating weird hipster you know

967
00:37:16,480 --> 00:37:23,280
monstrosities from reclaimed wood um so

968
00:37:19,520 --> 00:37:24,880
this is a franken caster um so yeah and

969
00:37:23,280 --> 00:37:27,200
a lot of them have been modified

970
00:37:24,880 --> 00:37:28,560
slightly so yeah

971
00:37:27,200 --> 00:37:29,920
amazing what's the timber you've

972
00:37:28,560 --> 00:37:31,760
reclaimed

973
00:37:29,920 --> 00:37:34,480
um it's uh

974
00:37:31,760 --> 00:37:36,880
sycamore um i believe

975
00:37:34,480 --> 00:37:40,240
it's the original designation not really

976
00:37:36,880 --> 00:37:43,280
the best um for um woods but it looked

977
00:37:40,240 --> 00:37:45,040
awesome so aesthetics function i don't

978
00:37:43,280 --> 00:37:46,640
know

979
00:37:45,040 --> 00:37:48,560
excellent maybe you'll maybe it'll end

980
00:37:46,640 --> 00:37:50,400
up on a movie set somewhere where it

981
00:37:48,560 --> 00:37:51,920
looks really good but the actual

982
00:37:50,400 --> 00:37:54,640
act is not playing it and then it's a

983
00:37:51,920 --> 00:37:56,880
different uh riff behind it excellent

984
00:37:54,640 --> 00:37:58,400
we've got about another five minutes if

985
00:37:56,880 --> 00:37:59,839
anyone's got another question they

986
00:37:58,400 --> 00:38:01,300
wanted to ask

987
00:37:59,839 --> 00:38:03,119
yeah absolutely um

988
00:38:01,300 --> 00:38:04,800
[Laughter]

989
00:38:03,119 --> 00:38:07,200
the um

990
00:38:04,800 --> 00:38:09,599
that is the gnl um guitar at the back as

991
00:38:07,200 --> 00:38:12,960
well um to answer um tom eastman thank

992
00:38:09,599 --> 00:38:15,040
you so much um yeah so um

993
00:38:12,960 --> 00:38:19,240
plays a song

994
00:38:15,040 --> 00:38:19,240
i'm so nervous right now

995
00:38:19,760 --> 00:38:24,720
it's so my fingers aren't quite up to

996
00:38:21,839 --> 00:38:26,240
the task but but thank you thank you

997
00:38:24,720 --> 00:38:28,960
excellent

998
00:38:26,240 --> 00:38:31,119
i've only just seen two acrylic guitars

999
00:38:28,960 --> 00:38:32,640
on a camera bidding site that i've sent

1000
00:38:31,119 --> 00:38:34,320
across to a friend who plays the guitar

1001
00:38:32,640 --> 00:38:35,839
saying you need both of these but it

1002
00:38:34,320 --> 00:38:38,560
looks really weird that the clear

1003
00:38:35,839 --> 00:38:40,800
acrylic with just the strings in the air

1004
00:38:38,560 --> 00:38:42,240
yeah i know right but um yeah it doesn't

1005
00:38:40,800 --> 00:38:44,480
look quite right but apparently they

1006
00:38:42,240 --> 00:38:45,680
sound the same so it's okay

1007
00:38:44,480 --> 00:38:48,240
they also have the same advice i'm

1008
00:38:45,680 --> 00:38:51,359
holding them in my hands bad

1009
00:38:48,240 --> 00:38:52,960
awesome hell yeah

1010
00:38:51,359 --> 00:38:55,040
we don't have any more questions at this

1011
00:38:52,960 --> 00:38:59,119
point so i i think we should start a

1012
00:38:55,040 --> 00:38:59,119
poll for what do you want him to play

1013
00:38:59,599 --> 00:39:02,320
um

1014
00:39:00,400 --> 00:39:05,520
unfortunately all my guitars have uh

1015
00:39:02,320 --> 00:39:08,320
weird tunings um so

1016
00:39:05,520 --> 00:39:08,320
yeah the

1017
00:39:12,640 --> 00:39:16,960
so this was this was like a weird

1018
00:39:14,960 --> 00:39:19,359
project guitar that i i made which is a

1019
00:39:16,960 --> 00:39:21,440
woody guthrie um reference by the way

1020
00:39:19,359 --> 00:39:25,280
like this sticker um he was a folk

1021
00:39:21,440 --> 00:39:27,359
singer in 1945 sue sang about um uh what

1022
00:39:25,280 --> 00:39:29,760
he called us the the the struggles of

1023
00:39:27,359 --> 00:39:31,599
like people um back in the day and stuff

1024
00:39:29,760 --> 00:39:33,359
like i was really into folk during the

1025
00:39:31,599 --> 00:39:35,520
time and that's why it looks like that

1026
00:39:33,359 --> 00:39:36,320
and um yeah

1027
00:39:35,520 --> 00:39:37,920
so

1028
00:39:36,320 --> 00:39:40,160
yeah

1029
00:39:37,920 --> 00:39:41,760
but that's all i have sorry

1030
00:39:40,160 --> 00:39:43,680
that's all right thank you johnny would

1031
00:39:41,760 --> 00:39:45,280
put you on the spot there yeah don't

1032
00:39:43,680 --> 00:39:46,720
worry it's all good excellent thank you

1033
00:39:45,280 --> 00:39:48,720
for your amazing talk this afternoon

1034
00:39:46,720 --> 00:39:51,040
john is available too in the post

1035
00:39:48,720 --> 00:39:52,960
conference chat if uh john maybe you can

1036
00:39:51,040 --> 00:39:54,720
convince him to play over there if he's

1037
00:39:52,960 --> 00:39:55,760
not gonna play here maybe he'll play in

1038
00:39:54,720 --> 00:39:57,440
the chat

1039
00:39:55,760 --> 00:39:58,800
but yeah thanks john for joining thanks

1040
00:39:57,440 --> 00:40:00,000
everybody i will now have a room

1041
00:39:58,800 --> 00:40:00,960
changeover and we'll be back very

1042
00:40:00,000 --> 00:40:04,839
shortly

1043
00:40:00,960 --> 00:40:04,839
bye for now have a good one