1
00:00:04,586 --> 00:00:07,964
I'd like to welcome up our very first
speaker of the day, Sharnecia Williams.

2
00:00:07,964 --> 00:00:12,232
Sharnecia is an engineering
manager at Mailchimp,

3
00:00:12,232 --> 00:00:16,694
working to build and
grow diverse teams of engineers,

4
00:00:16,694 --> 00:00:21,942
with a passion for creating
software with the consumer in mind.

5
00:00:21,942 --> 00:00:26,736
Over the course of her 20 years in IT,
she has worked as an engineer,

6
00:00:26,736 --> 00:00:29,908
solution architect, graphic designer, and

7
00:00:29,908 --> 00:00:34,897
a manager at Fortune 500 companies and
non-profit organizations.

8
00:00:34,897 --> 00:00:39,942
She is passionate about increasing
diversity and inclusion in tech.

9
00:00:39,942 --> 00:00:41,992
And was one of the teachers and

10
00:00:41,992 --> 00:00:46,928
coordinators of the SITES program
within the Atlanta chapter of DDPA.

11
00:00:46,928 --> 00:00:51,300
Which is a non-profit minority tech
organization that's dedicated to

12
00:00:51,300 --> 00:00:54,463
training aspiring and
seasoned IT professionals.

13
00:00:54,463 --> 00:00:58,850
And furthering the upward mobility
of minorities in the IT industry.

14
00:00:58,850 --> 00:01:03,510
Please give her a big,
warm Treehouse welcome.

15
00:01:03,510 --> 00:01:05,058
>> Hi, everyone.

16
00:01:05,058 --> 00:01:08,715
My name is Sharnecia Williams,
like Ryan said.

17
00:01:08,715 --> 00:01:13,622
And I'm here to talk to you
today about the key skills that

18
00:01:13,622 --> 00:01:16,291
everyone should be learning.

19
00:01:16,291 --> 00:01:21,155
And these are the skills that
I have found invaluable in

20
00:01:21,155 --> 00:01:24,769
my career over the last 20 years in IT.

21
00:01:27,434 --> 00:01:33,057
And I've broken this presentation
down into two separate sections.

22
00:01:33,057 --> 00:01:36,959
The first section that I'm gonna
go over is the soft skills.

23
00:01:36,959 --> 00:01:40,936
And these are skills that
everyone should be learning.

24
00:01:40,936 --> 00:01:44,462
No matter if you're going
into engineering or IT or

25
00:01:44,462 --> 00:01:49,066
if you're choosing another path,
these skills are invaluable.

26
00:01:49,066 --> 00:01:56,148
The second section and category that I'm
gonna talk about is the technical skills.

27
00:01:56,148 --> 00:02:00,735
These are the skills that are more
geared towards people who are going into

28
00:02:00,735 --> 00:02:02,669
the engineering profession.

29
00:02:02,669 --> 00:02:09,362
So with that said, we're gonna
start off with the soft skills.

30
00:02:09,362 --> 00:02:13,992
The first soft skills that I'm gonna
talk about today is communication.

31
00:02:13,992 --> 00:02:21,537
And communication is a very valuable
skill to be learning during this time.

32
00:02:21,537 --> 00:02:26,858
And it doesn't matter if you're
just starting off on your path or

33
00:02:26,858 --> 00:02:31,035
if you've been in your career for
multiple years.

34
00:02:31,035 --> 00:02:35,167
We all should be developing
our communication skills.

35
00:02:35,167 --> 00:02:39,759
And when I say communication,
I don't only mean verbal communication,

36
00:02:39,759 --> 00:02:42,064
I also mean written communication.

37
00:02:42,064 --> 00:02:44,044
They go hand in hand.

38
00:02:44,044 --> 00:02:49,336
And so when you're learning about
communication, you want to make sure

39
00:02:49,336 --> 00:02:54,820
you're able to communicate your ideas
effectively to others around you.

40
00:02:54,820 --> 00:02:57,422
And on the other side of communication,

