WEBVTT

1
00:00:07.759 --> 00:00:11.519
Hey everybody, thanks for coming to
another episode of My Angular Story. I'm

2
00:00:11.560 --> 00:00:16.120
your host Aaron Frost, and today
as a guest, we've got David Cooper.

3
00:00:16.440 --> 00:00:20.399
David, go ahead and say hi, Hey everybody. We've got so

4
00:00:20.519 --> 00:00:24.280
Dave. You're you. You're in
London, but you sound like you're Australian.

5
00:00:26.359 --> 00:00:29.640
Yeah, there's a little bit of
an accent still there. I moved

6
00:00:29.640 --> 00:00:34.880
to London about four years ago and
yep, I'm slowly losing that accent,

7
00:00:35.840 --> 00:00:39.119
which, yeah, it's a bit
heartbreaking. Yeah, you don't want to

8
00:00:39.119 --> 00:00:44.840
lose you don't want to lose your
accent. No, I'm sure I'm due

9
00:00:44.880 --> 00:00:47.640
to go out there in April.
I'm sure i'll get it back pretty quickly.

10
00:00:48.079 --> 00:00:51.799
Yeah, it should. I'm imagining
you'll just like roll right into it.

11
00:00:53.719 --> 00:00:58.439
Yeah. This episode is sponsored by
Century dot Io. Recently I came

12
00:00:58.479 --> 00:01:02.000
across a great tool for tracking monitoring
problems in my apps. Then I asked

13
00:01:02.039 --> 00:01:03.799
them if they wanted to sponsor the
show and allow me to share my experience

14
00:01:03.799 --> 00:01:07.480
with you. Century provides a terrific
interface for keeping track of what's going on

15
00:01:07.519 --> 00:01:11.079
with my app. It also tracks
releases so I can tell if what I

16
00:01:11.120 --> 00:01:14.760
deployed makes things better or worse.
They give full stack traces and as much

17
00:01:14.760 --> 00:01:18.400
information as possible about the situation when
the error occurred to help you track down

18
00:01:18.439 --> 00:01:22.079
the errors. Plus one thing I
love, you can customize the context provided

19
00:01:22.120 --> 00:01:25.840
by Century, so if you're looking
for specific information about the request, you

20
00:01:25.879 --> 00:01:29.760
can provide it. It automatically scrubs
passwords and secure information, and you can

21
00:01:29.799 --> 00:01:33.719
customize the scrubbing as well. Finally, it has a user feedback system built

22
00:01:33.719 --> 00:01:36.560
in that you can use to get
information from your users. Oh and I

23
00:01:36.560 --> 00:01:38.959
also love that they support open source
to the point where they actually open source

24
00:01:40.120 --> 00:01:42.840
centry. If you want to self
host it, use the code dev chat

25
00:01:42.920 --> 00:01:47.560
at century dot io to get two
months free on Century small plan. That's

26
00:01:47.680 --> 00:01:53.439
code dev chat at century dot io. So I speak Spanish, and I

27
00:01:53.560 --> 00:01:57.799
kind of I'm like this weird.
I kind of adopt the accident of whatever

28
00:01:57.879 --> 00:02:02.000
country I'm in. So, if
I'm in Mexico, and here's the one

29
00:02:02.040 --> 00:02:06.680
thing I always speak with like Mexican
slang terms, because that's where I learned

30
00:02:06.719 --> 00:02:08.680
was when I lived in Mexico.
Yep. But if I go to if

31
00:02:08.719 --> 00:02:13.800
I'm speaking with people from like Columbia
or Argentina, I just kind of adopt

32
00:02:13.840 --> 00:02:15.719
their accidents. So it's kind of
I kind of feel you on that front.

33
00:02:16.120 --> 00:02:21.000
You know. It's it's a very
cool thing how that actually works.

34
00:02:21.080 --> 00:02:24.599
But it's also very annoying because whenever
I talk to anyone from back home,

35
00:02:24.639 --> 00:02:28.560
they're like, oh, you sound
English now, and I'm like, that's

36
00:02:28.599 --> 00:02:34.240
the first thing that everyone says.
Yeah, yeah, So I when I

37
00:02:34.319 --> 00:02:37.319
lived in Mexico, people when I
came home. I lived there for two

38
00:02:37.360 --> 00:02:39.639
years. When I came home,
people were like, dude, you speak

39
00:02:39.680 --> 00:02:45.639
English with like like, you sound
like a Latino, but I definitely don't

40
00:02:45.639 --> 00:02:49.639
look Latino, and so people people
thought that was funny. But yeah,

41
00:02:49.840 --> 00:02:52.000
I know how you feel, man, I felt it. I felt it

42
00:02:52.039 --> 00:02:55.680
before. So dig you're you're an
Angular developer. That's why we're on the

43
00:02:55.680 --> 00:03:00.759
podcast. Yep, how long you've
been working with Angler? So I've been

44
00:03:00.800 --> 00:03:05.639
working with Anguila for a little while
now. I guess the first time that

45
00:03:05.719 --> 00:03:08.439
I was sort of introduced to it
was a really long time ago. I'm

46
00:03:08.439 --> 00:03:12.719
not sure what version of it would
have been, but it was when I

47
00:03:12.759 --> 00:03:15.520
was at my second job, so
it might have been like seven years ago

48
00:03:15.639 --> 00:03:20.680
or something like that. Back back
in Australia. Yeah, yeah, back

49
00:03:20.719 --> 00:03:24.319
in Perth in Australia, and I
was working an Internet services provider and one

50
00:03:24.319 --> 00:03:30.879
of the one of the guys there
had started building like a sort of like

51
00:03:30.919 --> 00:03:34.759
a c I CD server back before
well when when I guess, when the

52
00:03:34.800 --> 00:03:38.520
only thing available was probably Jenkins or
whatever that sort of people had heard of

53
00:03:38.639 --> 00:03:43.879
or years and he'd started and it
was like back when like people were making

54
00:03:43.919 --> 00:03:49.800
the switch from like SPN or CBS
to GET and he'd started building a front

55
00:03:49.919 --> 00:03:53.919
end for it. And you know, back I think we were using jQuery

56
00:03:53.000 --> 00:04:00.599
mainly, or maybe not even jQuery, and he showed everyone this being this

57
00:04:00.680 --> 00:04:04.039
thing angular and it was talking about
two way binding and all of this stuff,

58
00:04:04.080 --> 00:04:09.759
and everyone's like minds were blown,
and I guess like back then it

