WEBVTT

1
00:00:06.240 --> 00:00:07.559
<v Speaker 1>Welcome back to React Roundup.

2
00:00:07.719 --> 00:00:10.080
<v Speaker 2>It's a panelist show today where we're going to talk

3
00:00:10.080 --> 00:00:13.599
<v Speaker 2>about is working at a large or small company better

4
00:00:14.039 --> 00:00:17.480
<v Speaker 2>for your career? With me today is TJ Van Told

5
00:00:17.800 --> 00:00:22.320
<v Speaker 2>everybody and Page meeting House. Hey everyone, all right, I'm

6
00:00:22.320 --> 00:00:24.559
<v Speaker 2>going to start off with saying where I worked and

7
00:00:24.559 --> 00:00:26.920
<v Speaker 2>why you guys kind of fill in what you have

8
00:00:27.120 --> 00:00:29.039
<v Speaker 2>done so that we can kind of give us some background.

9
00:00:29.160 --> 00:00:33.079
<v Speaker 2>So I currently work at a seed stage startup, which

10
00:00:33.479 --> 00:00:35.399
<v Speaker 2>means that we haven't yet gotte our Series A or

11
00:00:35.439 --> 00:00:38.960
<v Speaker 2>Series B or serious funding. So it's very small. There's

12
00:00:38.960 --> 00:00:41.719
<v Speaker 2>about seven people in it, and it's a productivity startup

13
00:00:42.079 --> 00:00:45.719
<v Speaker 2>called Centered App, and we do kind of a flow

14
00:00:46.159 --> 00:00:49.000
<v Speaker 2>type system so to get you into the flow productivity.

15
00:00:49.000 --> 00:00:50.039
<v Speaker 1>So it's pretty cool stuff.

16
00:00:50.240 --> 00:00:54.039
<v Speaker 2>And before that, I was working at Nike and Walmart,

17
00:00:54.079 --> 00:00:57.159
<v Speaker 2>So I've kind of done both the small company and

18
00:00:57.240 --> 00:00:58.560
<v Speaker 2>big company thing just recently.

19
00:00:58.719 --> 00:01:00.719
<v Speaker 3>Yeah, and I can go back to this is is TJ.

20
00:01:00.960 --> 00:01:04.519
<v Speaker 3>And I've sort of ran all stages of this as well.

21
00:01:04.599 --> 00:01:07.480
<v Speaker 3>So I started off in big insurance fortune five hundred

22
00:01:08.359 --> 00:01:11.439
<v Speaker 3>insurance company is big stuff. From there, I worked for

23
00:01:11.599 --> 00:01:14.359
<v Speaker 3>a hosting company, liquid Web that was sort of I

24
00:01:14.400 --> 00:01:18.120
<v Speaker 3>guess like medium size, so that was like three four

25
00:01:18.239 --> 00:01:20.560
<v Speaker 3>hundred people when I was working there. Then I went

26
00:01:20.599 --> 00:01:24.959
<v Speaker 3>to work for Progress, which is a fairly large company

27
00:01:25.319 --> 00:01:28.719
<v Speaker 3>as well, and then currently I work with Paige at

28
00:01:28.719 --> 00:01:32.560
<v Speaker 3>Blues Wireless and we are a startup of twenty some people.

29
00:01:32.680 --> 00:01:36.200
<v Speaker 3>So I've got experience from sort of both large and

30
00:01:36.239 --> 00:01:37.480
<v Speaker 3>small and somewhere in between.

31
00:01:37.840 --> 00:01:41.400
<v Speaker 4>And I have a similar set of experience, but it's

32
00:01:41.439 --> 00:01:43.799
<v Speaker 4>not all in web development, which is a little bit

33
00:01:43.959 --> 00:01:46.560
<v Speaker 4>unique because I'm only I've been in web development now

34
00:01:46.599 --> 00:01:50.040
<v Speaker 4>for about five years. My first web job was with

35
00:01:50.200 --> 00:01:55.280
<v Speaker 4>home Depot, so the largest of large enterprise companies, and now,

36
00:01:55.319 --> 00:01:58.439
<v Speaker 4>as TJ mentioned, we are at the smallest of the

37
00:01:58.480 --> 00:02:01.560
<v Speaker 4>small startups with twenty I think we had our twenty

38
00:02:01.680 --> 00:02:05.319
<v Speaker 4>fourth or twenty fifth employee just joined recently. But prior

39
00:02:05.359 --> 00:02:08.759
<v Speaker 4>to that, for about five years, I worked in various

40
00:02:08.800 --> 00:02:12.680
<v Speaker 4>marketing agencies, and I worked for medium sized ones of

41
00:02:12.719 --> 00:02:17.560
<v Speaker 4>a few hundred people. One was acquired and became part

42
00:02:17.560 --> 00:02:21.919
<v Speaker 4>of a giant publicist marketing group, and then I went

43
00:02:22.000 --> 00:02:25.000
<v Speaker 4>to a startup of about forty forty people when I

44
00:02:25.080 --> 00:02:29.599
<v Speaker 4>was there, So everything from very large to very small

45
00:02:29.639 --> 00:02:33.840
<v Speaker 4>and back again, and all of them have definite benefits

46
00:02:33.840 --> 00:02:37.800
<v Speaker 4>and definite drawbacks, And it just depends, I guess what

47
00:02:37.840 --> 00:02:41.919
<v Speaker 4>you're looking for or what you place more value on

48
00:02:42.639 --> 00:02:45.719
<v Speaker 4>as to which ones you might be happier with, and

49
00:02:45.800 --> 00:02:48.400
<v Speaker 4>of course what stage of your career you're in too.

50
00:02:48.599 --> 00:02:51.800
<v Speaker 4>If you're just starting out, maybe a startup where you

51
00:02:51.840 --> 00:02:54.599
<v Speaker 4>get to touch everything is really exciting to you, or

52
00:02:55.159 --> 00:02:57.680
<v Speaker 4>it's terrifying because you don't know what you're doing and

53
00:02:57.719 --> 00:03:01.360
<v Speaker 4>what other developers and people to kind of mentor and

54
00:03:01.400 --> 00:03:04.159
<v Speaker 4>help guide you. So that's a kind of probably a

55
00:03:04.159 --> 00:03:07.360
<v Speaker 4>good place to get started, is what benefits are there

56
00:03:07.479 --> 00:03:10.800
<v Speaker 4>or what pros and cons to the various sizes and

57
00:03:10.879 --> 00:03:12.360
<v Speaker 4>stages of companies.

58
00:03:13.560 --> 00:03:16.319
<v Speaker 2>Yeah, I definitely think there's a huge advantage in kind

59
00:03:16.360 --> 00:03:19.360
<v Speaker 2>of a work life balance in the larger companies that

60
00:03:19.439 --> 00:03:23.199
<v Speaker 2>I've seen. If you are in the middle level, midway

61
00:03:23.199 --> 00:03:26.639
<v Speaker 2>through your career, or maybe you're looking to spend more

62
00:03:26.680 --> 00:03:29.039
<v Speaker 2>time with working on a family, I think a big

63
00:03:29.039 --> 00:03:31.879
<v Speaker 2>company is probably a better choice. You know, usually you

64
00:03:31.919 --> 00:03:36.000
<v Speaker 2>have larger teams and a little bit longer schedules so

65
00:03:36.039 --> 00:03:39.080
<v Speaker 2>that you can kind of predict more and be like, oh, Okay,

66
00:03:39.080 --> 00:03:42.080
<v Speaker 2>I'm actually going to take a vacation this year ooh exciting.

67
00:03:43.319 --> 00:03:47.159
<v Speaker 2>Whereas the seed stage startup, you know, you don't really

68
00:03:47.199 --> 00:03:50.479
<v Speaker 2>have an idea kind of almost day to day sometimes

69
00:03:50.479 --> 00:03:51.919
<v Speaker 2>what you're going to be working on or what the

70
00:03:51.960 --> 00:03:54.039
<v Speaker 2>intensity level is going to be, so there can be

71
00:03:54.080 --> 00:03:55.800
<v Speaker 2>a lot more challenging in terms of that.

72
00:03:56.280 --> 00:03:59.840
<v Speaker 3>Yeah, big companies in general are far more predictable. There's

73
00:04:00.080 --> 00:04:05.000
<v Speaker 3>there's more. There's more just process behind everything, which can

74
00:04:05.039 --> 00:04:07.479
<v Speaker 3>be interpreted as both a good or a bad thing.

75
00:04:07.680 --> 00:04:10.319
<v Speaker 3>Like to bring Jack's example up, like for the vacation thing.

76
00:04:10.560 --> 00:04:13.919
<v Speaker 3>Oftentimes it can be a good thing because there's very

77
00:04:14.159 --> 00:04:17.759
<v Speaker 3>little that would be totally unexpected. Nothing's going to like

78
00:04:17.879 --> 00:04:21.120
<v Speaker 3>throw you off and suddenly make you Chances are like

79
00:04:21.240 --> 00:04:24.279
<v Speaker 3>lose some time out of the blue. Things are far

80
00:04:24.319 --> 00:04:27.199
<v Speaker 3>more structured that way. But at the same time, you

81
00:04:27.199 --> 00:04:30.160
<v Speaker 3>could also view that as a negative because sometimes all

82
00:04:30.199 --> 00:04:32.800
<v Speaker 3>that process can get in your way when you're trying

83
00:04:32.839 --> 00:04:34.319
<v Speaker 3>to do something. I know all of us could tell

84
00:04:34.360 --> 00:04:38.560
<v Speaker 3>stories of like absurd things that happen at large companies

85
00:04:38.680 --> 00:04:42.639
<v Speaker 3>that stop you from accomplishing very trivial things, whereas in

86
00:04:42.639 --> 00:04:46.879
<v Speaker 3>small companies chances are at least there are always degrees

87
00:04:46.920 --> 00:04:48.959
<v Speaker 3>of this, but siances are you have a little bit

88
00:04:49.079 --> 00:04:53.480
<v Speaker 3>more freedom to do what you think is best accomplished,

89
00:04:53.480 --> 00:04:55.720
<v Speaker 3>what you think needs to get accomplished, with less getting

90
00:04:55.720 --> 00:04:58.639
<v Speaker 3>in your way. But again just to the constant thing

91
00:04:58.680 --> 00:05:01.680
<v Speaker 3>of trade offs, because that does make you more responsible

92
00:05:01.720 --> 00:05:04.319
<v Speaker 3>for things. There's less of a crutch for you to

93
00:05:05.160 --> 00:05:07.000
<v Speaker 3>fall back on if you can't get something done. You

94
00:05:07.079 --> 00:05:09.360
<v Speaker 3>might have to do something that you don't want to do,

95
00:05:09.480 --> 00:05:11.240
<v Speaker 3>but there's no one else to do it at a

96
00:05:11.240 --> 00:05:14.639
<v Speaker 3>small company, so there's it's tricky.

97
00:05:15.319 --> 00:05:15.879
<v Speaker 1>Yeah.

98
00:05:16.120 --> 00:05:20.000
<v Speaker 4>One thing that I appreciated coming out of my boot camp,

99
00:05:20.079 --> 00:05:21.920
<v Speaker 4>because I went to a coding boot camp for four

100
00:05:22.120 --> 00:05:26.600
<v Speaker 4>months and then transitioned into web development, was I wanted

101
00:05:26.600 --> 00:05:30.759
<v Speaker 4>to go to a medium or larger sized company because

102
00:05:30.839 --> 00:05:34.879
<v Speaker 4>I wanted other developers around me who were better than

103
00:05:35.199 --> 00:05:38.000
<v Speaker 4>me and more skilled and more knowledgeable and all those

104
00:05:38.040 --> 00:05:41.120
<v Speaker 4>things that I could learn from. Because if boot camp

105
00:05:41.160 --> 00:05:43.319
<v Speaker 4>taught me one thing, it was that there was so

106
00:05:43.480 --> 00:05:47.000
<v Speaker 4>much to learn that I just didn't know. It was

107
00:05:47.040 --> 00:05:50.839
<v Speaker 4>how much more there was after this kind of initial

108
00:05:50.959 --> 00:05:54.959
<v Speaker 4>crash course that I had gotten. So being able to

109
00:05:55.000 --> 00:05:58.519
<v Speaker 4>go to a company the size of home Depot, for instance,

110
00:05:58.720 --> 00:06:01.839
<v Speaker 4>was fantastic because suddenly I was on a team of

111
00:06:02.399 --> 00:06:07.000
<v Speaker 4>eight plus other developers from staff level all the way

112
00:06:07.040 --> 00:06:11.240
<v Speaker 4>down to software engineering level, and everything in between, people

113
00:06:11.319 --> 00:06:14.199
<v Speaker 4>who'd done it for decades, people who'd done it for

114
00:06:14.240 --> 00:06:18.079
<v Speaker 4>a few years, people who had computer science degrees, people