41
00:02:57,422 --> 00:03:02,713
besides just being able to get your ideas
across, it's about active listening.

42
00:03:02,713 --> 00:03:07,162
So you'll want to make sure that
you're also learning how to

43
00:03:07,162 --> 00:03:11,717
be an active listener,
listening to understand around you.

44
00:03:11,717 --> 00:03:16,492
So that you will be able to ask
more relevant questions and

45
00:03:16,492 --> 00:03:20,784
get ideas and
thought processes to be successful.

46
00:03:20,784 --> 00:03:25,369
So again, communication is
a very important skill that

47
00:03:25,369 --> 00:03:27,915
everyone should be learning.

48
00:03:27,915 --> 00:03:32,074
The next thing I'm gonna
talk about is teamwork.

49
00:03:32,074 --> 00:03:36,436
And I know you may be going
through your tech degree or

50
00:03:36,436 --> 00:03:42,600
you may be in college, or you may just
be starting out in doing boot camps.

51
00:03:42,600 --> 00:03:46,303
But while you're doing this,
you usually work solo.

52
00:03:46,303 --> 00:03:50,577
You're working on your project, and
it's just you and your code and

53
00:03:50,577 --> 00:03:54,497
you're really not having to
interact a lot with other people.

54
00:03:54,497 --> 00:03:57,701
And that's great for your learning phase.

55
00:03:57,701 --> 00:04:01,678
But when you get into an internship,
an apprenticeship, or

56
00:04:01,678 --> 00:04:05,660
start your first job,
you're gonna be working with a team.

57
00:04:05,660 --> 00:04:10,522
And that team is gonna work together and
they're going to collaborate in order to

58
00:04:10,522 --> 00:04:14,396
build the product that you're
gonna deliver to your customer.

59
00:04:14,396 --> 00:04:20,250
So when you are in a company,
it's not a solo sport like sprinting or

60
00:04:20,250 --> 00:04:26,743
long distance running, or of a team
sport like you're playing football.

61
00:04:26,743 --> 00:04:32,331
So with teamwork, learn how to work
within a group, learn how to collaborate.

62
00:04:32,331 --> 00:04:37,434
And also learn how to contribute your
ideas and your thought processes.

63
00:04:37,434 --> 00:04:42,555
It will enhance the team which means
you're gonna create a better product.

64
00:04:42,555 --> 00:04:46,880
The next skill I'm gonna
talk about is patience.

65
00:04:46,880 --> 00:04:51,528
So as I mentioned with the previous
skill set, which is teamwork,

66
00:04:51,528 --> 00:04:55,522
you're gonna be working with
a lot of different people.

67
00:04:55,522 --> 00:05:00,057
Not only are you gonna work with fellow
engineers, you're gonna work with

68
00:05:00,057 --> 00:05:04,389
product managers, engineering managers,
designers, marketers.

69
00:05:04,389 --> 00:05:09,287
It is an array of people that you're
gonna have to work with in order to

70
00:05:09,287 --> 00:05:13,184
deliver the solution and
the product to your end user.

71
00:05:13,184 --> 00:05:18,027
And so, with that you may be put on the
spot where you have to be able to explain

72
00:05:18,027 --> 00:05:22,593
your thought process, walk through
some code, or whatever it may be.

73
00:05:22,593 --> 00:05:27,563
And you have to have the skill of
patience to sit with someone else

74
00:05:27,563 --> 00:05:31,077
that may not understand engineering terms.

75
00:05:31,077 --> 00:05:34,844
And you're gonna have to sit there and
talk to them and

76
00:05:34,844 --> 00:05:37,124
get them on the same page as you.

77
00:05:37,124 --> 00:05:38,523
So having patience and

78
00:05:38,523 --> 00:05:42,956
developing that skill helps you to
be less frustrated in your journey.

79
00:05:42,956 --> 00:05:50,534
And another thing is making sure that
you develop patience for yourself.

80
00:05:50,534 --> 00:05:53,428
Engineering is always changing.