59
00:04:09.800 --> 00:04:14.280
was just some sort of like magical
black box. And then I sort of

60
00:04:14.360 --> 00:04:18.560
I tried understanding that and tried this
is like I was still pretty new to

61
00:04:18.600 --> 00:04:23.680
web development in general then, so
a lot of it was like magical and

62
00:04:24.000 --> 00:04:27.120
didn't make a hell of a lot
of sense to me. And then when

63
00:04:27.160 --> 00:04:30.959
I got my next job, I
oh, maybe it was a job after

64
00:04:30.000 --> 00:04:34.399
that, I can't quite remember.
I moved to Sydney, and I remember

65
00:04:35.360 --> 00:04:39.319
the job. The job ad was
sort of talking about, you know,

66
00:04:39.720 --> 00:04:43.959
you need angular JAS experience. I
didn't really have that much angular Jas experience,

67
00:04:44.040 --> 00:04:47.720
so I remember. I remember I
flew into Sydney the day before the

68
00:04:47.759 --> 00:04:53.120
interview and I caught up with a
friend and I thought, it's all right,

69
00:04:53.199 --> 00:04:57.480
I'll go and have some drinks with
my friend and back in the hotel

70
00:04:57.560 --> 00:05:00.959
room, I'll just quickly whip up
a little a little world, and I'm

71
00:05:00.000 --> 00:05:03.759
sure that I can I can get
my way through this interview. And ended

72
00:05:03.839 --> 00:05:10.759
up having about ten too many drinks
and sort of drunkenly coding some stuff up

73
00:05:10.759 --> 00:05:15.800
in my hotel room that night before
the interview. And it turned out that

74
00:05:15.879 --> 00:05:20.079
the thing that i'd built whilst in
the state I was in was almost identical

75
00:05:20.160 --> 00:05:24.160
to the question that they like,
the sort of tech tests that they'd given

76
00:05:24.160 --> 00:05:26.680
me in the interview. It was
like a little little thing where you put

77
00:05:26.720 --> 00:05:30.240
in a GitHub user name and it
would like render out like some statistics about

78
00:05:30.279 --> 00:05:34.199
a GitHub account or whatever. So
it was one of the luckiest and most

79
00:05:34.279 --> 00:05:38.959
ridiculous things that I think I've encountered
in my in my career, but it

80
00:05:39.439 --> 00:05:43.600
paid off. And ever since then, I guess I've loved it. I

81
00:05:43.639 --> 00:05:46.199
mean I've sort of dabbled with pretty
much all of this. I'm guessing you

82
00:05:46.279 --> 00:05:50.480
got the job. Yeah, yeah
I did. So. Yeah, you're

83
00:05:50.519 --> 00:05:57.560
just at home messing around with this
thing, and you just happened to demo

84
00:05:57.720 --> 00:06:00.920
up what they were about to ask
you the next in your interviews. So

85
00:06:00.360 --> 00:06:03.439
it sounds like you probably killed your
interview like you did ask them. Yeah,

86
00:06:03.519 --> 00:06:06.439
yeah, I remember they they sort
of gave me this question. I

87
00:06:06.480 --> 00:06:10.240
think they I think they're gonna quite
a long time, but I think the

88
00:06:10.279 --> 00:06:12.560
guys that asked me the question,
they sort of said, all right,

89
00:06:12.560 --> 00:06:15.399
we'll come back in a couple of
hours and see what you see what you

90
00:06:15.439 --> 00:06:17.680
can do. And I remember messaging
my mate that I was out with the

91
00:06:17.759 --> 00:06:21.360
night before, being like, you
never guess what just happened. So yeah,

92
00:06:21.360 --> 00:06:24.959
so I knowed that that was.
That was really cool. That was

93
00:06:25.120 --> 00:06:28.279
That was a really eye opening experience. Actually that job, it was all

94
00:06:28.319 --> 00:06:31.800
sorts of crazy stuff. Having to
that was sort of like my first Angular

95
00:06:31.879 --> 00:06:36.680
job. But also I had to
I had to write very performance code there

96
00:06:38.079 --> 00:06:40.480
for the for the job that I
was doing, So that was really cool.

97
00:06:40.959 --> 00:06:43.920
A bit of a bit of a
sort of jump in the deep ense

98
00:06:43.920 --> 00:06:47.120
sort of experience, right right,
right? So, uh huh, that's

99
00:06:47.160 --> 00:06:54.600
interesting. I don't think I've ever
had that happen where I was like perfectly

100
00:06:54.639 --> 00:07:01.839
prepared for the interview. Yeah,
it's never happened to me since. So,

101
00:07:01.839 --> 00:07:04.519
so how long did it I'm guessing
it didn't take you the two hours

102
00:07:04.680 --> 00:07:08.399
or did it take you to No. I just I just smashed it out.

103
00:07:08.439 --> 00:07:12.279
I think at the very beginning I
said to that, I said to

104
00:07:12.319 --> 00:07:15.240
them that I'd done something very similar
the night before, and I think I

105
00:07:15.319 --> 00:07:17.959
demoed it off to them and then
they sort of just left me to it

106
00:07:18.040 --> 00:07:21.079
to sort of polish it up,
and I just had to to refactor some

107
00:07:21.120 --> 00:07:26.920
things and tweak some things. Huh. That's pretty cool. Yeah, it

108
00:07:26.920 --> 00:07:30.360
worked out pretty good. Yeah,
that's awesome. That's so funny. I

109
00:07:30.439 --> 00:07:32.800
wonder how many of the listeners have
had that happen to me before. I

110
00:07:32.879 --> 00:07:36.720
mean, I know plenty of them
will have been in the scenario that I've

111
00:07:36.759 --> 00:07:41.839
been in, which is I didn't
nail the interview, like I totally mess

112
00:07:41.879 --> 00:07:46.600
it up. But I'm sure I'm
sure others have. I have experienced something

113
00:07:46.839 --> 00:07:49.480
a bit a bit more like you, So i'd be interested. Tweet at

114
00:07:49.560 --> 00:07:51.600
us. I want to hear about
it. Yeah, I definitely want to

115
00:07:51.600 --> 00:07:56.959
hear about it. If you ever
nailed your interview because you practiced something the

116
00:07:57.079 --> 00:08:00.160
night before the exact thing they about
to ask you, I guess, yes,

117
00:08:00.759 --> 00:08:05.199
I guess tweet out at me.
I want to hear so. So

118
00:08:05.319 --> 00:08:09.800
yeah, all right, so you
started seven years ago. It sounds like