115
00:06:18.160 --> 00:06:22.439
<v Speaker 4>who didn't, and having all of that around me to

116
00:06:22.839 --> 00:06:25.560
<v Speaker 4>learn from, and being part of a team where we

117
00:06:25.560 --> 00:06:30.439
<v Speaker 4>were responsible from everything full stack, our back end services,

118
00:06:30.519 --> 00:06:35.279
<v Speaker 4>our front end services, our build pipeline, doing testing, doing

119
00:06:35.920 --> 00:06:42.920
<v Speaker 4>code quality scans, setting up our GitHub repos and maintaining

120
00:06:42.959 --> 00:06:45.279
<v Speaker 4>those and making sure that they were up to standards.

121
00:06:45.360 --> 00:06:49.279
<v Speaker 4>All of that stuff was fantastic because I got to

122
00:06:50.160 --> 00:06:54.519
<v Speaker 4>touch and learn about all these different things. But it

123
00:06:54.560 --> 00:06:57.319
<v Speaker 4>was also very structured, like you say in that this

124
00:06:57.519 --> 00:07:01.639
<v Speaker 4>was our project, this was our lane, this was what

125
00:07:01.680 --> 00:07:04.319
<v Speaker 4>we were responsible for. And then if you needed something

126
00:07:04.439 --> 00:07:08.279
<v Speaker 4>done anywhere else, you had to talk to another team,

127
00:07:08.519 --> 00:07:10.560
<v Speaker 4>or you had to submit a form, or you had

128
00:07:10.560 --> 00:07:13.839
<v Speaker 4>to fill out X, Y and Z pieces of red

129
00:07:13.879 --> 00:07:18.600
<v Speaker 4>tape to get it done. And sometimes it was great

130
00:07:18.680 --> 00:07:21.319
<v Speaker 4>because we could just something would come to us and

131
00:07:21.360 --> 00:07:23.879
<v Speaker 4>we could say we're not responsible for that, go talk

132
00:07:23.920 --> 00:07:27.639
<v Speaker 4>to this other team. Or stuff would come to us

133
00:07:27.759 --> 00:07:30.680
<v Speaker 4>and we would be either responsible for it or we'd

134
00:07:30.680 --> 00:07:32.959
<v Speaker 4>have to figure it out, or it would be very painful,

135
00:07:33.000 --> 00:07:35.839
<v Speaker 4>like you say, to get it done what should have

136
00:07:35.839 --> 00:07:39.480
<v Speaker 4>been trivial if somebody had had the level of clearance

137
00:07:39.519 --> 00:07:43.839
<v Speaker 4>that was required to make what seemed like a small change.

138
00:07:44.160 --> 00:07:47.240
<v Speaker 4>So a lot of benefits to it, especially early in

139
00:07:47.240 --> 00:07:49.560
<v Speaker 4>your career, because you can just go tap someone on

140
00:07:49.560 --> 00:07:51.360
<v Speaker 4>the shoulder and say, hey, can you look at this

141
00:07:51.480 --> 00:07:53.839
<v Speaker 4>code with me or help me figure out what this

142
00:07:54.000 --> 00:07:56.160
<v Speaker 4>is doing or how to do it. But at the

143
00:07:56.199 --> 00:08:02.040
<v Speaker 4>same time, a lot of processes and potentially a lot

144
00:08:02.079 --> 00:08:05.519
<v Speaker 4>of time in between things getting done shouldn't really take

145
00:08:05.560 --> 00:08:10.040
<v Speaker 4>that long if you knew if you were a smaller company, I.

146
00:08:09.959 --> 00:08:14.000
<v Speaker 3>Guess, yeah, that's funny because that's similar to how I

147
00:08:14.040 --> 00:08:17.079
<v Speaker 3>got my start with big insurance. It's just like a

148
00:08:17.199 --> 00:08:19.000
<v Speaker 3>junior developer role.

149
00:08:19.240 --> 00:08:20.439
<v Speaker 1>And I think.

150
00:08:20.279 --> 00:08:23.480
<v Speaker 3>Another advantage of that is these larger companies they're more

151
00:08:23.560 --> 00:08:27.439
<v Speaker 3>likely to have like established training procedures and like the

152
00:08:27.480 --> 00:08:30.240
<v Speaker 3>budgets to do that sort of thing, whereas your small startup,

153
00:08:30.240 --> 00:08:31.879
<v Speaker 3>you know, they don't have the money to throw around

154
00:08:31.959 --> 00:08:34.440
<v Speaker 3>or the time to do that sort of thing. But

155
00:08:34.519 --> 00:08:37.519
<v Speaker 3>a larger company can have a whole training department that

156
00:08:37.519 --> 00:08:39.720
<v Speaker 3>at least the insurance company I worked for did. They

157
00:08:39.759 --> 00:08:41.799
<v Speaker 3>had people that that was their job was to train

158
00:08:42.440 --> 00:08:45.519
<v Speaker 3>other people and programs to help you get ramped up

159
00:08:45.559 --> 00:08:48.639
<v Speaker 3>and get more involved. And it was more of a

160
00:08:48.840 --> 00:08:52.120
<v Speaker 3>gradual on ramping that I definitely appreciated at the time.

161
00:08:52.200 --> 00:08:55.279
<v Speaker 3>And I only have good things to say about going

162
00:08:55.279 --> 00:08:57.879
<v Speaker 3>through that process and that company because it did help

163
00:08:57.960 --> 00:09:00.720
<v Speaker 3>me get up and running and you know, get my

164
00:09:00.759 --> 00:09:01.840
<v Speaker 3>career jump started.

165
00:09:02.320 --> 00:09:02.639
<v Speaker 1>All right.

166
00:09:02.679 --> 00:09:04.399
<v Speaker 2>I don't disagree with any of that, but I do

167
00:09:04.440 --> 00:09:07.080
<v Speaker 2>feel like we're kind of short shifting the whole startup

168
00:09:07.159 --> 00:09:10.799
<v Speaker 2>experience here, because there is a coolness to being able

169
00:09:10.840 --> 00:09:13.279
<v Speaker 2>to say, you know, hey, I watched this really great

170
00:09:13.279 --> 00:09:14.240
<v Speaker 2>YouTube video on.

171
00:09:14.960 --> 00:09:16.679
<v Speaker 1>Fire Store or whatever it is, you know, and.

172
00:09:18.360 --> 00:09:21.519
<v Speaker 2>It's filling a void in our ecosystem, and I'm we're

173
00:09:21.559 --> 00:09:23.799
<v Speaker 2>just going to go in there and bring it in

174
00:09:23.879 --> 00:09:25.840
<v Speaker 2>and get it done, and we're going to do it today.

175
00:09:26.679 --> 00:09:30.399
<v Speaker 1>And you only do that kind of thing at a startup.

176
00:09:30.440 --> 00:09:34.000
<v Speaker 2>I gotta say, if working at big companies, if you

177
00:09:34.080 --> 00:09:36.960
<v Speaker 2>want to get a new technology, like let's say that

178
00:09:36.960 --> 00:09:39.080
<v Speaker 2>they're doing traditional rest and you really are a huge

179
00:09:39.080 --> 00:09:42.559
<v Speaker 2>fan of graph quel, you have to go and drive that.

180
00:09:42.480 --> 00:09:46.200
<v Speaker 1>Thing daily every day.

181
00:09:46.559 --> 00:09:52.080
<v Speaker 2>Working with engineering management, product management, project management. These are

182
00:09:52.120 --> 00:09:55.200
<v Speaker 2>big ships and they are crazy hard to steer. And

183
00:09:55.240 --> 00:09:59.080
<v Speaker 2>so when folks are saying, oh, it's really hard to

184
00:09:59.279 --> 00:10:01.879
<v Speaker 2>get something done, the yeah, that's politics, and it's everything else,

185
00:10:01.919 --> 00:10:03.639
<v Speaker 2>and it's schedules and and it's all that.

186
00:10:03.840 --> 00:10:08.039
<v Speaker 1>So there are some advantages to that small company vibe of.

187
00:10:08.120 --> 00:10:10.600
<v Speaker 2>You can kind of just you know, get it done,

188
00:10:10.840 --> 00:10:12.879
<v Speaker 2>which is is a really nice feeling sometimes.

189
00:10:13.480 --> 00:10:18.399
<v Speaker 4>Absolutely, if you're ready to take ownership of stuff, you

190
00:10:18.440 --> 00:10:21.200
<v Speaker 4>can kill it at a small company. You just have

191
00:10:21.279 --> 00:10:24.279
<v Speaker 4>to be. I guess the biggest thing a big shift

192
00:10:24.320 --> 00:10:29.200
<v Speaker 4>for me was I I was used to going through

193
00:10:29.240 --> 00:10:33.360
<v Speaker 4>a lot of communication channels before getting minimal access to

194
00:10:33.440 --> 00:10:36.759
<v Speaker 4>whatever it was that we needed at home depot from

195
00:10:36.879 --> 00:10:39.919
<v Speaker 4>you know, from another team or an API endpoint or whatever.

196
00:10:40.600 --> 00:10:45.080
<v Speaker 4>And I had learned pretty early on that suggesting new technologies,

197
00:10:45.360 --> 00:10:49.159
<v Speaker 4>new potent, anything that was going to cost money probably

198
00:10:49.919 --> 00:10:53.759
<v Speaker 4>was never going to happen. They decided at a much

199
00:10:53.799 --> 00:10:56.919
<v Speaker 4>higher level than my team, or my manager or even

200
00:10:56.960 --> 00:11:01.639
<v Speaker 4>my department, what technologies we were using, what vendors we

201
00:11:01.759 --> 00:11:06.080
<v Speaker 4>had access to for anything, and good luck getting something

202
00:11:06.120 --> 00:11:08.519
<v Speaker 4>from the grassroots started that you heard about that you

203
00:11:08.559 --> 00:11:10.600
<v Speaker 4>thought would be really useful to the team. That was

204
00:11:10.679 --> 00:11:13.200
<v Speaker 4>just that was going to die on the vine. But

205
00:11:13.440 --> 00:11:17.240
<v Speaker 4>in startups that is absolutely the case. It's like, if

206
00:11:17.279 --> 00:11:19.639
<v Speaker 4>you see something and you have an idea of a

207
00:11:19.679 --> 00:11:22.279
<v Speaker 4>way to make it better, you can just throw it

208
00:11:22.320 --> 00:11:26.200
<v Speaker 4>out there and probably start running with it that same

209
00:11:26.279 --> 00:11:29.000
<v Speaker 4>day if you have the time and the energy to

210
00:11:29.080 --> 00:11:32.600
<v Speaker 4>do so, which is awesome. It feels so good and

211
00:11:32.720 --> 00:11:36.240
<v Speaker 4>knock stuff out that quickly, and it's a great way

212
00:11:36.279 --> 00:11:36.759
<v Speaker 4>to look.

213
00:11:39.799 --> 00:11:40.159
<v Speaker 1>Exactly.

214
00:11:40.320 --> 00:11:44.159
<v Speaker 4>It's true, you can you can get into a mess

215
00:11:44.200 --> 00:11:47.080
<v Speaker 4>of spaghetti and a lot of vendor charges really quickly

216
00:11:47.120 --> 00:11:50.320
<v Speaker 4>if you're not keeping up with it. But at the

217
00:11:50.360 --> 00:11:54.519
<v Speaker 4>same time you can also you could also really improve

218
00:11:54.919 --> 00:11:57.720
<v Speaker 4>everything in a very short amount of time if if

219
00:11:57.759 --> 00:12:01.120
<v Speaker 4>you make the right decisions and kind of value your options.

220
00:12:02.240 --> 00:12:04.919
<v Speaker 3>So fun story back in my big insurance day is

221
00:12:04.919 --> 00:12:08.080
<v Speaker 3>one of those like political battles that I fodd or

222
00:12:08.120 --> 00:12:13.440
<v Speaker 3>tried to spearhead was getting Chrome installed on everybody's PCs

223
00:12:15.759 --> 00:12:19.600
<v Speaker 3>because this was back when Chrome was was pretty new

224
00:12:20.039 --> 00:12:23.200
<v Speaker 3>and we were all on lockdown windows setups right, so

225
00:12:23.320 --> 00:12:25.799
<v Speaker 3>you couldn't you had no admin access, you can't, you

226
00:12:25.799 --> 00:12:29.879
<v Speaker 3>couldn't install a program. And so Chrome came out and

227
00:12:29.919 --> 00:12:32.440
<v Speaker 3>I was like, well, people are starting to use this thing, right, like,

228
00:12:32.519 --> 00:12:34.639
<v Speaker 3>we should have it. It has good developer tools, This

229
00:12:34.720 --> 00:12:38.000
<v Speaker 3>could really benefit us and the executives, Like like I

230
00:12:38.080 --> 00:12:41.279
<v Speaker 3>had to schedule meetings with executives to try to get