81
00:05:53,428 --> 00:06:00,363
The field is moving and new concepts and
new languages are coming out constantly.

82
00:06:00,363 --> 00:06:03,148
And don't get frustrated with yourself.

83
00:06:03,148 --> 00:06:07,987
Have some patience with yourself when
you're approaching new concepts or

84
00:06:07,987 --> 00:06:10,599
approaching learning a new language and

85
00:06:10,599 --> 00:06:14,531
you're not picking it up as
quickly as you think you should.

86
00:06:14,531 --> 00:06:19,097
Have patience, grace, and
mercy with yourself, okay?

87
00:06:19,097 --> 00:06:25,754
The next skill I'm gonna talk
about is time management.

88
00:06:25,754 --> 00:06:28,764
Okay, so while you're in your
learning phase you may be working.

89
00:06:28,764 --> 00:06:31,893
While you're in college, you're working,

90
00:06:31,893 --> 00:06:35,674
you have friends,
you have lots of responsibilities.

91
00:06:35,674 --> 00:06:40,587
And it seems like there may be not enough
time to get everything done in a day.

92
00:06:40,587 --> 00:06:43,322
And that's where this skill kicks in.

93
00:06:43,322 --> 00:06:47,714
Time management helps you to
manage your time effectively and

94
00:06:47,714 --> 00:06:51,261
allows you to focus on
the most important tasks and

95
00:06:51,261 --> 00:06:55,078
get those things done efficiently and
effectively.

96
00:06:55,078 --> 00:07:00,186
And so, there are many tips and
tricks and tools out there that help you

97
00:07:00,186 --> 00:07:05,221
to develop your time management skills,
like organizing your day.

98
00:07:05,221 --> 00:07:08,273
Well, you start off at
the beginning of your day and

99
00:07:08,273 --> 00:07:10,410
you organize what needs to happen.

100
00:07:10,410 --> 00:07:12,653
And you're prioritizing your work, so

101
00:07:12,653 --> 00:07:16,021
that you're getting the most
important things done first.

102
00:07:16,021 --> 00:07:20,326
And that leads into making sure
that you manage your calendar.

103
00:07:20,326 --> 00:07:25,047
I know it sounds mundane, but it's very
important for you to manage your calendar.

104
00:07:25,047 --> 00:07:29,914
Because if you don't manage your calendar,
your calendar is going to manage you.

105
00:07:29,914 --> 00:07:32,421
You'll end up getting to
the end of the day and

106
00:07:32,421 --> 00:07:36,986
you've got none of the tasks done that you
really wanted to have done for that day.

107
00:07:36,986 --> 00:07:39,902
Because you didn't prioritize your day,

108
00:07:39,902 --> 00:07:44,690
you didn't organize your day, and
you did not manage your calendar.

109
00:07:44,690 --> 00:07:49,639
So make sure that you master
the skill of time management.

110
00:07:49,639 --> 00:07:55,225
The next skill I'm talking
about is problem solving.

111
00:07:55,225 --> 00:08:01,275
This skill, it works in your career,
it works in your personal life.

112
00:08:01,275 --> 00:08:06,191
It's something that everyone has to do,
and you can't get away from it.

113
00:08:06,191 --> 00:08:11,370
And the way that you solve problems
effectively is taking a step back and

114
00:08:11,370 --> 00:08:15,097
be objective when you're
looking at the problem.

115
00:08:15,097 --> 00:08:20,043
And also figuring out what
are you trying to solve for

116
00:08:20,043 --> 00:08:24,551
and what caused the problem
in the first place?

117
00:08:24,551 --> 00:08:28,236
If you know what caused the problem,
you can come up with the solution.

118
00:08:28,236 --> 00:08:33,344
So being able to approach
a problem objectively,

119
00:08:33,344 --> 00:08:36,270
start to dig deeper into it.

120
00:08:36,270 --> 00:08:40,382
You're gonna have to use some critical
thinking skills along the way.

121
00:08:40,382 --> 00:08:43,039
So developing those muscles and