119
00:08:09.839 --> 00:08:13.040
six years ago you started bugger around
with either and you're still using it.

120
00:08:15.040 --> 00:08:16.680
Yeah, So I use I use
a few different things. I guess in

121
00:08:16.759 --> 00:08:22.360
my day to day job, like
where I'm currently working, there's there's a

122
00:08:22.360 --> 00:08:26.600
little bit of everything floating around there. Like I've been at this job for

123
00:08:26.639 --> 00:08:28.480
about three years now, and when
I started, there's actually quite a lot

124
00:08:28.519 --> 00:08:33.440
of angular jas still floating around.
And it was actually quite interesting because that

125
00:08:33.559 --> 00:08:39.600
year I went to an Angular connect
and I remember during the keynote, I

126
00:08:39.600 --> 00:08:41.360
can't remember who was doing the keynote
that year, but there was sort of

127
00:08:41.399 --> 00:08:45.639
like talking about I don't know why, version of it might have been just

128
00:08:45.679 --> 00:08:48.639
when Angular two just came out,
and they were talking about like, you

129
00:08:48.639 --> 00:08:52.679
know, everyone's thinking that, everyone
the crowd's thinking, Yeah, Okay,

130
00:08:52.720 --> 00:08:56.600
well, these Google guys, they
must be all using the latest and greatest,

131
00:08:56.600 --> 00:08:58.600
and I think at the time they
still had about seventy five percent Angular

132
00:08:58.679 --> 00:09:03.480
JA in the code bases and sort
of talking about their plans to migrate across

133
00:09:05.000 --> 00:09:07.559
and so that was like it was
quite interesting, like hearing about that and

134
00:09:07.600 --> 00:09:11.399
then seeing what was happening in my
work. And then over time we've we've

135
00:09:11.440 --> 00:09:16.879
refactored a lot of applications, either
to the latest version of Angular or going

136
00:09:16.879 --> 00:09:22.919
from angular JAS to Angular or maybe
something's moved across to React. Yeah.

137
00:09:24.039 --> 00:09:26.919
Yeah, I don't know if you
have to censor out anytime someone says react

138
00:09:26.919 --> 00:09:33.240
on this podcast, or they didn't
just yeah, I think you said the

139
00:09:33.399 --> 00:09:35.799
word, then they don't know what
happened. Yeah, it's probably preferable to

140
00:09:35.799 --> 00:09:43.080
say the F word over that accident. We're going to believe that both excellent

141
00:09:43.840 --> 00:09:48.120
now we I mean, React make
saying you're better, so we oh,

142
00:09:48.240 --> 00:09:52.039
yeah, absolutely, I mean you
could go on about that for days.

143
00:09:52.039 --> 00:09:54.960
But yeah, no, they've definitely
helped each other so much. I mean,

144
00:09:56.240 --> 00:10:01.240
the state of web frameworks these days, like any any web framework that's

145
00:10:01.240 --> 00:10:03.759
still being maintained at the moment,
is like absolutely incredible to work with.

146
00:10:05.000 --> 00:10:11.720
Like it's yeah, it's such The
web development space is just such a such

147
00:10:11.759 --> 00:10:15.120
an an amazing sort of space to
be working in now that it was like

148
00:10:15.159 --> 00:10:18.120
five years ago, which isn't a
lot of time, like to have passed

149
00:10:18.120 --> 00:10:22.200
them. So much has changed,
you know, everything's everything's using timescript now

150
00:10:22.200 --> 00:10:26.279
as well, which is like the
best thing ever. Yeah, so it's

151
00:10:26.279 --> 00:10:31.320
like it's very very cool. Yeah, that's awesome. Hey, folks,

152
00:10:31.360 --> 00:10:35.120
this is Charles Maxwood, and I
just launched my book, The Maxicoder's Guide

153
00:10:35.120 --> 00:10:39.039
Defining Your Dream Developer Job. It's
up on Amazon. We self published it.

154
00:10:39.240 --> 00:10:41.639
I would love your support if you
want to go check it out,

155
00:10:41.679 --> 00:10:45.080
you can find it there, The
Maxicoter's Guide Defining Your Dream Developer Job.

156
00:10:45.360 --> 00:10:48.519
Have a good one, max out. Yeah. I mean I look at

157
00:10:48.519 --> 00:10:54.720
Angular and you know, I compare
it as a framework to you know,

158
00:10:54.879 --> 00:10:58.240
like reactor View, and I think
that I see advantages in a lot of

159
00:10:58.279 --> 00:11:05.879
them. But Angular Angular heavily heavy, heavy, angler's heavy opinions towards you

160
00:11:05.960 --> 00:11:11.519
will use type script is such a
massive like all right, I like Anger

161
00:11:11.519 --> 00:11:16.279
a little bit more than the rest
because it's and then they also like really

162
00:11:16.320 --> 00:11:20.639
really push you to use our xcs, and for me, our EXS is

163
00:11:20.639 --> 00:11:24.840
the greatest technology on the web right
now. So I'm like, I look

164
00:11:24.840 --> 00:11:30.840
at those two opinions of Angular,
and they really really forced me to be

165
00:11:30.960 --> 00:11:35.080
like, yeah, Anglars, I
like Angular the most by far, Like

166
00:11:35.159 --> 00:11:41.720
Angular is fantastic. Yeah, but
it's it's it's largely do because I absolutely

167
00:11:41.720 --> 00:11:48.080
love type scripts and I absolutely love
our exers. Yeah. Yeah, it's

168
00:11:48.120 --> 00:11:52.440
just the whole like reactive programming and
observables and all of that. It's like

169
00:11:52.519 --> 00:11:54.440
you look at it now and you're
sort of you know, that's obviously sort

170
00:11:54.440 --> 00:11:58.639
of what you go to way of
thinking about solving problems and structuring, like

171
00:11:58.759 --> 00:12:01.639
how how you're going to how you're
going to do these things, And like

172
00:12:01.879 --> 00:12:05.679
you look back and be like a
couple of years ago that you'd never thought

173
00:12:05.720 --> 00:12:09.159
like that. You're sort of like
grabbing your hair, being like, why

174
00:12:09.200 --> 00:12:11.600
on earth wasn't this always available?
Why wasn't this always just a thing?

175
00:12:11.799 --> 00:12:16.559
Yeah? Yeah, Like I look
at observables and and I'm like, wait,

176
00:12:18.720 --> 00:12:24.000
how did promises survive so long?
Like it's insane. Not that promises