231
00:12:41.320 --> 00:12:43.840
<v Speaker 3>this to happen because they were saying, well, our apps

232
00:12:43.840 --> 00:12:46.200
<v Speaker 3>don't support Chrome, why do you need this? And like

233
00:12:46.399 --> 00:12:50.639
<v Speaker 3>just the absurdity of that entire process, right, Like, especially

234
00:12:50.720 --> 00:12:54.080
<v Speaker 3>given the benefit of hindsight and looking back at this

235
00:12:54.720 --> 00:12:58.200
<v Speaker 3>is just it gets frustrating at a certain point. Like

236
00:12:58.279 --> 00:13:00.840
<v Speaker 3>if if you're the type of person that wants total

237
00:13:00.879 --> 00:13:03.080
<v Speaker 3>control over what you're doing and want to be able

238
00:13:03.120 --> 00:13:07.159
<v Speaker 3>to try and experiment with things, that those sorts of experiences,

239
00:13:07.159 --> 00:13:08.840
<v Speaker 3>I mean, things like that are eventually why I left

240
00:13:08.840 --> 00:13:12.120
<v Speaker 3>that company is because that's it just gets ridiculous. Right,

241
00:13:12.200 --> 00:13:14.279
<v Speaker 3>At a certain point, you just can't take that sort

242
00:13:14.320 --> 00:13:15.039
<v Speaker 3>of thing anymore.

243
00:13:15.799 --> 00:13:19.399
<v Speaker 2>Yeah, I think the there's a bias here when you

244
00:13:19.399 --> 00:13:22.480
<v Speaker 2>think about like a company culture and how it can

245
00:13:22.519 --> 00:13:26.120
<v Speaker 2>go wrong. I think in the in the small startup case,

246
00:13:26.639 --> 00:13:29.480
<v Speaker 2>the going wrong tends to error towards workoholism.

247
00:13:29.879 --> 00:13:32.039
<v Speaker 1>Right, it's just we or we just do we just

248
00:13:32.039 --> 00:13:34.000
<v Speaker 1>got to go go, go, go go kind of thing,

249
00:13:34.000 --> 00:13:35.879
<v Speaker 1>and it's just you're it's crazy.

250
00:13:36.799 --> 00:13:39.879
<v Speaker 2>Whereas in the big companies when they go bad in

251
00:13:39.919 --> 00:13:43.240
<v Speaker 2>terms of culture, they kind of bias towards just politics,

252
00:13:43.279 --> 00:13:47.480
<v Speaker 2>just endless politics, endless meetings that never resolved anything, and

253
00:13:47.480 --> 00:13:50.080
<v Speaker 2>it's just kind of soul crushing and grinding. And then

254
00:13:50.559 --> 00:13:53.320
<v Speaker 2>so I guess that's that is a decision point there

255
00:13:53.399 --> 00:13:56.159
<v Speaker 2>is like, Hey, if things go wrong, which direction do

256
00:13:56.279 --> 00:13:58.639
<v Speaker 2>I want them to go wrong in? Is it is

257
00:13:58.639 --> 00:14:01.200
<v Speaker 2>it overworking myself or is it just kind of being

258
00:14:01.240 --> 00:14:03.639
<v Speaker 2>frustrated to the point where I'm just like, ah, peace out,

259
00:14:03.840 --> 00:14:05.039
<v Speaker 2>I don't need this stuff anymore.

260
00:14:05.320 --> 00:14:07.679
<v Speaker 3>And I think though, like that those might just be

261
00:14:07.799 --> 00:14:11.039
<v Speaker 3>good red flags to look for if you're like interviewing

262
00:14:11.120 --> 00:14:14.320
<v Speaker 3>or evaluating a job, right Like, if you are interviewing

263
00:14:14.360 --> 00:14:16.600
<v Speaker 3>or if you are looking into a startup, those are

264
00:14:16.639 --> 00:14:18.600
<v Speaker 3>the sort of questions you want to ask, right like

265
00:14:18.639 --> 00:14:21.440
<v Speaker 3>how many hours am I expected to work? Is overtime

266
00:14:21.480 --> 00:14:23.639
<v Speaker 3>going to be a thing here? Is it expected? Like

267
00:14:24.039 --> 00:14:26.440
<v Speaker 3>I think startup you could probably expect to do a

268
00:14:26.480 --> 00:14:30.000
<v Speaker 3>bit more work. But you know, unless unless you're really

269
00:14:30.559 --> 00:14:33.639
<v Speaker 3>that sort of person that wants to throw yourself headfirst

270
00:14:33.639 --> 00:14:36.440
<v Speaker 3>into this stuff, like I would definitely consider it a

271
00:14:36.440 --> 00:14:38.799
<v Speaker 3>red flag if they told me, you know, you're expected

272
00:14:38.840 --> 00:14:41.360
<v Speaker 3>to work fifty sixty hours a week or to do

273
00:14:41.919 --> 00:14:44.960
<v Speaker 3>the weekend work, And so that's the sort of thing

274
00:14:45.000 --> 00:14:47.799
<v Speaker 3>I would look for. And on the flip side, like

275
00:14:47.919 --> 00:14:51.679
<v Speaker 3>with big companies, I mean, you would want to ask

276
00:14:51.759 --> 00:14:55.159
<v Speaker 3>questions about how much authority do developers have, how much

277
00:14:55.200 --> 00:14:58.519
<v Speaker 3>are they involved in the decision making processes, you know,

278
00:14:58.559 --> 00:15:00.679
<v Speaker 3>how much do they get to say, and what technologies

279
00:15:00.679 --> 00:15:04.840
<v Speaker 3>are used because I've been involved. Even though those are

280
00:15:04.879 --> 00:15:08.960
<v Speaker 3>like stereotypical things about these companies, there's certainly pockets of

281
00:15:08.960 --> 00:15:13.000
<v Speaker 3>big companies that operate more like a startup, right and

282
00:15:13.080 --> 00:15:16.720
<v Speaker 3>there are startups that are a little bit more stable

283
00:15:16.759 --> 00:15:19.000
<v Speaker 3>and secure. So those are the sort of things I

284
00:15:19.000 --> 00:15:22.879
<v Speaker 3>guess to look for as you're exploring your options.

285
00:15:23.399 --> 00:15:26.200
<v Speaker 4>And another good thing to consider is what kind of

286
00:15:26.320 --> 00:15:29.200
<v Speaker 4>experience are you looking to gain, Like do you want

287
00:15:29.240 --> 00:15:33.720
<v Speaker 4>to go super deep into one particular either area of

288
00:15:33.759 --> 00:15:38.840
<v Speaker 4>expertise or one product like that's because that's typically what

289
00:15:38.879 --> 00:15:42.720
<v Speaker 4>you're going to have on the enterprise level, is you're

290
00:15:42.720 --> 00:15:46.399
<v Speaker 4>going to have one product that you are responsible for

291
00:15:46.960 --> 00:15:49.320
<v Speaker 4>and it's but it's going to be a complex product

292
00:15:49.480 --> 00:15:51.960
<v Speaker 4>more more likely than not, So you're going to be

293
00:15:52.080 --> 00:15:54.720
<v Speaker 4>handling the databases, you're going to be handling the back ends,

294
00:15:54.799 --> 00:15:56.840
<v Speaker 4>the front ends, and you're going to be doing some

295
00:15:56.919 --> 00:16:00.720
<v Speaker 4>probably some pretty complex stuff with it. But if you

296
00:16:00.759 --> 00:16:03.799
<v Speaker 4>are if you like having a variety of things to

297
00:16:03.840 --> 00:16:06.960
<v Speaker 4>work on, then maybe a startup is a better choice

298
00:16:07.000 --> 00:16:10.360
<v Speaker 4>for that because you'll probably be touching one website one day,

299
00:16:10.399 --> 00:16:12.440
<v Speaker 4>and then you'll be looking at some kind of an

300
00:16:12.600 --> 00:16:14.919
<v Speaker 4>SEO tool the next day, and then you'll be trying

301
00:16:14.960 --> 00:16:17.480
<v Speaker 4>to get analytics a third day and figuring out how

302
00:16:17.519 --> 00:16:22.240
<v Speaker 4>to connect all these different pieces of the company into

303
00:16:22.960 --> 00:16:25.720
<v Speaker 4>things that make sense. So if you get a little

304
00:16:25.759 --> 00:16:28.600
<v Speaker 4>burned out on one piece, you could probably go pick

305
00:16:28.639 --> 00:16:31.200
<v Speaker 4>up a bug somewhere else and get kind of a

306
00:16:31.240 --> 00:16:34.559
<v Speaker 4>refresher and a little respite from it, and then you

307
00:16:34.840 --> 00:16:36.679
<v Speaker 4>go back to it in a few days time. So

308
00:16:37.440 --> 00:16:41.480
<v Speaker 4>it's kind of like breadth versus depth. And there's small

309
00:16:41.480 --> 00:16:45.360
<v Speaker 4>companies startups still are doing very complex things as well,

310
00:16:45.919 --> 00:16:48.159
<v Speaker 4>but there's still going to be probably a better chance

311
00:16:48.200 --> 00:16:53.159
<v Speaker 4>of you getting more experience in more different things than

312
00:16:53.200 --> 00:16:57.440
<v Speaker 4>there would be on a larger product team in a

313
00:16:57.440 --> 00:16:58.440
<v Speaker 4>big organization.

314
00:16:59.039 --> 00:17:01.799
<v Speaker 2>And there's definitely I mean, when you think about a startup,

315
00:17:01.879 --> 00:17:04.440
<v Speaker 2>right you've got your your seed round startup, and that's

316
00:17:04.839 --> 00:17:07.559
<v Speaker 2>basically pre product market fit, meaning that they still don't

317
00:17:07.559 --> 00:17:09.759
<v Speaker 2>really know what they're doing, and.

318
00:17:09.720 --> 00:17:11.519
<v Speaker 1>That can be wild.

319
00:17:11.960 --> 00:17:15.359
<v Speaker 2>Everything's changing all the time, versus like a C like

320
00:17:15.400 --> 00:17:17.240
<v Speaker 2>a Series A or a Series B or Series C,

321
00:17:17.920 --> 00:17:20.400
<v Speaker 2>where the company knows what it's doing now it's just

322
00:17:20.400 --> 00:17:23.200
<v Speaker 2>a question of like scaling it up and getting to

323
00:17:23.240 --> 00:17:25.200
<v Speaker 2>be larger, and there's a bit more of a of

324
00:17:25.240 --> 00:17:27.599
<v Speaker 2>a comfort zone in there. And then on the big

325
00:17:27.599 --> 00:17:32.440
<v Speaker 2>company side, there's there's tech companies like Google and Facebook,

326
00:17:32.480 --> 00:17:34.519
<v Speaker 2>and these are companies that are have kind of a

327
00:17:34.640 --> 00:17:38.039
<v Speaker 2>cored engineering, like a heart in engineering. And then you've

328
00:17:38.039 --> 00:17:40.480
<v Speaker 2>got your sort of brick and mortar startups like your

329
00:17:40.480 --> 00:17:44.599
<v Speaker 2>home depot, your Walmart, your Nike, where they're companies that

330
00:17:44.720 --> 00:17:50.079
<v Speaker 2>culturally are really about like having a star and you're

331
00:17:50.240 --> 00:17:53.000
<v Speaker 2>like the weird tech folks coming in saying, well, way

332
00:17:53.039 --> 00:17:54.599
<v Speaker 2>we can sell this stuff online?

333
00:17:54.720 --> 00:17:54.960
<v Speaker 1>You know.

334
00:17:55.119 --> 00:17:57.759
<v Speaker 2>So there's definitely when you talk about like the things

335
00:17:57.759 --> 00:17:59.880
<v Speaker 2>to look out for in the interview and questions like that,

336
00:18:00.319 --> 00:18:03.359
<v Speaker 2>got to think about those like where is this company,

337
00:18:03.559 --> 00:18:05.960
<v Speaker 2>what's its background and is.

338
00:18:05.920 --> 00:18:07.839
<v Speaker 1>That going to work within my career? And where I

339
00:18:07.839 --> 00:18:09.240
<v Speaker 1>want to take my career. Yeah.

340
00:18:09.240 --> 00:18:11.440
<v Speaker 3>When I worked in Big Insurance, we had to wear

341
00:18:11.640 --> 00:18:15.519
<v Speaker 3>a shirt and tie into the office every day because

342
00:18:16.160 --> 00:18:19.960
<v Speaker 3>there was an insurance company right the whole it aspect

343
00:18:20.000 --> 00:18:22.200
<v Speaker 3>of it was just one component of it, and it

344
00:18:22.279 --> 00:18:24.640
<v Speaker 3>was just a company policy you wear shirt and tie.

345
00:18:24.759 --> 00:18:27.880
<v Speaker 3>So I got dressed up every day. I was prepared