122
00:08:43,039 --> 00:08:49,056
that skill set of solving problems
definitely helps you in your career.

123
00:08:49,056 --> 00:08:54,599
Now, that sort of rounds out the soft
skills section of my presentation.

124
00:08:54,599 --> 00:08:59,274
The next section we're gonna go
into is the technical skills.

125
00:08:59,274 --> 00:09:03,970
And again, like I said at
the beginning of the presentation,

126
00:09:03,970 --> 00:09:10,128
this section is more geared towards people
who are going into being an engineer.

127
00:09:10,128 --> 00:09:17,365
And the first skill that I want to talk
about is working in large code bases.

128
00:09:17,365 --> 00:09:21,622
So if you're at the very, very beginning
and you're taking boot camps or

129
00:09:21,622 --> 00:09:24,520
you're in the tech degree
program at Treehouse.

130
00:09:24,520 --> 00:09:27,616
Or you're in full four year college,

131
00:09:27,616 --> 00:09:31,497
you're used to working
in smaller code bases.

132
00:09:31,497 --> 00:09:35,589
Code bases that either your
instructor created for you or

133
00:09:35,589 --> 00:09:39,695
it's code that you've actually
created from scratch.

134
00:09:39,695 --> 00:09:42,967
And that is wonderful
in the learning phase.

135
00:09:42,967 --> 00:09:47,503
But when you move on to your
apprenticeship or into an internship,

136
00:09:47,503 --> 00:09:52,288
or get hired at your first job,
you're gonna get kinda overwhelmed.

137
00:09:52,288 --> 00:09:57,603
Cuz you're gonna be working with code
bases that are thousands of lines of code,

138
00:09:57,603 --> 00:09:59,959
and you have no frame of reference.

139
00:09:59,959 --> 00:10:02,623
So.
Learning to get used to working in

140
00:10:02,623 --> 00:10:05,504
large code bases will help you not feel so

141
00:10:05,504 --> 00:10:10,082
overwhelmed when you go into being
an apprentice or intern, and

142
00:10:10,082 --> 00:10:15,377
there's places that you can get large
code bases, like going to GitHub.

143
00:10:15,377 --> 00:10:20,836
You can go look at somebody's open source
code and pull it down and start to work

144
00:10:20,836 --> 00:10:26,394
through that code, so you can get familiar
with working with larger code base.

145
00:10:26,394 --> 00:10:31,369
The next skill I'm gonna talk
about is understanding code,

146
00:10:31,369 --> 00:10:36,059
reading and understanding
code that you did not create.

147
00:10:36,059 --> 00:10:40,786
And so that's where that code base that
you got, the open source code base

148
00:10:40,786 --> 00:10:44,610
I just talked about in the previous
skill comes into handy.

149
00:10:44,610 --> 00:10:50,284
So you can pull that code base down, you
can start to read it and try to understand

150
00:10:50,284 --> 00:10:55,551
what the engineers were trying to
accomplish with this particular code.

151
00:10:55,551 --> 00:11:00,329
Now, there's different ways that you can
learn how to read and understand code.

152
00:11:00,329 --> 00:11:03,732
One of the ways I used to
love to do is to slow code,

153
00:11:03,732 --> 00:11:07,727
where I'm writing the code
down in plain English for me.

154
00:11:07,727 --> 00:11:13,070
Another way is to bring that code into
your favorite IDE and walk through

155
00:11:13,070 --> 00:11:18,257
it in debug mode and with some test
data and see what the code is doing.

156
00:11:18,257 --> 00:11:20,946
Get familiar with reading and

157
00:11:20,946 --> 00:11:25,040
understanding code that
you did not create.

158
00:11:25,040 --> 00:11:30,387
The next skill set I'm going to
talk about is code repositories.

159
00:11:30,387 --> 00:11:33,888
So all this code lives somewhere.

160
00:11:33,888 --> 00:11:39,593
And so,
a very popular code repository is GitHub.

161
00:11:39,593 --> 00:11:43,470
And so,
regardless of where you are writing code,