177
00:12:24.000 --> 00:12:28.559
aren't good, it's just that observables
are so much more superior. Yeah,

178
00:12:28.600 --> 00:12:33.559
it's just so much neater promises are
single use? How and observables? How

179
00:12:35.240 --> 00:12:41.320
did single use promises last for so
long? That's my question? Is it

180
00:12:41.480 --> 00:12:45.480
just seems intense? Yeah, so
so yeah, anyway, keep going.

181
00:12:45.679 --> 00:12:46.519
Yeah, I was just going to
say, I think that like one of

182
00:12:46.559 --> 00:12:52.279
the biggest things is it's it's taken
I guess the front end community so much

183
00:12:52.360 --> 00:13:00.159
longer to think of solving problems in
functional terms like that's now like become being

184
00:13:00.200 --> 00:13:01.840
such a big thing in the front
end space. But it definitely wasn't like

185
00:13:01.919 --> 00:13:07.399
that, Like everything was so oo
based, like you're thinking, like when

186
00:13:07.799 --> 00:13:13.200
just like people trying to write classes
in like ES five and having like anything

187
00:13:13.240 --> 00:13:16.639
that way, you had to mess
around with prototypes and inheritance and stuff like

188
00:13:16.679 --> 00:13:20.600
that, and it's just like it's
so gross to think that people used to

189
00:13:20.639 --> 00:13:24.799
work like that. But you know, once again, like that was only

190
00:13:24.840 --> 00:13:28.519
a few years ago. It really
wasn't that long ago that people were thinking

191
00:13:28.600 --> 00:13:33.120
like that, and really we are
oh yeah yeah. Yeah. So one

192
00:13:33.159 --> 00:13:37.039
thing you know, when we talk
when we say reactive programming, I think

193
00:13:37.080 --> 00:13:43.200
people if you don't know what that
means, you really get lost at when

194
00:13:43.240 --> 00:13:46.360
when we say what is reactive?
And I think it makes people feel like,

195
00:13:46.039 --> 00:13:48.840
ah, I'm not smart enough,
and I think it makes them shy

196
00:13:48.879 --> 00:13:52.399
away a little bit from the conversation
because they're like, I don't know what

197
00:13:52.519 --> 00:13:58.279
it is, so I can't talk
about it. So I've focused a lot

198
00:13:58.279 --> 00:14:03.399
of reasons on trying to teach the
reactive piece of Angular and just the concept

199
00:14:03.440 --> 00:14:07.320
of reactive programming, because I feel
like it's such an important thing. And

200
00:14:07.480 --> 00:14:13.559
uh, in teaching that, I
mean, when you learn our ex tell

201
00:14:13.600 --> 00:14:16.039
me, tell me if this happened
to you, you basically write your code

202
00:14:16.039 --> 00:14:22.039
differently once you understand it. Yeah, absolutely, yeah, and sorry,

203
00:14:22.039 --> 00:14:26.279
go ahead. Oh, just like
I think the the thing that just like

204
00:14:26.320 --> 00:14:30.080
springs to mind, like sort of
bringing this back to Angular as well,

205
00:14:30.639 --> 00:14:35.000
is making a HGTP request yep,
Like just the even just doing that,

206
00:14:35.159 --> 00:14:41.799
like subscribing to that observable. And
I think that there's there's quite a lot

207
00:14:41.879 --> 00:14:46.399
even just doing that is quite a
learning curve, and there's so many like

208
00:14:46.480 --> 00:14:50.440
different concepts if you've never come across
that before. I still remember when it

209
00:14:50.480 --> 00:14:54.080
was first introduced to me, and
I just remember reading like the r XJS

210
00:14:54.159 --> 00:15:01.080
documentation, which is absolutely amazing,
but it's so much in maation to absorb.

211
00:15:01.159 --> 00:15:03.799
It's so like it's so much to
take in, and then it's so

212
00:15:03.879 --> 00:15:07.159
much. It's so like it takes
such a long time, and it's quite

213
00:15:07.159 --> 00:15:09.679
a process. Like think of term, think of things in terms of like

214
00:15:09.679 --> 00:15:13.840
like reactive programming, or think of
things in terms of observables. It like

215
00:15:13.879 --> 00:15:18.440
sort of reminds me of when like
things like map and filter and reduce are

216
00:15:18.480 --> 00:15:22.840
sort of introduced to you and you
need to move away from like mutable data

217
00:15:22.840 --> 00:15:28.519
structures and using for loops for everything, and then eventually one day it just

218
00:15:28.600 --> 00:15:31.440
clicks and you start thinking of terms. You start thinking of things in terms

219
00:15:31.480 --> 00:15:37.360
of those you know, mapping and
filtering and all of that. Yeah,

220
00:15:37.759 --> 00:15:43.159
I uh so, like it's I
try. It's it's hard to help people

221
00:15:43.240 --> 00:15:48.679
like get get across that initial like
aha moment, right, Yeah. And

222
00:15:48.519 --> 00:15:54.440
I struggled teaching it because it was
so hard for me that I'm like,

223
00:15:54.679 --> 00:15:56.480
oh man, how do I teach
this? This thing that was so hard

224
00:15:56.519 --> 00:16:03.840
for me? And I've come up
in my mind of this a way that

225
00:16:03.919 --> 00:16:07.000
it makes sense to me, but
I don't think it makes sense that other

226
00:16:07.039 --> 00:16:10.600
people, like like when you when
you say, hey, declarative coding versus

227
00:16:10.639 --> 00:16:15.120
imperative coding. Those two words largely
don't have any significance to most people,

228
00:16:15.200 --> 00:16:22.960
like they certainly did it to me. But once I understood what RX did

229
00:16:22.000 --> 00:16:26.600
to my programming style, I was
like, oh, I now just declare

230
00:16:26.639 --> 00:16:33.679
things I don't actually I don't actually
write much more like my click candlers are

231
00:16:33.759 --> 00:16:40.159
are nothing more than just setting variables, like I don't actually do ahtps in

232
00:16:40.200 --> 00:16:42.440
my click handler, you know,
I just say, hey, put this

233
00:16:42.519 --> 00:16:48.799
into that abservable, and then the
abserable that was already declared like freaks out

234
00:16:48.799 --> 00:16:52.639
and does all this stuff. Right. Yeah, So so like trying to

235
00:16:52.679 --> 00:16:57.600
help people understand, Hey, your
code before our X you wrote declarative code

236
00:16:59.360 --> 00:17:06.799
and or sorry, imperative code,
and afterwards you're gonna write declarative getting them