346
00:18:27.920 --> 00:18:33.200
<v Speaker 3>every uh every like wedding and events like. I was ready, like, man,

347
00:18:33.200 --> 00:18:35.359
<v Speaker 3>I got a full I got a full wardrobe, ready.

348
00:18:35.200 --> 00:18:38.160
<v Speaker 4>For this business, casual, ready for anything.

349
00:18:38.880 --> 00:18:43.720
<v Speaker 1>Yeah. I got a smock at Walmart, a full on smock. Yeah.

350
00:18:43.799 --> 00:18:45.279
<v Speaker 1>And I actually knew the cheer too.

351
00:18:45.720 --> 00:18:46.960
<v Speaker 4>Oh yeah, yeah, I had.

352
00:18:47.160 --> 00:18:49.720
<v Speaker 1>I was a principal engineer. I wasn't anywhere near I

353
00:18:49.720 --> 00:18:51.720
<v Speaker 1>did you know? I would go into the store. I'm like, hey,

354
00:18:51.720 --> 00:18:52.279
<v Speaker 1>I worked there.

355
00:18:52.319 --> 00:18:56.440
<v Speaker 4>I guess home Depot, Apron, the whole nine yards. But before,

356
00:18:56.519 --> 00:19:00.319
<v Speaker 4>right before I got there and got hired, everybody, even

357
00:19:00.480 --> 00:19:03.880
<v Speaker 4>people who worked in our corporate offices, were required I think,

358
00:19:03.920 --> 00:19:07.119
<v Speaker 4>to do maybe three or four store days a year

359
00:19:07.599 --> 00:19:09.440
<v Speaker 4>where they would go in and be on the front

360
00:19:09.480 --> 00:19:12.519
<v Speaker 4>lines helping customers and dealing with all the stuff that

361
00:19:12.559 --> 00:19:16.759
<v Speaker 4>store employees do on a daily basis. And once I

362
00:19:16.920 --> 00:19:20.079
<v Speaker 4>was hired, they had actually made that they had gotten

363
00:19:20.160 --> 00:19:23.319
<v Speaker 4>rid of that as a requirement, So you did your

364
00:19:23.319 --> 00:19:27.480
<v Speaker 4>one store day when you first started, and then pretty

365
00:19:27.519 --> 00:19:30.720
<v Speaker 4>much never again because they wanted you working on whatever

366
00:19:30.759 --> 00:19:32.640
<v Speaker 4>it was that you were actually hired to do. But

367
00:19:32.720 --> 00:19:35.960
<v Speaker 4>I you know, I really enjoyed it, and I think

368
00:19:36.400 --> 00:19:39.200
<v Speaker 4>a lot of people gained a lot more empathy for

369
00:19:39.839 --> 00:19:44.160
<v Speaker 4>the amount of stuff that customer service or customer facing

370
00:19:44.200 --> 00:19:47.440
<v Speaker 4>people put up with on a daily basis, and especially

371
00:19:47.519 --> 00:19:51.200
<v Speaker 4>when it's something like home depot hardware, where people come

372
00:19:51.200 --> 00:19:53.480
<v Speaker 4>in and something is broken off of their window but

373
00:19:53.519 --> 00:19:55.759
<v Speaker 4>they have no idea what it's called. You have no

374
00:19:55.880 --> 00:19:58.799
<v Speaker 4>idea what it's called, You've never even seen this piece before,

375
00:19:59.160 --> 00:20:01.400
<v Speaker 4>and you're expected to try and help them find it

376
00:20:01.440 --> 00:20:04.640
<v Speaker 4>in the store and replace it. So it was a

377
00:20:04.799 --> 00:20:07.480
<v Speaker 4>I think it's a great wake up call for people

378
00:20:07.519 --> 00:20:12.039
<v Speaker 4>who have not worked in customers facing jobs before just

379
00:20:12.119 --> 00:20:15.559
<v Speaker 4>how difficult that can be and how tiring it can be.

380
00:20:16.000 --> 00:20:18.640
<v Speaker 4>But at the same time, I also very much understand

381
00:20:19.079 --> 00:20:22.400
<v Speaker 4>we're paying you a lot more, most likely than we're

382
00:20:22.440 --> 00:20:25.599
<v Speaker 4>paying the store employees, So do your job, whatever it

383
00:20:25.680 --> 00:20:27.240
<v Speaker 4>was we actually hired.

384
00:20:26.960 --> 00:20:30.279
<v Speaker 3>You to do. I do think like it. I don't

385
00:20:30.279 --> 00:20:32.440
<v Speaker 3>know if this is strictly speaking true, but at larger

386
00:20:32.480 --> 00:20:36.359
<v Speaker 3>companies you do feel a little bit more removed from

387
00:20:36.599 --> 00:20:38.839
<v Speaker 3>whatever it is the company is doing. You feel a

388
00:20:38.880 --> 00:20:42.400
<v Speaker 3>bit more like a cog and a giant system. And

389
00:20:42.640 --> 00:20:45.160
<v Speaker 3>I have to imagine that home depot program was trying

390
00:20:45.160 --> 00:20:48.200
<v Speaker 3>to help you rectify that or bring people close to

391
00:20:48.279 --> 00:20:52.319
<v Speaker 3>it to it, because when I worked in commercial automobile insurance,

392
00:20:52.440 --> 00:20:55.920
<v Speaker 3>like I never met anybody that was actually insurance agent

393
00:20:56.119 --> 00:20:59.680
<v Speaker 3>or an actual policy holder, so it was very I

394
00:20:59.799 --> 00:21:03.119
<v Speaker 3>was very far removed. It felt very just esoteric random

395
00:21:03.359 --> 00:21:06.079
<v Speaker 3>stuff I was doing. And it does give you, like

396
00:21:06.200 --> 00:21:09.720
<v Speaker 3>a little bus motivation. It does help when you really

397
00:21:09.759 --> 00:21:12.799
<v Speaker 3>feel like you are doing something important or worthwhile or

398
00:21:12.839 --> 00:21:15.799
<v Speaker 3>have a connection to whatever it is the end product

399
00:21:15.920 --> 00:21:17.480
<v Speaker 3>or service that it is you're producing.

400
00:21:17.880 --> 00:21:19.519
<v Speaker 1>Yeah, that's a big deal.

401
00:21:19.759 --> 00:21:21.640
<v Speaker 2>I mean for me, the reason that I got into

402
00:21:21.839 --> 00:21:24.920
<v Speaker 2>software or writing code when I was kid was I

403
00:21:24.960 --> 00:21:27.000
<v Speaker 2>wanted to make games for my friends, and so it's

404
00:21:27.000 --> 00:21:29.240
<v Speaker 2>been that virtuous cycle. Always wanted to put stuff in

405
00:21:29.279 --> 00:21:32.799
<v Speaker 2>front of people that are like, ooh, that's neat, you know,

406
00:21:32.839 --> 00:21:35.359
<v Speaker 2>and get that little buzz of like wow, I made that,

407
00:21:35.440 --> 00:21:37.640
<v Speaker 2>and people like it, you know. But if you're working

408
00:21:37.680 --> 00:21:39.559
<v Speaker 2>in insurance.

409
00:21:39.960 --> 00:21:43.920
<v Speaker 1>You know, maybe that's not a thing that you know, Wow,

410
00:21:44.000 --> 00:21:48.880
<v Speaker 1>I made rich people a lot richer. Woo you devise

411
00:21:48.960 --> 00:21:53.200
<v Speaker 1>that algorithm? Woo. Yeah I got with an additional point

412
00:21:53.279 --> 00:21:55.599
<v Speaker 1>zero or zero one percent. Yes, yeah.

413
00:21:55.599 --> 00:21:58.000
<v Speaker 2>You know, at the end of the day, you're like, wow,

414
00:21:58.039 --> 00:21:59.759
<v Speaker 2>I want maybe I want something in my life where

415
00:21:59.799 --> 00:22:02.799
<v Speaker 2>I want to give people something, you know, new And

416
00:22:03.599 --> 00:22:06.039
<v Speaker 2>Nike I did this feature where you know, you would

417
00:22:06.079 --> 00:22:09.640
<v Speaker 2>recommend shoes based on the shoes that you'd already bought

418
00:22:09.640 --> 00:22:12.640
<v Speaker 2>and that sort of stuff, and being a person as

419
00:22:12.680 --> 00:22:15.480
<v Speaker 2>a runner with flat feet, that actually was something cool

420
00:22:15.519 --> 00:22:18.599
<v Speaker 2>to me because like, that's a better kind of experience

421
00:22:18.640 --> 00:22:20.200
<v Speaker 2>they might get in a store where you know, you

422
00:22:20.279 --> 00:22:21.799
<v Speaker 2>talk to somebody and you want to get you know,

423
00:22:22.039 --> 00:22:24.240
<v Speaker 2>get some advice. You know, here's an algorithm saying, hey,

424
00:22:24.519 --> 00:22:26.119
<v Speaker 2>you know you bought you know, these kind of motion

425
00:22:26.160 --> 00:22:28.839
<v Speaker 2>petrol shoes whatever. And then I felt like, oh, I

426
00:22:28.839 --> 00:22:30.920
<v Speaker 2>had an impact in somebody's life today, and that's a

427
00:22:30.960 --> 00:22:32.640
<v Speaker 2>good thing. That's a nice way to wake up in

428
00:22:32.680 --> 00:22:34.759
<v Speaker 2>the morning and feel like, ah, you know, I'm changing

429
00:22:34.759 --> 00:22:35.279
<v Speaker 2>in the world this.

430
00:22:35.319 --> 00:22:37.039
<v Speaker 1>A little bit today. Yeah.

431
00:22:37.279 --> 00:22:40.359
<v Speaker 4>That that user feedback that you get if you get it,

432
00:22:40.440 --> 00:22:42.880
<v Speaker 4>if you're lucky enough to be able to see some

433
00:22:43.000 --> 00:22:46.119
<v Speaker 4>of what people say is is awesome. Like the team

434
00:22:46.119 --> 00:22:48.480
<v Speaker 4>that I worked for within Home Depot, we were an

435
00:22:48.480 --> 00:22:52.119
<v Speaker 4>internal team and our clients were actually Home Depot employees

436
00:22:52.160 --> 00:22:56.680
<v Speaker 4>as well, so from time to time they they had

437
00:22:56.680 --> 00:22:58.839
<v Speaker 4>to use our tool to do their jobs and we

438
00:22:58.880 --> 00:23:02.319
<v Speaker 4>would get feedback both negative and positive. But some of

439
00:23:02.480 --> 00:23:05.279
<v Speaker 4>the times when we'd get positive feedback, people would say

440
00:23:05.319 --> 00:23:09.119
<v Speaker 4>things like we'd saved them hours out of their week

441
00:23:09.359 --> 00:23:13.160
<v Speaker 4>with stuff that we had made and done, which was

442
00:23:13.720 --> 00:23:18.119
<v Speaker 4>so rewarding. And that's the kind of thing exactly that

443
00:23:18.279 --> 00:23:21.480
<v Speaker 4>really motivates you. It's like you might not see as

444
00:23:21.519 --> 00:23:25.400
<v Speaker 4>you're building something the benefit or the impact that it's

445
00:23:25.440 --> 00:23:28.759
<v Speaker 4>going to have on somebody else's job, But hearing things

446
00:23:28.839 --> 00:23:32.720
<v Speaker 4>like we'd saved them hours of work a week was awesome.

447
00:23:33.279 --> 00:23:36.839
<v Speaker 4>And that's something that kind of was attractive to me

448
00:23:36.960 --> 00:23:39.880
<v Speaker 4>when I was starting to interview at Blues where I

449
00:23:39.960 --> 00:23:43.680
<v Speaker 4>work now. Was seeing the product that they're making and

450
00:23:43.799 --> 00:23:49.839
<v Speaker 4>hearing how it could improve so much was really enticing.

451
00:23:50.359 --> 00:23:55.519
<v Speaker 4>You know, it's a product that makes it easy to

452
00:23:55.680 --> 00:23:59.880
<v Speaker 4>have an Internet of Things object that doesn't necessarily have

453
00:24:00.079 --> 00:24:03.680
<v Speaker 4>access to Wi Fi. It gives it that cellular connection

454
00:24:03.960 --> 00:24:05.920
<v Speaker 4>so that it can take the data from the sensors

455
00:24:05.920 --> 00:24:08.400
<v Speaker 4>that it's got and send it up to a cloud

456
00:24:08.440 --> 00:24:11.960
<v Speaker 4>really easily. And when you start to think about all

457
00:24:12.039 --> 00:24:15.599
<v Speaker 4>the potential use cases for that and how many people

458
00:24:15.839 --> 00:24:19.160
<v Speaker 4>or how many products it could positively impact, that's really

459
00:24:19.200 --> 00:24:22.759
<v Speaker 4>really cool to think about all the things that it