162
00:11:43,470 --> 00:11:47,798
if you're writing it in the Tech Degree,
or at college,

163
00:11:47,798 --> 00:11:53,301
usually you're using some type of code
repository to push your code in so

164
00:11:53,301 --> 00:11:59,556
that your instructors or your mentors can
look at your code and give you feedback.

165
00:11:59,556 --> 00:12:04,158
And so, whatever code repository
that you are working with,

166
00:12:04,158 --> 00:12:09,114
make sure you understand the ins and
outs of that code repository,

167
00:12:09,114 --> 00:12:13,185
whatever commands that
are needed to bring code down,

168
00:12:13,185 --> 00:12:16,658
push code up,
work out some merge conflicts.

169
00:12:16,658 --> 00:12:23,205
Understand what all those commands are and
be effective at using them.

170
00:12:23,205 --> 00:12:27,013
So again,
GitHub is a popular code repository, but

171
00:12:27,013 --> 00:12:29,705
there are several others out there.

172
00:12:29,705 --> 00:12:31,774
But I would start with GitHub,

173
00:12:31,774 --> 00:12:35,603
there's a lot of good tutorials
out there about GitHub.

174
00:12:35,603 --> 00:12:40,294
The next skill I'm going
to talk about is testing.

175
00:12:40,294 --> 00:12:44,776
I know, you are an engineer and
you write code, but

176
00:12:44,776 --> 00:12:48,945
a part of writing code is
testing that code, and

177
00:12:48,945 --> 00:12:55,011
making sure that you are delivering
a solid product to your end user.

178
00:12:55,011 --> 00:13:02,343
Now, in the corporate world, we do have
people who are dedicated to testing code,

179
00:13:02,343 --> 00:13:06,767
and they're QA,
quality assurance employees.

180
00:13:06,767 --> 00:13:11,993
But before you hand your
code over to the tester,

181
00:13:11,993 --> 00:13:17,354
you should be making sure
that your code is valid.

182
00:13:17,354 --> 00:13:21,504
Go through the unit tests,
make sure that you

183
00:13:21,504 --> 00:13:26,212
are delivering code that
is worthy to be passed on.

184
00:13:26,212 --> 00:13:30,695
So, also sometimes in companies,
there isn't a QA person there and

185
00:13:30,695 --> 00:13:32,331
the buck stops with you.

186
00:13:32,331 --> 00:13:36,558
And if it gets past you, that means that
that defect goes into production and

187
00:13:36,558 --> 00:13:41,202
into your product that you deliver to your
end user, and that's not what you want.

188
00:13:41,202 --> 00:13:45,817
So you want to make sure that you
are testing your code to the best of your

189
00:13:45,817 --> 00:13:46,686
abilities.

190
00:13:46,686 --> 00:13:51,296
And there are plenty of courses out
there that would teach you how to

191
00:13:51,296 --> 00:13:53,694
unit test your code effectively.

192
00:13:54,886 --> 00:13:59,124
The next skill I'm gonna
talk about is documentation.

193
00:13:59,124 --> 00:14:03,281
This is actually our
all-time favorite of mine.

194
00:14:03,281 --> 00:14:05,514
I love to document.

195
00:14:05,514 --> 00:14:08,841
And not all engineers like to document.

196
00:14:08,841 --> 00:14:10,870
Some may groan about documenting.

197
00:14:10,870 --> 00:14:15,798
But believe me, if you start in
your career early learning to

198
00:14:15,798 --> 00:14:20,827
love documentation and
this skill of documenting your code,

199
00:14:20,827 --> 00:14:25,384
then it will save you a lot
of frustration in the future.

200
00:14:25,384 --> 00:14:29,620
Because when you create documentation
about what you are doing,

201
00:14:29,620 --> 00:14:34,624
what your code is doing, and you post it
on a wiki or in Confluence, that means

202
00:14:34,624 --> 00:14:39,721
that that information is there and
it's shareable across the organization.

203
00:14:39,721 --> 00:14:42,438
That means that other
engineers can look at it.