237
00:17:06.799 --> 00:17:08.920
over that hurdle? What does that
mean? Though? It feels scary to

238
00:17:08.920 --> 00:17:14.920
say you're going to code differently,
but like you are going to go differently,

239
00:17:15.039 --> 00:17:18.960
right yeah, and there's no look
back exactly, and then that the

240
00:17:18.960 --> 00:17:22.880
thing you won't look back once it
happens. Yeah, yeah, as soon

241
00:17:22.880 --> 00:17:26.640
as as soon as you have the
light bulb moment, that's it you're you,

242
00:17:26.640 --> 00:17:32.559
you'll be subscribed to that sort of
way of thinking for good. Yeah.

243
00:17:33.480 --> 00:17:37.640
So uh so have you what kind
of what kind of unique experiences have

244
00:17:37.759 --> 00:17:41.480
you had around and either like if
you have you worked with open source and

245
00:17:41.519 --> 00:17:45.920
you given toxic conferences, are you
doing blogs like talk to us about Hey,

246
00:17:45.079 --> 00:17:51.519
who's Dave? Who's Dave? That's
a very very deep question. Well,

247
00:17:51.559 --> 00:17:55.920
I guess like stuff I've been doing
in the community just in general over

248
00:17:55.960 --> 00:17:59.640
like the last few years and all
of that. I as soon as I

249
00:17:59.720 --> 00:18:03.519
moved to London, I started doing
as much talking at like meetups around London

250
00:18:03.559 --> 00:18:07.440
and Bristol because of my work has
an office in Bristol, so I do

251
00:18:07.480 --> 00:18:11.079
a bit of travel there, so
there's a couple of meetups there. So

252
00:18:11.359 --> 00:18:15.160
I love I love doing public speaking. And then this year I just did

253
00:18:15.160 --> 00:18:18.079
my my first step of conference talk
actually, which was at Angular Connect,

254
00:18:19.480 --> 00:18:22.880
which is yeah, yeah, which
was pretty awesome. It was a pretty

255
00:18:22.920 --> 00:18:26.400
I guess, like for a first
sort of conference talk, it was a

256
00:18:26.400 --> 00:18:30.039
pretty big stage. Yeah, it's
crazy. You went from zero to connect

257
00:18:30.200 --> 00:18:34.359
that's big. Yeah. I absolutely
loved it. I was so nervous because

258
00:18:34.640 --> 00:18:41.119
I was talking in the slightly smaller
room, and there was there was a

259
00:18:41.160 --> 00:18:45.079
deep dive talk going on in the
other room at the same time as me,

260
00:18:45.160 --> 00:18:45.759
and I thought, well, that's
it. I'm going to give about

261
00:18:45.759 --> 00:18:49.440
four people turn up to my room
because people love a deep dive talk,

262
00:18:49.839 --> 00:18:56.839
like they're my favorite types of talks
as well. And but I think I

263
00:18:56.839 --> 00:18:59.039
had a full room when I was
doing it, and it was it was

264
00:18:59.079 --> 00:19:04.079
really really exciting, And it was
just after my my baby was just born,

265
00:19:06.039 --> 00:19:08.000
so my fiance and baby were there
as well, and pulled them up

266
00:19:08.039 --> 00:19:14.000
on stage to embarrass them. So
that was really really cool. So yeah,

267
00:19:14.000 --> 00:19:18.400
I've slutely that and I just I
just submitted CFP for m G COMF

268
00:19:18.839 --> 00:19:23.279
for the next year. Yeah,
so yeah, that's that's really exciting as

269
00:19:23.279 --> 00:19:30.680
well. And then around like I
guess open source and stuff, I created

270
00:19:32.160 --> 00:19:37.319
a data mocking library called data marks, which is what I spoke about the

271
00:19:37.799 --> 00:19:44.160
topic of data mocking at Angular Connect
and that's got a bit of traction and

272
00:19:44.200 --> 00:19:48.119
I'm sort of that's starting to ramp
up as well, Like that's getting I

273
00:19:48.119 --> 00:19:51.839
think it's up to maybe about four
four thousand downloads a month or something like

274
00:19:51.839 --> 00:19:56.279
that, which I'm really happy with. What is this that's four thousand downloads

275
00:19:56.279 --> 00:20:03.880
a month. So so it just
gives you a way of through your It's

276
00:20:03.079 --> 00:20:07.440
a code config that you specify a
bunch of endpoints in your application that you

277
00:20:07.480 --> 00:20:11.880
want to mock out, and so
it's just matched on the endpoint name and

278
00:20:11.920 --> 00:20:17.480
you can do a regular expression against
that and then you can just specify what

279
00:20:17.559 --> 00:20:22.039
you want the response to be and
then in your code it won't actually it'll

280
00:20:22.079 --> 00:20:30.640
just intercept the hate GTP calls and
give back canned responses. So would this

281
00:20:30.720 --> 00:20:33.640
be for like testing or what would
this be for? So this is I

282
00:20:33.680 --> 00:20:36.960
guess and that's the biggest question that
I get around it as well. And

283
00:20:36.960 --> 00:20:38.920
this is the thing that I'm most
passionate about, which is it's not for

284
00:20:40.000 --> 00:20:44.359
testing, it's but actually doing local
development. So when if you're developing a

285
00:20:44.359 --> 00:20:47.880
feature or trying to reproduce a bug, or you know, just trying to

286
00:20:47.880 --> 00:20:52.240
make a general improvement on your application, rather than connecting out to you know,

287
00:20:52.359 --> 00:20:56.799
either a production environment or a UAT
environment or whatever, where you're actually

288
00:20:56.799 --> 00:21:03.519
touching real data in databases and and
things immediately become unpredictable. Or maybe you

289
00:21:03.559 --> 00:21:10.200
know, you don't really want to
be mutating someone's actual data. This this

290
00:21:10.279 --> 00:21:14.720
allows you to completely circumvent that you
don't need any sort of like network connection

291
00:21:15.000 --> 00:21:18.480
and you can It's really it means
that as well as that you don't need

292
00:21:18.559 --> 00:21:23.119
to rely on an endpoint existing to
be able to develop your your features.

293
00:21:25.000 --> 00:21:29.400
So whether that's whether it's you having
to write that endpoint yourself, or if

294
00:21:29.400 --> 00:21:32.960
you're relying on a back end engineer
or just some other engineer to write that

295
00:21:33.039 --> 00:21:37.519
endpoint for you, you can still
crack on and and and you know,