460
00:24:22.759 --> 00:24:26.279
<v Speaker 4>could help make better and make easier. And that's something

461
00:24:26.279 --> 00:24:27.319
<v Speaker 4>that I wanted to be part of.

462
00:24:28.240 --> 00:24:30.640
<v Speaker 3>Yeah, And I think like that sort of thing doesn't

463
00:24:30.680 --> 00:24:35.000
<v Speaker 3>necessarily have to be a small company big company thing.

464
00:24:35.119 --> 00:24:37.319
<v Speaker 3>I think it's probably easier to be more involved in

465
00:24:37.359 --> 00:24:40.880
<v Speaker 3>a smaller company. But I mean, I've also had experiences

466
00:24:40.880 --> 00:24:44.599
<v Speaker 3>when I worked at Progress and we sold software, but

467
00:24:45.240 --> 00:24:47.559
<v Speaker 3>I very rarely got to see any of the people

468
00:24:47.640 --> 00:24:50.880
<v Speaker 3>using it. So I used to like going to events

469
00:24:50.960 --> 00:24:54.680
<v Speaker 3>like JavaScript events, software events, because sometimes people would come

470
00:24:54.799 --> 00:24:57.519
<v Speaker 3>up to we'd have like booze or just see them

471
00:24:57.559 --> 00:24:59.759
<v Speaker 3>and people would say, Hey, I use your stuff, or

472
00:25:00.000 --> 00:25:03.400
<v Speaker 3>I've read your blog post, and it's it's an amazing

473
00:25:03.599 --> 00:25:06.960
<v Speaker 3>like just jolt you get because lots of times when

474
00:25:07.000 --> 00:25:08.920
<v Speaker 3>you do stuff like that, you put work out into

475
00:25:08.960 --> 00:25:11.720
<v Speaker 3>the ether and unless somebody tells you, you just kind

476
00:25:11.720 --> 00:25:14.640
<v Speaker 3>of assumed well, it's out there, and who knows if

477
00:25:14.640 --> 00:25:16.640
<v Speaker 3>anybody's going to see this or do anything with it.

478
00:25:17.119 --> 00:25:22.359
<v Speaker 3>So just getting that, like that reassurance that your work

479
00:25:22.400 --> 00:25:26.200
<v Speaker 3>actually is being used, you have a purpose in life

480
00:25:26.200 --> 00:25:26.880
<v Speaker 3>at least for this.

481
00:25:27.079 --> 00:25:29.960
<v Speaker 4>So, yeah, you can feel like you're screaming into the

482
00:25:30.000 --> 00:25:33.440
<v Speaker 4>voids sometimes when you're writing content and nobody comments or

483
00:25:33.480 --> 00:25:35.559
<v Speaker 4>shares or just even likes it.

484
00:25:36.720 --> 00:25:40.359
<v Speaker 1>Yeah exactly, I felt that before. Yeah, Well, so.

485
00:25:40.359 --> 00:25:42.759
<v Speaker 2>That actually brings an interesting point, which is, I think

486
00:25:42.759 --> 00:25:46.319
<v Speaker 2>it's undervalue that engineers need to market themselves. It's a

487
00:25:46.319 --> 00:25:48.759
<v Speaker 2>lot easier to get a job when the company's coming

488
00:25:48.960 --> 00:25:52.319
<v Speaker 2>after you as opposed to you going and wanting to

489
00:25:52.359 --> 00:25:54.920
<v Speaker 2>work at a company, right, so that there's a great

490
00:25:54.920 --> 00:25:58.759
<v Speaker 2>incentive that's going a different way. And to get there, right,

491
00:25:58.759 --> 00:26:01.200
<v Speaker 2>you got to build an aim for yourself, and that

492
00:26:01.400 --> 00:26:04.359
<v Speaker 2>is in some senses a risk at a big company,

493
00:26:04.359 --> 00:26:07.759
<v Speaker 2>because big companies are gonna have you know, closed source systems,

494
00:26:08.480 --> 00:26:10.319
<v Speaker 2>and unless you're going to get on an open source

495
00:26:10.359 --> 00:26:14.640
<v Speaker 2>project that is well well supported inside of a big company,

496
00:26:14.680 --> 00:26:18.440
<v Speaker 2>lots of big companies start oss and then just let

497
00:26:18.480 --> 00:26:21.920
<v Speaker 2>it die in the search for you know, profit, which

498
00:26:21.960 --> 00:26:24.319
<v Speaker 2>is of course important, but you know, that kind of

499
00:26:24.400 --> 00:26:26.279
<v Speaker 2>thing you want, you're going to be able to build

500
00:26:26.319 --> 00:26:30.960
<v Speaker 2>up some blog posts and content around your resume. I

501
00:26:30.960 --> 00:26:33.160
<v Speaker 2>think maybe a little bit more at the tech company

502
00:26:33.720 --> 00:26:37.559
<v Speaker 2>or at the like smaller medium sized company that's kind

503
00:26:37.559 --> 00:26:39.880
<v Speaker 2>of doing some innovative work and wants to put something

504
00:26:39.880 --> 00:26:41.839
<v Speaker 2>out in open source, maybe get a little buzz better

505
00:26:41.880 --> 00:26:45.559
<v Speaker 2>for recruiting. And I think there's many more opportunities for well, sorry,

506
00:26:45.599 --> 00:26:50.720
<v Speaker 2>but like selfless self promotion at like in some of

507
00:26:50.720 --> 00:26:52.160
<v Speaker 2>these companies. And that's the thing to keep you an

508
00:26:52.200 --> 00:26:55.240
<v Speaker 2>eye out for, because you do have to promote yourself.

509
00:26:55.480 --> 00:26:55.880
<v Speaker 3>You do.

510
00:26:56.240 --> 00:27:00.160
<v Speaker 4>And that was something that I got that another scene

511
00:27:00.240 --> 00:27:03.359
<v Speaker 4>developer told me pretty early on in my career, maybe

512
00:27:03.359 --> 00:27:06.359
<v Speaker 4>i'd been working for about a year, year and a half,

513
00:27:06.960 --> 00:27:10.319
<v Speaker 4>and he made the comment that I really, if I

514
00:27:10.359 --> 00:27:14.279
<v Speaker 4>wanted to kind of show my cred, especially because I

515
00:27:14.319 --> 00:27:17.799
<v Speaker 4>didn't have a computer science background or degree, I was

516
00:27:17.839 --> 00:27:20.319
<v Speaker 4>going to need to or it would really benefit me

517
00:27:20.680 --> 00:27:23.599
<v Speaker 4>to start writing about what I was learning at work.

518
00:27:23.880 --> 00:27:27.039
<v Speaker 4>And even though I worked on an internal tool, I

519
00:27:27.119 --> 00:27:30.240
<v Speaker 4>found plenty of opportunities to take what I had learned

520
00:27:30.640 --> 00:27:34.680
<v Speaker 4>and change it into something that I didn't use our

521
00:27:35.000 --> 00:27:38.119
<v Speaker 4>internal source code for, you know, I could make a

522
00:27:38.240 --> 00:27:41.240
<v Speaker 4>much smaller example that I would put into my own

523
00:27:41.279 --> 00:27:44.480
<v Speaker 4>GitHub repo and then put out in the community that

524
00:27:44.680 --> 00:27:48.920
<v Speaker 4>was free of all the home depot specific ip or

525
00:27:48.960 --> 00:27:51.039
<v Speaker 4>I would just take a concept that I had learned

526
00:27:51.079 --> 00:27:55.680
<v Speaker 4>about and create some small, much simplified version of it,

527
00:27:56.200 --> 00:28:00.000
<v Speaker 4>or even even stuff that I had built inside projects

528
00:28:00.160 --> 00:28:02.839
<v Speaker 4>was a great one that I would be able to

529
00:28:02.960 --> 00:28:05.359
<v Speaker 4>use because they were it was my own code, and

530
00:28:05.400 --> 00:28:07.599
<v Speaker 4>I would, you know, I would refer back to stuff

531
00:28:07.640 --> 00:28:09.559
<v Speaker 4>that we had done at work to figure out how

532
00:28:09.559 --> 00:28:11.680
<v Speaker 4>to make it work for my side project. But it

533
00:28:11.799 --> 00:28:15.119
<v Speaker 4>was all written by me and my own stuff. But

534
00:28:15.200 --> 00:28:19.400
<v Speaker 4>that was a huge, huge thing, I think in helping

535
00:28:19.480 --> 00:28:22.319
<v Speaker 4>me get further in my career because it was something

536
00:28:22.359 --> 00:28:24.880
<v Speaker 4>that I could point to internally when somebody would have

537
00:28:24.920 --> 00:28:26.680
<v Speaker 4>a question, I'd be like, oh, I wrote a blog

538
00:28:26.720 --> 00:28:29.400
<v Speaker 4>post about that, and so you know, people on my

539
00:28:29.440 --> 00:28:31.960
<v Speaker 4>team could benefit from it. My managers could see that

540
00:28:32.000 --> 00:28:35.839
<v Speaker 4>I was doing it. It helped kind of solidify yes,

541
00:28:36.200 --> 00:28:38.319
<v Speaker 4>I do know what I'm talking about, and I have

542
00:28:38.799 --> 00:28:41.839
<v Speaker 4>at least learned enough to be able to write and

543
00:28:41.960 --> 00:28:45.279
<v Speaker 4>teach somebody else about it. But it also was an

544
00:28:45.319 --> 00:28:48.960
<v Speaker 4>outside signal to people outside of the company. That I

545
00:28:49.160 --> 00:28:52.759
<v Speaker 4>was doing good things and giving back to the community

546
00:28:52.799 --> 00:28:55.359
<v Speaker 4>in this way and making my way.

547
00:28:55.200 --> 00:28:55.640
<v Speaker 1>And I am.

548
00:28:56.279 --> 00:28:58.599
<v Speaker 4>I know that. Because of that kind of stuff, I

549
00:28:58.640 --> 00:29:03.119
<v Speaker 4>started getting opportunityes, Like a couple of software's and service

550
00:29:03.160 --> 00:29:05.799
<v Speaker 4>companies asked me, after I'd been publishing for probably a

551
00:29:05.839 --> 00:29:08.599
<v Speaker 4>couple of years just on my own, if I'd like

552
00:29:08.680 --> 00:29:11.000
<v Speaker 4>to write for their publications, and they paid me to

553
00:29:11.000 --> 00:29:14.240
<v Speaker 4>do it. And then I was invited onto one of

554
00:29:14.279 --> 00:29:18.000
<v Speaker 4>the podcasts here because I'd written an article for log Rocket,

555
00:29:18.160 --> 00:29:21.319
<v Speaker 4>and suddenly I was on JavaScript Jabber, which is a

556
00:29:21.359 --> 00:29:24.960
<v Speaker 4>sister podcast of ours, talking about it. And then I

557
00:29:25.000 --> 00:29:28.319
<v Speaker 4>was invited to React Roundup because I'd done a conference

558
00:29:28.359 --> 00:29:31.640
<v Speaker 4>talk on responsive design and React and that had been

559
00:29:31.759 --> 00:29:35.440
<v Speaker 4>picked up by one of the newsletter publications. So that

560
00:29:35.559 --> 00:29:38.680
<v Speaker 4>kind of stuff not only does it build your credibility

561
00:29:38.920 --> 00:29:42.640
<v Speaker 4>and give you a platform which a lot of other

562
00:29:42.839 --> 00:29:47.119
<v Speaker 4>developers are not doing, so it's a huge visibility booster there,

563
00:29:47.400 --> 00:29:51.599
<v Speaker 4>but it also can potentially lead to paid speaking engagements,

564
00:29:51.720 --> 00:29:55.920
<v Speaker 4>paid writing engagements, new jobs because somebody saw that you

565
00:29:56.039 --> 00:29:58.240
<v Speaker 4>did X, Y and Z and they're like, I need

566
00:29:58.279 --> 00:30:00.880
<v Speaker 4>somebody here to do X, Y and Z. Also, it's

567
00:30:01.319 --> 00:30:06.480
<v Speaker 4>ridiculous how if you're consistently doing stuff like that, you

568
00:30:06.519 --> 00:30:10.319
<v Speaker 4>can turn it into something much bigger than what it

569
00:30:10.400 --> 00:30:11.200
<v Speaker 4>started out as.

570
00:30:11.720 --> 00:30:14.240
<v Speaker 3>Yeah, And I feel like because I had a similar

571
00:30:14.319 --> 00:30:16.920
<v Speaker 3>journey in terms of working on my own to you

572
00:30:16.920 --> 00:30:19.680
<v Speaker 3>get my name out from outside of a big company.

573
00:30:19.960 --> 00:30:22.599
<v Speaker 3>And the thing is you do have to jump through

574
00:30:22.640 --> 00:30:24.599
<v Speaker 3>some hoops because I had to do some similar things,