204
00:14:42,438 --> 00:14:47,179
And if you happen to move off that
product and go work somewhere else,

205
00:14:47,179 --> 00:14:52,165
that means that the new engineer that
is coming in to support or to enhance

206
00:14:52,165 --> 00:14:56,906
that code base that you created,
they know what that code is about and

207
00:14:56,906 --> 00:15:02,175
how it is supposed to function,
which makes it better for everyone around.

208
00:15:02,175 --> 00:15:06,854
And outside of documenting,
like in a separate document like Flores or

209
00:15:06,854 --> 00:15:11,846
a Google doc or wherever, you should
also be documenting your functions and

210
00:15:11,846 --> 00:15:15,201
your code within the code
base by adding comments.

211
00:15:15,201 --> 00:15:19,278
Believe me, it will save you a host
of frustration in the future,

212
00:15:19,278 --> 00:15:23,503
because you can walk away from code and
you may not visit that code for

213
00:15:23,503 --> 00:15:26,711
months on end and
you have to go back and enhance it.

214
00:15:26,711 --> 00:15:31,537
And now you have to start all over and
you have to reverse engineer because you

215
00:15:31,537 --> 00:15:35,777
did not document while you were
going along the first time around.

216
00:15:35,777 --> 00:15:39,729
So just make sure that you document,
document, document.

217
00:15:39,729 --> 00:15:44,792
Believe me, it's gonna save you
a ton of time in the future.

218
00:15:44,792 --> 00:15:50,715
And that wraps up the technical skill
set section of the presentation.

219
00:15:50,715 --> 00:15:54,822
But before we move, go,
one more thing, and

220
00:15:54,822 --> 00:16:00,138
this is not dedicated to soft skills or
technical skills.

221
00:16:00,138 --> 00:16:02,488
This is about you.

222
00:16:03,831 --> 00:16:08,267
Confidence, develop confidence.

223
00:16:08,267 --> 00:16:13,978
And as you go along and you go into your
apprenticeship or your internship and

224
00:16:13,978 --> 00:16:19,691
you're working around a host of engineers
that have been in the industry for

225
00:16:19,691 --> 00:16:24,351
1, 2, 5, 20 years and
they have that much experience.

226
00:16:24,351 --> 00:16:29,098
You can feel intimidated and
you can feel like you are an imposter.

227
00:16:29,098 --> 00:16:32,624
And so
you start to deal with imposter syndrome.

228
00:16:32,624 --> 00:16:37,182
But you have to realize those
engineers that are working at that

229
00:16:37,182 --> 00:16:41,841
company all started the same place
that you did, as a beginner.

230
00:16:41,841 --> 00:16:47,878
And so you have to have confidence in what
you have learned in your Tech Degree or

231
00:16:47,878 --> 00:16:53,094
in your college degree or
in your boot camp, have confidence in what

232
00:16:53,094 --> 00:16:58,050
you have learned and that you can
contribute to the team at hand.

233
00:16:58,050 --> 00:17:06,292
And so, I just want to implore you that
having confidence is very, very important.

234
00:17:06,292 --> 00:17:09,661
So to wrap it all up,
I'm gonna do a review real quick.

235
00:17:09,661 --> 00:17:16,577
So on the soft skills side, I have
five skills that I found invaluable.

236
00:17:16,577 --> 00:17:20,660
That was communication,
teamwork, patience,

237
00:17:20,660 --> 00:17:24,071
time management, and problem solving.

238
00:17:24,071 --> 00:17:30,219
And on the tech skill side,
it was working in a large code base,

239
00:17:30,219 --> 00:17:35,903
understanding code and
working with code repositories,

240
00:17:35,903 --> 00:17:39,035
testing, and documentation.

241
00:17:39,035 --> 00:17:43,343
So these are the ten
skills that I have found

242
00:17:43,343 --> 00:17:48,022
invaluable in my career
in the IT profession.

243
00:17:48,022 --> 00:17:51,324
Now, I would love to connect with you.

244
00:17:51,324 --> 00:17:53,809
So here's my connection information.