296
00:21:37.559 --> 00:21:41.759
write your features, fix your bugs
without without needing those endpoints to be available

297
00:21:41.759 --> 00:21:48.759
all the time. Adventures and Angler
is a dev chat dot tv production made

298
00:21:48.759 --> 00:21:52.240
in partnership with hero Devs. Hero
Devs is a group of Angular experts who

299
00:21:52.240 --> 00:21:56.359
can help your team code like true
developer heroes. If your team needs an

300
00:21:56.359 --> 00:22:03.079
Angular expert, reach out to Aaron
at hero deav today. So it sounds

301
00:22:03.119 --> 00:22:10.000
to me like it would be a
really good teaching tool as well, Like

302
00:22:10.039 --> 00:22:14.279
if I was going to give a
workshop and I wanted people to practice using

303
00:22:14.319 --> 00:22:18.400
Angular and making HTTP calls, they
could and they wouldn't actually have to send

304
00:22:18.480 --> 00:22:22.200
up the back end though, So
it'd make my MPM install much lighter,

305
00:22:22.240 --> 00:22:25.480
like they wouldn't have to you know, run a local host or whatever to

306
00:22:25.759 --> 00:22:27.359
get data going, or I wouldn't
have to have like a you know,

307
00:22:29.200 --> 00:22:32.680
an easy two running that would serve
everybody, like I could just do some

308
00:22:32.759 --> 00:22:37.720
in browser memories and stuff. Absolutely, I think I actually think that the

309
00:22:37.200 --> 00:22:42.119
Angular Cli I'd love to see it
provide some sort of mocking solution so to

310
00:22:42.279 --> 00:22:45.559
achieve the same thing, like so
that you can just say, hey,

311
00:22:45.920 --> 00:22:53.039
Angular ci a cli, spin up
this application and provide a flag to tell

312
00:22:53.039 --> 00:22:57.240
it to give you some like give
you the ability to to mock data out,

313
00:22:57.279 --> 00:23:02.400
and then you can immediately begin doing
feature work. So what's the name

314
00:23:02.440 --> 00:23:07.000
of this package. It's called data
marks. It's on NPM data mars.

315
00:23:07.359 --> 00:23:11.680
Yeah, data Dashmarks, And yeah, I absolutely love it. I love

316
00:23:11.720 --> 00:23:15.880
all things testing and mocking and all
of that, because I think it's just

317
00:23:15.160 --> 00:23:22.000
a space that everyone everyone is sort
of being stuck in the same frame of

318
00:23:22.079 --> 00:23:25.920
mind of how we do these sorts
of things, and I think this changes

319
00:23:25.960 --> 00:23:29.559
it up a little bit, just
in the way that we think about things

320
00:23:29.599 --> 00:23:34.839
like it isn't absolutely necessary to be
using real data or or you know,

321
00:23:36.440 --> 00:23:41.839
a shared environment database or anything like
that. Because I think that a lot

322
00:23:41.880 --> 00:23:44.640
of the time, bad things have
real potential to happen. Like if you're

323
00:23:44.680 --> 00:23:48.960
touching live data, then if you
make any sort of right operation to anything,

324
00:23:48.319 --> 00:23:52.039
you know, you could be you
could be impacting a customer or a

325
00:23:52.160 --> 00:23:56.200
user. Or if you're using a
shared environment, like a shared development environment,

326
00:23:56.720 --> 00:23:57.519
you know, someone else might be
relying. You know, if you've

327
00:23:57.559 --> 00:24:02.079
just pulled up a customer and you've
just change their I don't know their address

328
00:24:02.160 --> 00:24:04.799
or whatever, and someone else is
relying on that to be in a particular

329
00:24:04.839 --> 00:24:11.480
state, I think that that that's
definitely like a really a big one.

330
00:24:11.519 --> 00:24:14.440
And then I guess, like the
other the biggest well not the biggest thing,

331
00:24:14.480 --> 00:24:18.960
but one of the biggest things is
that if I say to you know,

332
00:24:18.279 --> 00:24:22.319
I could say to anyone with their
applications, you know, bring me

333
00:24:22.400 --> 00:24:26.440
up a customer that I don't know, if it's like a banking application,

334
00:24:26.519 --> 00:24:27.920
bring me up a customer that has
three accounts, two of them are in

335
00:24:27.960 --> 00:24:33.359
credit, one of them is in
debt, and you know their their latest

336
00:24:33.559 --> 00:24:37.599
credit card payment is late or whatever, Like I don't want to have to

337
00:24:37.640 --> 00:24:41.960
go and mess around in a database, and you know, like force a

338
00:24:41.000 --> 00:24:45.319
customer to be in that particular state. I'd rather just have some solution that

339
00:24:45.359 --> 00:24:49.880
I can just say. You know, in data marks, there's the concept

340
00:24:49.880 --> 00:24:56.119
of a scenario and you could just
like say, scenario two accounts good,

341
00:24:56.160 --> 00:25:00.240
one account bad, and then you
can define what the responses look like for

342
00:25:00.400 --> 00:25:06.960
that. Mm hmm yeah, super
quick and yeah, I absolutely love it.

343
00:25:07.440 --> 00:25:10.039
But I would say that considering I'm
the guy that wrote it. But

344
00:25:10.480 --> 00:25:14.799
it's I think it's I just think
it's a very cool idea. That is

345
00:25:14.799 --> 00:25:21.880
a cool idea. Well, that's
awesome. I love seeing people with with

346
00:25:22.279 --> 00:25:25.160
open source levers like that. I
can't find it. I was looking while

347
00:25:25.160 --> 00:25:30.440
you're talking. I think Ward Bell
wrote something very similar. I think I

348
00:25:30.440 --> 00:25:34.480
think it's like in browser back end
or I can't remember. I can't remember

349
00:25:34.519 --> 00:25:38.720
what you call it, but I
feel like Devakata has done some trainings with

350
00:25:38.720 --> 00:25:42.799
with something like this before. So
I have a very love the idea.

351
00:25:42.920 --> 00:25:49.000
I love the idea of people having
ways to not have a back end,

352
00:25:49.079 --> 00:25:52.319
whether it's for development or for teaching. I love that as an option.

353
00:25:52.680 --> 00:25:56.640
So I've just painted link to it
in the chat there. Actually cool.

354
00:25:56.920 --> 00:26:00.359
Yeah, so we'll have we'll have
a we'll have a linked in the show

355
00:26:00.400 --> 00:26:04.799
notes. If anyone who wants to
go check it out, well cool.