575
00:30:24.720 --> 00:30:28.079
<v Speaker 3>Like you're very careful to make sure you're not using

576
00:30:28.240 --> 00:30:31.920
<v Speaker 3>any code that it was originally there. You almost like

577
00:30:32.039 --> 00:30:35.240
<v Speaker 3>feel like awkward, you're foresuer doing all of this on

578
00:30:35.319 --> 00:30:38.039
<v Speaker 3>your free time, not as part of your work time.

579
00:30:38.640 --> 00:30:40.839
<v Speaker 3>And I feel like in a startup, there's because there's

580
00:30:41.000 --> 00:30:45.240
<v Speaker 3>less bureaucracy, you have more ability to get your name

581
00:30:45.319 --> 00:30:47.680
<v Speaker 3>out for sure, because you have more freedom to work

582
00:30:47.680 --> 00:30:50.440
<v Speaker 3>on stuff you're interested in and therefore more willing to

583
00:30:50.480 --> 00:30:53.920
<v Speaker 3>write about. Small companies in general aren't going to care, like,

584
00:30:54.359 --> 00:30:56.359
<v Speaker 3>you know, lose my care if you take like an

585
00:30:56.480 --> 00:30:58.720
<v Speaker 3>entire section of code you've been working on for a

586
00:30:58.759 --> 00:31:00.720
<v Speaker 3>long time and throw it out there. But if you're

587
00:31:00.759 --> 00:31:03.000
<v Speaker 3>just referencing something you did, it's like, oh, that's like

588
00:31:03.079 --> 00:31:06.440
<v Speaker 3>good pr Probably like putting the name out there, it's

589
00:31:06.519 --> 00:31:09.319
<v Speaker 3>it's not a big deal. There's there's less concerns, So

590
00:31:09.920 --> 00:31:13.200
<v Speaker 3>I feel like you definitely do have more freedom at

591
00:31:13.200 --> 00:31:16.240
<v Speaker 3>a smaller company to try to make a name for

592
00:31:16.279 --> 00:31:19.079
<v Speaker 3>yourself than you do instead of like a giant organization.

593
00:31:19.480 --> 00:31:22.359
<v Speaker 2>Yeah, I think page you put like a great recipe

594
00:31:22.400 --> 00:31:25.759
<v Speaker 2>there for just starting out and getting into it. You know, Hey,

595
00:31:25.799 --> 00:31:28.240
<v Speaker 2>I ran into this little thing. I'm going to go

596
00:31:28.319 --> 00:31:30.640
<v Speaker 2>and you know, do a quick dev too on how

597
00:31:30.680 --> 00:31:33.480
<v Speaker 2>to fix this one particular issue, and you'll end up

598
00:31:33.480 --> 00:31:35.160
<v Speaker 2>in a bunch of Google searches because other people will

599
00:31:35.160 --> 00:31:37.160
<v Speaker 2>get stuck on and be like, oh, yeah, you know

600
00:31:37.279 --> 00:31:39.839
<v Speaker 2>that guy's you know, I've got a good, you know,

601
00:31:40.200 --> 00:31:42.359
<v Speaker 2>recipe for how to get around that, and then it

602
00:31:42.440 --> 00:31:44.000
<v Speaker 2>kind of builds on it and you get more and

603
00:31:44.000 --> 00:31:45.880
<v Speaker 2>more exposure and that's great.

604
00:31:46.480 --> 00:31:46.680
<v Speaker 1>Yeah.

605
00:31:46.720 --> 00:31:49.039
<v Speaker 2>So yeah, a really good recipe there to get into

606
00:31:49.039 --> 00:31:51.240
<v Speaker 2>the world of self marketing.

607
00:31:51.519 --> 00:31:51.720
<v Speaker 1>Yeah.

608
00:31:51.759 --> 00:31:53.960
<v Speaker 4>I mean, I just have a note on my phone.

609
00:31:54.079 --> 00:31:57.200
<v Speaker 4>It's the most basic thing ever of stuff that I

610
00:31:57.240 --> 00:32:00.640
<v Speaker 4>have figured out how to do, either through work, through projects,

611
00:32:00.640 --> 00:32:02.839
<v Speaker 4>and when I come across something else that I think

612
00:32:02.880 --> 00:32:05.160
<v Speaker 4>would be interesting or that I think other people would

613
00:32:05.279 --> 00:32:07.519
<v Speaker 4>like to see how I did it, I'll just write

614
00:32:07.519 --> 00:32:09.240
<v Speaker 4>it down as a note to myself, and then when

615
00:32:09.240 --> 00:32:11.359
<v Speaker 4>I'm when I have time and when I'm looking for

616
00:32:11.400 --> 00:32:13.680
<v Speaker 4>something to write about, I'll just reference back to that

617
00:32:13.799 --> 00:32:16.720
<v Speaker 4>and pick one of the topics that still sounds good.

618
00:32:17.079 --> 00:32:19.400
<v Speaker 4>And it's a great jumping off point because I know

619
00:32:19.440 --> 00:32:21.000
<v Speaker 4>a lot of people struggle with, well what am I

620
00:32:21.039 --> 00:32:23.200
<v Speaker 4>going to write about? Well, what are you doing all day?

621
00:32:23.319 --> 00:32:27.079
<v Speaker 4>You're probably solving interesting problems. So just kind of try

622
00:32:27.119 --> 00:32:30.920
<v Speaker 4>and keep a reminder to yourself of something interesting that

623
00:32:31.000 --> 00:32:34.359
<v Speaker 4>you solved. You know, probably somebody else, you know, they'll

624
00:32:34.440 --> 00:32:36.920
<v Speaker 4>run up against it too. You're probably not the only

625
00:32:36.960 --> 00:32:39.400
<v Speaker 4>person who will meet this particular thing.

626
00:32:39.720 --> 00:32:43.160
<v Speaker 3>Yeah, And honestly, if you're not solving interesting problems, then

627
00:32:43.160 --> 00:32:46.200
<v Speaker 3>it might be time to consider, right, Like, there's it's

628
00:32:46.240 --> 00:32:49.119
<v Speaker 3>a great it's a higher you know, there's a good

629
00:32:49.119 --> 00:32:51.400
<v Speaker 3>time to be a software developer. That's what I'm what

630
00:32:51.440 --> 00:32:55.039
<v Speaker 3>I'm getting at. There are opportunities out there, so the

631
00:32:55.119 --> 00:32:58.000
<v Speaker 3>interesting problems don't have to be you know, the world's

632
00:32:58.000 --> 00:33:00.519
<v Speaker 3>most inventive startup, like you're at the next there, BnB

633
00:33:00.599 --> 00:33:02.960
<v Speaker 3>and Uber. You can have interesting problems to solve in

634
00:33:03.000 --> 00:33:06.079
<v Speaker 3>all sorts of markets, Like there were certainly interesting insurance problems.

635
00:33:06.079 --> 00:33:09.920
<v Speaker 3>I'm sure there are interesting home depot problems, Nike problems

636
00:33:10.039 --> 00:33:13.920
<v Speaker 3>as well, because those types of companies have like there's

637
00:33:13.920 --> 00:33:16.119
<v Speaker 3>something to be said about solving something at those sorts

638
00:33:16.119 --> 00:33:18.559
<v Speaker 3>of scales as well, like you really do have the

639
00:33:18.599 --> 00:33:22.119
<v Speaker 3>potential to touch a lot of people to make a difference,

640
00:33:22.200 --> 00:33:26.960
<v Speaker 3>Like it's it is funny because bigger companies also tend

641
00:33:26.960 --> 00:33:30.240
<v Speaker 3>to have more ceremony and process, but that's somewhat for

642
00:33:30.279 --> 00:33:32.599
<v Speaker 3>a reason, Like sometimes you get to deal with some

643
00:33:32.680 --> 00:33:38.160
<v Speaker 3>interesting problems of hitting sometimes huge user bases and large

644
00:33:38.240 --> 00:33:40.759
<v Speaker 3>data sets that you're going to have trouble finding at

645
00:33:40.799 --> 00:33:43.440
<v Speaker 3>a startup, So sometimes you can find some unique and

646
00:33:43.440 --> 00:33:45.279
<v Speaker 3>interesting problems to solve at big companies.

647
00:33:45.319 --> 00:33:49.079
<v Speaker 4>Also, Oh absolutely, one of the ones that springs to

648
00:33:49.119 --> 00:33:52.880
<v Speaker 4>mind immediately that was pretty new when I left, or

649
00:33:53.240 --> 00:33:57.079
<v Speaker 4>have been solved recently, was we had some product data

650
00:33:57.440 --> 00:34:02.440
<v Speaker 4>that was two hundred and fifty thousand potential rows in

651
00:34:02.519 --> 00:34:05.480
<v Speaker 4>an Excel spreadsheet that we either needed to upload and

652
00:34:05.720 --> 00:34:08.920
<v Speaker 4>ingest into our system or make downloadable for the user.

653
00:34:09.280 --> 00:34:14.159
<v Speaker 4>So yeah, those were nightmare things to solve, but our

654
00:34:14.239 --> 00:34:17.480
<v Speaker 4>users lived and died by these Excel spreadsheets, so it

655
00:34:17.559 --> 00:34:20.519
<v Speaker 4>wasn't even a question of if we could make this work.

656
00:34:20.559 --> 00:34:22.760
<v Speaker 4>It was more how do we make this work? Because

657
00:34:23.039 --> 00:34:26.119
<v Speaker 4>it needs to work. It was just so, yeah, those

658
00:34:26.119 --> 00:34:30.199
<v Speaker 4>are ridiculous problems. But because it was a larger company

659
00:34:30.280 --> 00:34:33.800
<v Speaker 4>and has been around for forty years, you couldn't just

660
00:34:33.960 --> 00:34:36.320
<v Speaker 4>say we're not going to support this anymore because the

661
00:34:36.440 --> 00:34:39.119
<v Speaker 4>users would mutiny and come with us, come at us

662
00:34:39.119 --> 00:34:43.079
<v Speaker 4>with pitchfork. So yeah, there were definitely lots of weird,

663
00:34:43.199 --> 00:34:46.960
<v Speaker 4>interesting problems that had to be solved. But at the

664
00:34:47.000 --> 00:34:50.119
<v Speaker 4>same time, these are the same kind of problems that

665
00:34:50.159 --> 00:34:54.360
<v Speaker 4>I know other companies of large scale and maybe older

666
00:34:54.599 --> 00:34:57.599
<v Speaker 4>are also struggling with. Not everybody can start out as

667
00:34:57.639 --> 00:35:01.840
<v Speaker 4>Google and just be all information systems data from the

668
00:35:01.920 --> 00:35:04.679
<v Speaker 4>get go. There's lots and lots of brick and mortar

669
00:35:04.719 --> 00:35:08.559
<v Speaker 4>stores that are struggling with legacy systems and old processes

670
00:35:08.679 --> 00:35:12.800
<v Speaker 4>that they can't just shut down. They have to revamp

671
00:35:12.880 --> 00:35:15.280
<v Speaker 4>them and make them bring them into the twenty first century,

672
00:35:15.280 --> 00:35:18.800
<v Speaker 4>but also support the older way of doing stuff. Well,

673
00:35:18.840 --> 00:35:20.800
<v Speaker 4>one thing that I wanted to bring up that I

674
00:35:21.519 --> 00:35:24.039
<v Speaker 4>don't think we've really talked about is the various sorts

675
00:35:24.079 --> 00:35:26.960
<v Speaker 4>of roles that you can have at different companies like

676
00:35:28.119 --> 00:35:31.519
<v Speaker 4>a large store or a large company like home depot

677
00:35:32.079 --> 00:35:35.360
<v Speaker 4>because of what they do, they're not going to have

678
00:35:35.480 --> 00:35:39.440
<v Speaker 4>things like developer relations that they just don't need it

679
00:35:39.480 --> 00:35:42.840
<v Speaker 4>because they're selling hammers and they're selling chainsaws and they're

680
00:35:42.880 --> 00:35:47.000
<v Speaker 4>selling mails. But if you want to be maybe a

681
00:35:47.039 --> 00:35:50.400
<v Speaker 4>site reliability engineer, they definitely have a team that is

682
00:35:50.480 --> 00:35:53.880
<v Speaker 4>all about that, making sure that the infrastructure underneath all

683
00:35:53.880 --> 00:35:57.719
<v Speaker 4>these applications is stable and sound and scaling and doing

684
00:35:57.760 --> 00:36:03.000
<v Speaker 4>everything that it needs to where like Blues, developer relations

685
00:36:03.119 --> 00:36:06.679
<v Speaker 4>is a huge part of our culture because we want

686
00:36:06.719 --> 00:36:10.400
<v Speaker 4>developers to really like using our products and to think

687
00:36:10.440 --> 00:36:14.360
<v Speaker 4>of us when they're looking at their next IoT initiative