245
00:17:53,809 --> 00:17:55,775
You can find me on LinkedIn.

246
00:17:55,775 --> 00:18:00,722
And thank you for
attending my presentation.

247
00:18:00,722 --> 00:18:04,983
There is a few more minutes
that I have open for questions.

248
00:18:04,983 --> 00:18:09,646
So let me move right on over to
look at what questions we have.

249
00:18:13,201 --> 00:18:17,355
Ooh, okay, so here's a question.

250
00:18:17,355 --> 00:18:21,625
Sometimes I get busy and
when I return to my coding practice,

251
00:18:21,625 --> 00:18:24,820
I feel overwhelmed at what I've forgotten.

252
00:18:24,820 --> 00:18:30,165
What advice do you have
when I'm in this situation?

253
00:18:30,165 --> 00:18:34,287
So I completely understand
where you're coming from.

254
00:18:34,287 --> 00:18:39,270
And I will say in my career, what I've
done is I've created documentation for

255
00:18:39,270 --> 00:18:39,884
myself.

256
00:18:39,884 --> 00:18:43,350
It's not necessarily for other engineers.

257
00:18:43,350 --> 00:18:47,838
It is strictly for
myself what I write down, tips, tricks,

258
00:18:47,838 --> 00:18:52,677
tools, concepts, and
it's my little cheat sheet that I'm able

259
00:18:52,677 --> 00:18:56,739
to refer back to in order to
jog my memory about things.

260
00:18:56,739 --> 00:19:00,742
So if you find yourself
where you're really busy and

261
00:19:00,742 --> 00:19:05,839
you need to create some kind of
document that you can refer back to,

262
00:19:05,839 --> 00:19:08,584
where you could put a placeholder.

263
00:19:08,584 --> 00:19:11,297
And so you can go back and say, yeah,

264
00:19:11,297 --> 00:19:14,930
I remember what I was doing
because you document it.

265
00:19:14,930 --> 00:19:18,393
So please create yourself a tips, tricks,

266
00:19:18,393 --> 00:19:21,960
some type of book for
yourself, a playbook.

267
00:19:21,960 --> 00:19:24,189
I create mine in Google Doc, but

268
00:19:24,189 --> 00:19:29,738
you could use whatever you need to use in
order to help yourself jog your memory.

269
00:19:29,738 --> 00:19:32,543
Okay, I got time for one more question.

270
00:19:32,543 --> 00:19:36,984
So let me see,
do coders use cheat sheets for coding or

271
00:19:36,984 --> 00:19:40,263
do coders need to memorize many codes?

272
00:19:40,263 --> 00:19:44,069
We use cheat sheets, we Google a lot.

273
00:19:44,069 --> 00:19:50,253
So please do not feel like you
need to memorize code, you do not.

274
00:19:50,253 --> 00:19:52,126
As you get more proficient,

275
00:19:52,126 --> 00:19:55,883
you will memorize things
because you use it constantly.

276
00:19:55,883 --> 00:19:59,906
But overall, you're not gonna
be able to remember everything.

277
00:19:59,906 --> 00:20:04,318
So that goes back to my cheat sheet,
my playbook that I had,

278
00:20:04,318 --> 00:20:08,223
my tips, tricks and
tools that I use as an engineer.

279
00:20:08,223 --> 00:20:13,145
I had a whole playlist within
YouTube on GitHub commands.

280
00:20:13,145 --> 00:20:15,043
I didn't memorize all of that.

281
00:20:15,043 --> 00:20:18,455
I had to go back and
make reference points.

282
00:20:18,455 --> 00:20:22,525
So please do not feel like you
need to memorize all of the code.

283
00:20:22,525 --> 00:20:27,698
You will learn as you go along and
that is time.

284
00:20:27,698 --> 00:20:32,566
So thank you all for
attending my presentation,

285
00:20:32,566 --> 00:20:35,660
and so, have a wonderful day.

286
00:20:35,660 --> 00:20:37,287
Thank you, bye.