356
00:26:07.119 --> 00:26:11.079
So is there any last Is there
anything else that you'd like? Hey,

357
00:26:11.119 --> 00:26:12.359
if I was going to say one
thing about me, this is what I

358
00:26:12.400 --> 00:26:22.359
would say. I just to help
people get to know I guess one like,

359
00:26:22.799 --> 00:26:26.920
I'm definitely one of those people that
is more on the cowboys side of

360
00:26:26.960 --> 00:26:32.160
things. I love just having an
idea or hearing an idea and immediately just

361
00:26:32.160 --> 00:26:34.519
start start to get code down,
start to build things out, iterate on

362
00:26:34.599 --> 00:26:41.039
things. It's just I just I
guess I'm probably a little bit hyperactive in

363
00:26:41.039 --> 00:26:45.160
that sense. I just love to
do things, get things done, you

364
00:26:45.200 --> 00:26:48.839
know, make mistakes quickly. And
I think that's it also makes things really

365
00:26:48.880 --> 00:26:53.240
fun. Rather than standing around whiteboards
all day trying to over architect things,

366
00:26:55.400 --> 00:27:02.200
just get it done. And I
I love. I guess the other thing.

367
00:27:02.279 --> 00:27:04.519
I just love to I love to
talk to people about any anything to

368
00:27:04.559 --> 00:27:10.440
do with software or web development or
anything like that. It's it's I think

369
00:27:10.440 --> 00:27:15.200
it's just so much fun. Cool. If if people out there want to

370
00:27:15.200 --> 00:27:18.759
get a hold of you, or
they want to ask you some questions,

371
00:27:18.759 --> 00:27:21.680
what's the easiest way for for them
to get a hold of you. You

372
00:27:21.720 --> 00:27:25.640
can get a hold of me on
Twitter. I think my Twitter handle is

373
00:27:25.720 --> 00:27:33.200
Dave Wright's codes or or you can
get me on email as well. That's

374
00:27:33.200 --> 00:27:36.839
probably a good place, Dave at
Davecooper dot org. It's a pretty good

375
00:27:36.839 --> 00:27:40.640
way of getting in contact with me. But yeah, that's that. Those

376
00:27:40.640 --> 00:27:45.279
are probably the two places. Yeah, Dave rights codes at Dave Rights codes

377
00:27:45.480 --> 00:27:48.799
spelled just like it sounds. I
found well cool. Yeah, so if

378
00:27:48.799 --> 00:27:52.599
you want to, if you have
any questions, feel free to to reach

379
00:27:52.680 --> 00:27:57.119
out to to Dave. All right, so Dave, we're gonna move on

380
00:27:57.160 --> 00:28:00.279
to the last the kind of closing
port from the podcast. It's called the

381
00:28:00.359 --> 00:28:04.319
Picks. You get to pick uh, something that you really like and that

382
00:28:04.359 --> 00:28:08.599
you want to share with with other
people. So I'm going to do a

383
00:28:08.640 --> 00:28:14.039
pick. It doesn't have to be
related to programming. It can be if

384
00:28:14.079 --> 00:28:17.160
you want it to be, though, So I'm going to pick Uh.

385
00:28:18.000 --> 00:28:21.279
I've picked it recently, but it
happened again, so I'm going to pick

386
00:28:21.279 --> 00:28:25.559
it again. Yep. There's this
television show It's been on for years,

387
00:28:25.599 --> 00:28:29.279
Like a lot of millennials think,
like wow, that's still on. It's

388
00:28:29.319 --> 00:28:33.880
called It's called Survivor, and I
love Survivor. I can't I can't get

389
00:28:33.960 --> 00:28:37.400
enough a survivor I had one of
my friends went on a few years ago,

390
00:28:37.799 --> 00:28:41.200
and I was already an addict,
but ever since I've been more of

391
00:28:41.240 --> 00:28:47.000
an addict. I just lost like
eighty pounds because I really, really I

392
00:28:47.440 --> 00:28:51.519
don't want to die. That's why
I lost the light. But ancillary goal

393
00:28:51.599 --> 00:28:52.720
was I want to go tryal for
Survivor. I think I could. I

394
00:28:52.720 --> 00:28:57.200
think I can kill it. Anyway. This season though, this this this

395
00:28:57.240 --> 00:29:03.519
season that is currently playing in the
States is uh, it's got some really

396
00:29:03.559 --> 00:29:08.839
strong social messaging, Like Survivors never
really had strong social messaging. Like once

397
00:29:08.880 --> 00:29:12.960
in a while there will be talk
of like an all girls alliance and how

398
00:29:14.039 --> 00:29:18.279
women are powerful, right, But
but other than that specific scenario, there's

399
00:29:18.319 --> 00:29:22.400
not a lot of social messaging and
insight Survivor, right, And they don't

400
00:29:22.440 --> 00:29:26.960
really call out, hey, why
do why do black people get voted out

401
00:29:26.960 --> 00:29:29.559
first? Like that? That sucks? Why does that? Why does that

402
00:29:29.599 --> 00:29:33.880
continue to happen season after season?
Right? Yeah, well, this season

403
00:29:34.240 --> 00:29:37.799
they're talking about those things and it's
not necessarily the show owners. It's the

404
00:29:37.839 --> 00:29:44.440
contestants on the Island. They just
got like a really good cluster of people

405
00:29:45.160 --> 00:29:49.000
and they're talking about these things that
are like impactful, and like I watched

406
00:29:49.039 --> 00:29:52.799
these shows with my kids and like
I get like chills, and a couple

407
00:29:52.839 --> 00:29:56.039
of times I've even like teared up
a little bit and my kids are like,

408
00:29:56.039 --> 00:29:57.359
what's the matter? I'm like,
that was just a really good message,

409
00:29:57.599 --> 00:30:03.920
you know what they're teaching. So
I'm gonna pick because this season,

410
00:30:03.000 --> 00:30:07.400
two things that I really care about
have crossed into an interest they've intersected,

411
00:30:07.400 --> 00:30:12.119
which is I really like Survivor and
I really care about equality and people treating

412
00:30:12.160 --> 00:30:17.200
each other excellently, and so it's
the two things that kind of crossed over.

413
00:30:17.240 --> 00:30:21.720
So I'm going to pick again Survivor. So that's my pick is Survivor.

414
00:30:22.559 --> 00:30:26.319
Hey you got any picks? Bro
oh man? This is This is

415
00:30:26.359 --> 00:30:32.319
a really a really tough one.
But I'm sure people struggle a bit with