688
00:36:14.880 --> 00:36:17.519
<v Speaker 4>and evaluating the options that are out there. So it

689
00:36:17.559 --> 00:36:20.599
<v Speaker 4>also really depends like where where do you want your

690
00:36:20.639 --> 00:36:23.960
<v Speaker 4>career to go. Do you want to specialize in a

691
00:36:24.039 --> 00:36:27.119
<v Speaker 4>large company where you can be a real subject matter

692
00:36:27.199 --> 00:36:30.960
<v Speaker 4>expert in a particular area or field, or do you

693
00:36:31.039 --> 00:36:33.360
<v Speaker 4>want to be out in front of the public because

694
00:36:33.360 --> 00:36:35.639
<v Speaker 4>that might make it more sense to be at a

695
00:36:35.639 --> 00:36:38.519
<v Speaker 4>smaller company trying to get help get the company's name

696
00:36:38.559 --> 00:36:41.480
<v Speaker 4>out at the same time as you're making a name

697
00:36:41.519 --> 00:36:44.559
<v Speaker 4>for yourself at that company. So it's there's a lot

698
00:36:44.639 --> 00:36:48.119
<v Speaker 4>of different things to consider based on where you want

699
00:36:48.159 --> 00:36:48.920
<v Speaker 4>to go next.

700
00:36:49.119 --> 00:36:51.800
<v Speaker 3>I guess yeah, I'm just thinking, look at Progress. We

701
00:36:51.960 --> 00:36:55.360
<v Speaker 3>had an SEO team with like a handful of people

702
00:36:55.400 --> 00:36:58.639
<v Speaker 3>that just specialized in that, and thinking, like the smaller

703
00:36:58.679 --> 00:37:00.880
<v Speaker 3>companies have worked for a blue like there there is

704
00:37:00.920 --> 00:37:04.320
<v Speaker 3>no SEO team, there's no SEO person, Like, it's si

705
00:37:04.519 --> 00:37:06.440
<v Speaker 3>SEO is going to be what it is, right like,

706
00:37:07.000 --> 00:37:09.920
<v Speaker 3>so I think get bigger roles just because there's there's

707
00:37:09.960 --> 00:37:14.320
<v Speaker 3>more people, there's naturally going to be more specialization. I mean,

708
00:37:14.360 --> 00:37:17.199
<v Speaker 3>I've worked at bigger companies that had like people that

709
00:37:17.280 --> 00:37:20.480
<v Speaker 3>their entire job was specializing in one database. They were

710
00:37:20.519 --> 00:37:23.920
<v Speaker 3>just the database person for that technology. They knew it

711
00:37:24.000 --> 00:37:26.440
<v Speaker 3>in and out, and that database was important enough to

712
00:37:26.440 --> 00:37:30.920
<v Speaker 3>the company to hire someone specifically for that. So if

713
00:37:30.960 --> 00:37:33.119
<v Speaker 3>that's your thing, like, if you have a niche that

714
00:37:33.239 --> 00:37:37.119
<v Speaker 3>you love, that's your life's passion, you probably can find

715
00:37:37.159 --> 00:37:38.760
<v Speaker 3>a role for it at a larger company, or at

716
00:37:38.800 --> 00:37:40.079
<v Speaker 3>least you're probably more likely to.

717
00:37:40.559 --> 00:37:42.639
<v Speaker 2>I've always been impressed by that. I was a guy

718
00:37:42.679 --> 00:37:44.360
<v Speaker 2>a company I was working on who was the my

719
00:37:44.519 --> 00:37:47.920
<v Speaker 2>sqel guy just straight up like that is what he knew.

720
00:37:49.159 --> 00:37:52.639
<v Speaker 2>He knew every single look and cranny of my sequel

721
00:37:52.840 --> 00:37:55.320
<v Speaker 2>and down to like the dot the triple Dot version

722
00:37:55.320 --> 00:37:58.639
<v Speaker 2>of Patch releases, right, But you know you're like, well,

723
00:37:58.639 --> 00:38:01.079
<v Speaker 2>what happens when if my sequel isn't around anymore?

724
00:38:01.119 --> 00:38:02.840
<v Speaker 1>I not that it won't I'm not saying it won't be.

725
00:38:02.920 --> 00:38:04.800
<v Speaker 2>I'm just like putting it out there, like I think

726
00:38:04.800 --> 00:38:08.559
<v Speaker 2>about it as a career longevity thing, and it's like, no,

727
00:38:08.639 --> 00:38:10.519
<v Speaker 2>it's always going to be. And it's like, wow, that

728
00:38:10.639 --> 00:38:15.320
<v Speaker 2>is an impressive amount of dedication to a very very

729
00:38:15.360 --> 00:38:18.079
<v Speaker 2>focused piece of it. But then again, you know you

730
00:38:18.159 --> 00:38:20.920
<v Speaker 2>do that and if that's your gig, I mean I'm

731
00:38:20.920 --> 00:38:22.960
<v Speaker 2>guessing you probably get paid some decent money for that.

732
00:38:23.400 --> 00:38:25.760
<v Speaker 3>Oh yeah, and if you do the work as you

733
00:38:25.760 --> 00:38:28.159
<v Speaker 3>said earlier, to like be able to pro public profile

734
00:38:28.199 --> 00:38:30.920
<v Speaker 3>around it. If you need a MySQL specialist, because you know,

735
00:38:31.039 --> 00:38:33.519
<v Speaker 3>some big company somewhere is going to hit some MySQL

736
00:38:33.599 --> 00:38:35.840
<v Speaker 3>airs over and over again and do a Google search

737
00:38:35.880 --> 00:38:40.159
<v Speaker 3>to look for someone right there, you'll be exactly Yeah.

738
00:38:40.199 --> 00:38:43.119
<v Speaker 4>I had a friend, a coworker at my old job,

739
00:38:43.159 --> 00:38:46.000
<v Speaker 4>and he would tell me about a previous company he'd

740
00:38:46.039 --> 00:38:48.599
<v Speaker 4>worked for and they had the coball guy and the

741
00:38:48.639 --> 00:38:51.599
<v Speaker 4>Cobyal guy only came in like two weeks out of

742
00:38:51.599 --> 00:38:55.360
<v Speaker 4>the year to maintain their mission critical co ball system.

743
00:38:56.000 --> 00:38:59.000
<v Speaker 4>But he got paid big bucks because he was one

744
00:38:59.039 --> 00:39:02.639
<v Speaker 4>of the few who still nose cobaal and like I said,

745
00:39:02.719 --> 00:39:06.280
<v Speaker 4>only had to work a minuscule amount of time. So

746
00:39:06.480 --> 00:39:08.320
<v Speaker 4>if you want to be if you want to go

747
00:39:08.360 --> 00:39:12.119
<v Speaker 4>into one of those archaic languages that are still powering

748
00:39:12.239 --> 00:39:15.880
<v Speaker 4>so much of our industry, it's probably not a bad idea.

749
00:39:16.280 --> 00:39:19.480
<v Speaker 4>But if you like being on the newer side of

750
00:39:19.519 --> 00:39:22.719
<v Speaker 4>the technology, which will give you a lot more job options, probably,

751
00:39:22.760 --> 00:39:26.239
<v Speaker 4>I mean, he had job security forever because this system

752
00:39:26.960 --> 00:39:30.719
<v Speaker 4>needed to exist and needed to be maintained. But you

753
00:39:30.840 --> 00:39:33.840
<v Speaker 4>probably want to have a more flexible, more up to

754
00:39:33.920 --> 00:39:36.679
<v Speaker 4>date skill set if you plan on being in this

755
00:39:36.840 --> 00:39:41.280
<v Speaker 4>industry for another twenty thirty years. But yeah, there's definitely

756
00:39:41.320 --> 00:39:43.400
<v Speaker 4>a place for those people, for sure.

757
00:39:44.639 --> 00:39:45.880
<v Speaker 1>And that's an interesting point, right.

758
00:39:46.159 --> 00:39:48.800
<v Speaker 2>People seem to think about well when they look at

759
00:39:49.079 --> 00:39:51.480
<v Speaker 2>one of these jobs as maybe an eight to five job,

760
00:39:51.800 --> 00:39:55.320
<v Speaker 2>And I really don't think that technology is an eight

761
00:39:55.360 --> 00:39:58.280
<v Speaker 2>to five job. You have to go after hours and

762
00:39:58.360 --> 00:40:01.760
<v Speaker 2>train yourself and keep up with the new technologies. It's

763
00:40:02.079 --> 00:40:05.599
<v Speaker 2>there's just more to it than that, and it's we

764
00:40:05.639 --> 00:40:07.199
<v Speaker 2>get paid a lot of money, And there's a good

765
00:40:07.239 --> 00:40:09.159
<v Speaker 2>reason that we get paid a lot of money, and

766
00:40:09.239 --> 00:40:13.760
<v Speaker 2>it's because not necessarily just overworking, but like you have

767
00:40:13.840 --> 00:40:17.360
<v Speaker 2>to make sure that you are also driving your own

768
00:40:17.400 --> 00:40:20.239
<v Speaker 2>technology in your own career, and that's going to push

769
00:40:20.320 --> 00:40:22.280
<v Speaker 2>beyond an a defined boundary.

770
00:40:22.559 --> 00:40:24.440
<v Speaker 3>Yeah, it sort of depends on what you want, right,

771
00:40:24.559 --> 00:40:28.000
<v Speaker 3>Like there are certainly people that I have friends that

772
00:40:28.039 --> 00:40:31.360
<v Speaker 3>are working in big insurance still and are still doing

773
00:40:31.440 --> 00:40:34.719
<v Speaker 3>the same nine to five job. And there's something to

774
00:40:34.719 --> 00:40:37.679
<v Speaker 3>be said of just finding a comfortable place that's something

775
00:40:37.679 --> 00:40:40.800
<v Speaker 3>that you enjoy doing, because there are certainly roles that

776
00:40:40.840 --> 00:40:43.519
<v Speaker 3>you can keep doing without having to do the grind,

777
00:40:43.559 --> 00:40:45.440
<v Speaker 3>and you might not get as far into your career,

778
00:40:45.519 --> 00:40:48.880
<v Speaker 3>but it's just what you're comfortable doing. So it's it's

779
00:40:48.880 --> 00:40:51.639
<v Speaker 3>about finding what you want to accomplish and then you know,

780
00:40:51.760 --> 00:40:54.400
<v Speaker 3>valuating your options and trying to figure out how to

781
00:40:54.480 --> 00:40:57.960
<v Speaker 3>get there. And definitely say that those jobs exist in

782
00:40:57.199 --> 00:41:03.119
<v Speaker 3>the larger company, Yeah, companies that almost expected that you have.

783
00:41:03.280 --> 00:41:07.119
<v Speaker 3>You're you're passionate about technology and always learning and that

784
00:41:07.119 --> 00:41:08.840
<v Speaker 3>sort of stuff. I remember when I was working a

785
00:41:09.039 --> 00:41:10.800
<v Speaker 3>name which is a host of the social network company

786
00:41:10.800 --> 00:41:13.320
<v Speaker 3>and Steve jobs is still around. I mean, the entire

787
00:41:13.440 --> 00:41:17.719
<v Speaker 3>company would shut down for watching that keynote because we're

788
00:41:17.719 --> 00:41:19.679
<v Speaker 3>all just glued about what was going to come out

789
00:41:19.719 --> 00:41:22.559
<v Speaker 3>of WILLI Wan because chocolate factory, you know, this year,

790
00:41:23.440 --> 00:41:26.159
<v Speaker 3>and and you go into bigger companies and they're like, well,

791
00:41:26.199 --> 00:41:27.239
<v Speaker 3>you know, it's Apple release day.

792
00:41:27.239 --> 00:41:28.199
<v Speaker 1>What are we doing? They're like, what.

793
00:41:29.840 --> 00:41:33.320
<v Speaker 2>Nothing the other day at the office, dude, Yeah, yep,

794
00:41:33.440 --> 00:41:35.599
<v Speaker 2>all right, well this has been absolutely wonderful.

795
00:41:35.920 --> 00:41:39.000
<v Speaker 1>Let's talk about picks. Anymody got one?

796
00:41:39.280 --> 00:41:41.199
<v Speaker 3>Yeah, I can go first. So I'm going to pick

797
00:41:41.320 --> 00:41:45.480
<v Speaker 3>a app for the Mac called Rocket, and it's an

798
00:41:45.519 --> 00:41:48.800
<v Speaker 3>app to but you drop in emoji in any application.

799
00:41:49.400 --> 00:41:53.920
<v Speaker 3>You essentially hit colon. You have to give your Mac

800
00:41:54.000 --> 00:41:57.280
<v Speaker 3>like full accessibility access to this app, but you just

801
00:41:57.320 --> 00:42:00.360
<v Speaker 3>type of colon in any application anywhere where you can type,