416
00:30:32.359 --> 00:30:41.599
this one. I guess something that
something that I I'm really really interesting.

417
00:30:41.640 --> 00:30:47.720
I guess Okay, this will be
this will be a pretty nerdy one.

418
00:30:48.039 --> 00:30:55.519
Okay. Back in Australia, I
used to I used to run We started

419
00:30:55.559 --> 00:31:00.559
up a company and then I sold
it and people always ask you know,

420
00:31:00.640 --> 00:31:04.960
what company, what company did you
start up? And I always have to

421
00:31:06.039 --> 00:31:10.279
start it off with it sounds a
lot more dodgy than it is, which

422
00:31:10.319 --> 00:31:17.240
then makes it sound even dodgier than
that. But it was. It was

423
00:31:17.480 --> 00:31:22.519
a company that we bought and sold
locksmithing suppliers, and then people sometimes asked,

424
00:31:22.519 --> 00:31:27.359
what's a locksmithings supply and I'm talking
about like lock picks and tools like

425
00:31:27.440 --> 00:31:33.279
that. Basically, we saw me
and this other guy that started it.

426
00:31:33.359 --> 00:31:40.799
We just saw that there were no
real like retailers of lock picking stuff in

427
00:31:40.839 --> 00:31:45.079
Australia, and the stuff that you
could get was really really like cheap,

428
00:31:45.519 --> 00:31:48.640
flimsy. It was. It was
really poor quality stuff. And so we

429
00:31:48.799 --> 00:31:53.200
decided that we would see if we
can strike up some wholesale agreements with some

430
00:31:53.240 --> 00:32:00.440
of the sort of more reputable manufacturers, and we sort of got that started

431
00:32:00.480 --> 00:32:02.759
out, and we just sunk a
little bit of cash into the company each

432
00:32:02.880 --> 00:32:07.160
just to get things going, and
it took off really, really well.

433
00:32:07.559 --> 00:32:12.119
And one of the things that we
would always get when we would talk to

434
00:32:12.160 --> 00:32:15.279
people about this sort of thing is, you know, they'd always say,

435
00:32:15.279 --> 00:32:17.440
oh, don't you know that's illegal? And you know why, would you

436
00:32:17.480 --> 00:32:22.519
be supplying, you know, things
that I was supplying tools to help criminals,

437
00:32:22.559 --> 00:32:27.119
you know, break into places,
to which that we always had to

438
00:32:27.119 --> 00:32:29.960
sort of say, well, actually, in Australia, it's not illegal to

439
00:32:30.440 --> 00:32:35.279
buy our own those things. But
the other thing as well is that it

440
00:32:35.319 --> 00:32:38.880
isn't it isn't really criminals that are
using these things. It's either locksmith professionals.

441
00:32:38.960 --> 00:32:43.319
Yeah, yeah, there's professionals.
But the thing that I want to

442
00:32:43.359 --> 00:32:49.359
pick here is the it's actually the
lock sport community, which is like it's

443
00:32:49.400 --> 00:32:53.599
a competitive lock picking, which is
a really really cool thing, and the

444
00:32:53.680 --> 00:32:59.079
communities around it in Australia are massive. You know, they hold these big

445
00:32:59.119 --> 00:33:01.519
competitions, you know where you've got
to like sort of they have they have

446
00:33:01.640 --> 00:33:06.119
all sorts of like I guess you
call them events where you know you have

447
00:33:06.200 --> 00:33:09.000
to you know, pick x amount
of locks in the fastest amount of time,

448
00:33:09.119 --> 00:33:13.519
or there's just a really hard lock
and whoever can do it first.

449
00:33:13.799 --> 00:33:19.119
So those sorts of things, and
it's like a super it's a super nerdy

450
00:33:19.119 --> 00:33:21.720
thing, but I think it's just
like a really cool thing that people if

451
00:33:21.720 --> 00:33:24.640
you if you're interested in in I
guess the mechanics of how locks work and

452
00:33:24.680 --> 00:33:30.079
the different types of locks and all
of that. I'd implore people to see

453
00:33:30.079 --> 00:33:36.000
if they do have a local locksport
community, and if they don't, maybe

454
00:33:36.039 --> 00:33:40.279
even try and start on themselves.
Nice. Nice, So what if some

455
00:33:40.519 --> 00:33:43.640
people wanted to check it out?
Where would they go? Check kind of

456
00:33:43.720 --> 00:33:47.480
check out to learn more about this? It depends where they are. I'd

457
00:33:47.480 --> 00:33:52.000
probably check out meetup. Meetup usually
have some stuff. It really depends where

458
00:33:52.000 --> 00:33:57.200
you are in the world. Like, there'll be different Some countries have like

459
00:33:57.680 --> 00:34:00.480
a more like foreign base. Some
of them are just based on be talk

460
00:34:00.559 --> 00:34:02.519
and all of that. So I
just have a little Google, have a

461
00:34:02.519 --> 00:34:05.680
look on made up. I'm sure
that you'll be able to find something.

462
00:34:05.920 --> 00:34:09.119
Okay, so check it out,
become a locksmithy. It'll be fun.

463
00:34:10.239 --> 00:34:14.119
That's the pick, all right,
Dave, thanks for coming on. I'm

464
00:34:14.119 --> 00:34:15.679
glad I got a chance to chat
with you and meet you. If you're

465
00:34:15.679 --> 00:34:22.599
a friend of Ed, I'm glad
that we're friends. I would say I'm

466
00:34:22.599 --> 00:34:25.480
gonna say good luck on the on
the Energie comf talk picsh you know,

467
00:34:25.760 --> 00:34:30.360
only a small fraction of an amount
of people that make it picked. So

468
00:34:30.599 --> 00:34:32.960
I will say good luck because Thank
you very much, Mom, thanks for

469
00:34:34.000 --> 00:34:37.960
having me. But as far as
just being good in the community, I

470
00:34:37.000 --> 00:34:42.519
appreciate it and thanks for thanks for
coming on, thanks so much, and

471
00:34:42.559 --> 00:34:45.599
to the listeners, I'll say thanks
for thanks for being a part of this

472
00:34:45.760 --> 00:34:51.039
and we'll catch you next time.
Peace. Bandwidth for this segment is provided

473
00:34:51.039 --> 00:34:54.119
by cash fly, the world's fastest
CDN. Deliver your content fast with cash

474
00:34:54.119 --> 00:34:59.199
Fly. Visit c A c H
E f l Y dot com to learn

475
00:34:59.239 --> 00:35:00.360
more. Se