802
00:42:00.360 --> 00:42:03.159
<v Speaker 3>and it brings up a little like system wide emoji picker.

803
00:42:03.559 --> 00:42:06.440
<v Speaker 3>And I've really enjoyed using it. I remembered it because

804
00:42:06.719 --> 00:42:08.920
<v Speaker 3>I got a new Mac for the new job and

805
00:42:08.960 --> 00:42:11.000
<v Speaker 3>I went to take colon in something and my emoji

806
00:42:11.000 --> 00:42:12.480
<v Speaker 3>picker didn't come up, and I was like, oh man,

807
00:42:12.559 --> 00:42:14.880
<v Speaker 3>I didn't realize how reliant I had become on this thing.

808
00:42:15.639 --> 00:42:19.400
<v Speaker 3>But it's also smart enough to you can filter out

809
00:42:19.400 --> 00:42:24.320
<v Speaker 3>certain apps, so like Slack is essentially blacklisted because Slack

810
00:42:24.360 --> 00:42:27.679
<v Speaker 3>already has an emoji picker, right, so it doesn't like

811
00:42:27.800 --> 00:42:30.480
<v Speaker 3>you don't get two emoji pickers conflicting with each other,

812
00:42:30.519 --> 00:42:33.119
<v Speaker 3>and you can sort of configure that. But for lots

813
00:42:33.119 --> 00:42:35.159
<v Speaker 3>of times, if you're just like in a random textbox

814
00:42:35.159 --> 00:42:37.159
<v Speaker 3>and Chrome, sometimes it's nice to be able to type

815
00:42:37.280 --> 00:42:39.679
<v Speaker 3>an emoji and just have it work. So I found

816
00:42:39.679 --> 00:42:42.079
<v Speaker 3>it's a pretty nice littleb for doing that. So that's

817
00:42:42.119 --> 00:42:42.480
<v Speaker 3>my pick.

818
00:42:42.559 --> 00:42:44.159
<v Speaker 1>That's awesome, nice, cool.

819
00:42:44.119 --> 00:42:47.840
<v Speaker 4>Those are fun. So my pick for this week is

820
00:42:47.960 --> 00:42:51.440
<v Speaker 4>going to continue on the IoT train that I have

821
00:42:51.559 --> 00:42:54.440
<v Speaker 4>been on as of late. This one is one that

822
00:42:54.519 --> 00:42:57.519
<v Speaker 4>actually I posted to Twitter last week and it got

823
00:42:57.559 --> 00:42:59.760
<v Speaker 4>a lot more engagement that I was expecting. And it's

824
00:42:59.760 --> 00:43:04.840
<v Speaker 4>called The Raspberry Pie Beginner's Guide, and it's a yeah,

825
00:43:04.880 --> 00:43:09.119
<v Speaker 4>it's a kid's book. It's built for kids to get

826
00:43:09.199 --> 00:43:11.960
<v Speaker 4>started with their first Raspberry Pie and kind of get

827
00:43:11.960 --> 00:43:16.559
<v Speaker 4>into programming, and it's fantastic. It is two hundred and

828
00:43:16.559 --> 00:43:21.960
<v Speaker 4>fifty two color pages with pictures and code blocks and

829
00:43:22.360 --> 00:43:25.880
<v Speaker 4>all kinds of good tips for people who don't know

830
00:43:25.920 --> 00:43:28.920
<v Speaker 4>anything about raspberry pies, but are looking to learn, and

831
00:43:29.000 --> 00:43:33.119
<v Speaker 4>even though it is aimed at kids, I found it

832
00:43:33.159 --> 00:43:36.079
<v Speaker 4>really useful and helpful. And apparently the rest of Twitter

833
00:43:36.079 --> 00:43:39.480
<v Speaker 4>agreed with me, because there were plenty of people who

834
00:43:39.559 --> 00:43:41.960
<v Speaker 4>were writing about how they had used it, how they

835
00:43:42.000 --> 00:43:45.719
<v Speaker 4>and their kids have used it. How no shame in

836
00:43:46.199 --> 00:43:49.679
<v Speaker 4>buying a book that's aimed at kids to get you started.

837
00:43:49.920 --> 00:43:53.760
<v Speaker 4>So I would highly recommend it if you are looking

838
00:43:53.840 --> 00:43:57.760
<v Speaker 4>to get into that kind of industry or start tinkering

839
00:43:57.800 --> 00:44:01.039
<v Speaker 4>around with this, because it's very helpful. It's cleared up

840
00:44:01.039 --> 00:44:03.239
<v Speaker 4>a lot of stuff that I just didn't know. I

841
00:44:03.280 --> 00:44:05.840
<v Speaker 4>didn't know about raspberry pies and how to kind of

842
00:44:06.360 --> 00:44:10.599
<v Speaker 4>begin the IoT learning. So it's it's a good read.

843
00:44:11.480 --> 00:44:12.639
<v Speaker 1>So when are we going to get to see some

844
00:44:12.639 --> 00:44:14.079
<v Speaker 1>of your IoT creations?

845
00:44:14.800 --> 00:44:17.280
<v Speaker 4>Well, as soon as I finished the book, and I

846
00:44:17.360 --> 00:44:19.679
<v Speaker 4>have a whole bunch of sensors that I have ordered

847
00:44:19.760 --> 00:44:24.519
<v Speaker 4>from a company called the Seed with three e's. They

848
00:44:24.559 --> 00:44:28.320
<v Speaker 4>make all sorts of sensors for pies and Arduino's and

849
00:44:28.400 --> 00:44:32.079
<v Speaker 4>all those little micro controllers and reco processors. But they

850
00:44:32.079 --> 00:44:36.000
<v Speaker 4>are I think their factories in China, so I'm waiting

851
00:44:36.079 --> 00:44:40.159
<v Speaker 4>on the international shipping to oh yeah, get done. It's

852
00:44:40.199 --> 00:44:43.280
<v Speaker 4>taking a little bit longer than something like Amazon.

853
00:44:44.159 --> 00:44:47.840
<v Speaker 3>But soon I feel like we need more books like

854
00:44:47.920 --> 00:44:51.159
<v Speaker 3>that for adults. I don't know if any of you remember.

855
00:44:51.440 --> 00:44:53.159
<v Speaker 3>I don't think these are a thing anymore, but I

856
00:44:53.239 --> 00:44:54.239
<v Speaker 3>think it was head Start.

857
00:44:55.039 --> 00:44:56.880
<v Speaker 1>Oh yeah, those are great, yea.

858
00:44:57.119 --> 00:44:59.920
<v Speaker 3>And they were just fantastically written because they would have

859
00:45:00.159 --> 00:45:04.280
<v Speaker 3>just like cartoons all over the place, and also head First.

860
00:45:04.519 --> 00:45:07.000
<v Speaker 1>I thought it was maybe head First. Was it head First?

861
00:45:07.360 --> 00:45:09.199
<v Speaker 3>I can't remember, but I had.

862
00:45:09.079 --> 00:45:11.719
<v Speaker 1>A lot of the cartoons and that was fantastic.

863
00:45:12.159 --> 00:45:12.519
<v Speaker 2>Yeah.

864
00:45:12.679 --> 00:45:14.239
<v Speaker 3>I don't know what happened to them, but those books

865
00:45:14.239 --> 00:45:16.559
<v Speaker 3>were great. And sometimes they would have those books on

866
00:45:16.679 --> 00:45:21.840
<v Speaker 3>pretty advanced topics. I remember learning like some advanced Java

867
00:45:21.920 --> 00:45:24.960
<v Speaker 3>from those books, and it was just so presentable. And

868
00:45:25.000 --> 00:45:27.519
<v Speaker 3>I feel like we don't, like, we don't do textbooks

869
00:45:27.599 --> 00:45:30.800
<v Speaker 3>much anymore in the first place, and when we do, like,

870
00:45:31.079 --> 00:45:33.239
<v Speaker 3>I don't know, I feel like we'vearied on too much

871
00:45:33.239 --> 00:45:36.039
<v Speaker 3>of the side of like text informational, unless on the

872
00:45:36.639 --> 00:45:39.000
<v Speaker 3>fun sort of aspect of presenting some of this content.

873
00:45:39.559 --> 00:45:43.039
<v Speaker 4>Yeah, the O'Reilly books, as detailed as they can get,

874
00:45:43.079 --> 00:45:46.800
<v Speaker 4>are usually a little bit dry, and it's very nice

875
00:45:46.840 --> 00:45:50.599
<v Speaker 4>to see little cartoons of people picking stuff up and

876
00:45:50.599 --> 00:45:55.039
<v Speaker 4>holding pies and connecting things and diagrams and all that stuff.

877
00:45:55.079 --> 00:45:58.360
<v Speaker 4>So yeah, I agree with you, we need to bring

878
00:45:58.400 --> 00:46:00.639
<v Speaker 4>the fun back to tech full stuff.

879
00:46:01.440 --> 00:46:03.400
<v Speaker 2>Having written a couple of those, they do it digitally.

880
00:46:03.679 --> 00:46:06.400
<v Speaker 2>They do have a very strong tone and the editors

881
00:46:06.400 --> 00:46:08.840
<v Speaker 2>will enforce that on you if you don't like. My

882
00:46:09.280 --> 00:46:12.119
<v Speaker 2>tone is much more jovial and fun and kind of approachable.

883
00:46:12.440 --> 00:46:15.239
<v Speaker 2>So when I write books for myself there, they're very that,

884
00:46:16.199 --> 00:46:19.079
<v Speaker 2>whereas you know, you get the Ariiley thing and they're saying, oh, no,

885
00:46:19.119 --> 00:46:20.440
<v Speaker 2>you know this is this is a bit more of

886
00:46:20.480 --> 00:46:22.639
<v Speaker 2>a textual reference kind of thing. But they did have

887
00:46:22.679 --> 00:46:24.880
<v Speaker 2>that head first series and it is very good. If

888
00:46:24.880 --> 00:46:27.440
<v Speaker 2>they had a head first mL, I'd be all over

889
00:46:27.519 --> 00:46:29.199
<v Speaker 2>that right now for sure.

890
00:46:29.599 --> 00:46:31.920
<v Speaker 1>Yep. All right, Well, my pick for this week is

891
00:46:32.119 --> 00:46:33.760
<v Speaker 1>Virtual Coffee. IOW.

892
00:46:33.960 --> 00:46:37.559
<v Speaker 2>It's a kind of get together for folks in tech.

893
00:46:37.880 --> 00:46:40.639
<v Speaker 2>It's really good. They're very strong in terms of keeping

894
00:46:40.639 --> 00:46:43.639
<v Speaker 2>it a safe space and making sure that there's a

895
00:46:43.719 --> 00:46:46.639
<v Speaker 2>large diversity of folks in the chat and the one

896
00:46:46.639 --> 00:46:49.199
<v Speaker 2>that I went to, we talked a lot about work

897
00:46:49.239 --> 00:46:52.960
<v Speaker 2>life balance and getting burnt out and how to deal

898
00:46:53.000 --> 00:46:54.519
<v Speaker 2>with that, and I thought that that was really cool

899
00:46:54.519 --> 00:46:57.159
<v Speaker 2>and it was interesting because the topic time just came

900
00:46:57.159 --> 00:47:00.559
<v Speaker 2>out of nowhere. It's like the thing that was foremost

901
00:47:00.599 --> 00:47:03.400
<v Speaker 2>some people's minds. I think the pandemic and being inside

902
00:47:03.400 --> 00:47:05.199
<v Speaker 2>all the time has really kind of brought to the

903
00:47:05.199 --> 00:47:08.320
<v Speaker 2>fore all these issues of like burnout and the rest

904
00:47:08.320 --> 00:47:11.159
<v Speaker 2>of it and how do we manage that? So very interesting.

905
00:47:11.239 --> 00:47:12.639
<v Speaker 2>It's great to be able to talk to other people

906
00:47:12.679 --> 00:47:14.840
<v Speaker 2>on network, and so what we talked about before about

907
00:47:15.039 --> 00:47:17.480
<v Speaker 2>self promotion, you know, find these kinds of ways that

908
00:47:17.519 --> 00:47:19.920
<v Speaker 2>you can get your name out there and say, you know, hey,

909
00:47:20.480 --> 00:47:24.039
<v Speaker 2>I'm in the community looking around for work, or this

910
00:47:24.119 --> 00:47:26.039
<v Speaker 2>is what I've been doing lately, and get your name

911
00:47:26.039 --> 00:47:26.440
<v Speaker 2>out there.

912
00:47:26.519 --> 00:47:29.079
<v Speaker 1>All right, Well, this has been wonderful. Thanks for listening

913
00:47:29.119 --> 00:47:31.599
<v Speaker 1>to REACT. Round up and see you next week, hie,

914
00:47:31.599 --> 00:47:32.960
<v Speaker 1>everybody see you then. I
