Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Don Hansen (00:00):
Today I want to talk
about a type of person that I
come across in my mentorshipsessions or that'll pop into my
community, who is probably notgoing to get a dev job.
Now, this might sound incorrect.
A lot of people think that youneed a lot of motivation to
(00:24):
become a developer, and if youdon't have that motivation, this
might not be the profession foryou.
Right?
You might need to really gaugewhether this like coding,
solving problems through code,being a software engineer is
(00:47):
really something that you havethe resiliency to pursue,
because it's a very long pathand, you know, if you really
don't enjoy coding, you mightnot make it to the end of that
path to land that firstdeveloper job.
Now, you might think thisbecause I've given this advice,
right, but there's nuance inthis advice.
A lot of people think that ifthey don't feel high motivation,
(01:14):
if they don't feel like anintense enjoyment in coding, a
passion we hear this word a lota passion for coding, that
you're not meant to become adeveloper, and that is entirely,
entirely untrue.
You don't need to be passionateabout this, you do need to
enjoy it.
If you don't enjoy it this is along path you're probably going
(01:35):
to give up right?
I'm just talking about theaverage person.
You will probably give up.
Of course there are exceptionsto that rule, but you're most
likely going to give up if youdon't even enjoy it.
But I come across someone whosometimes I would do kind of
like I used to do sales whatwould you call them Like kind of
(01:58):
like pre-sales calls for mymentorship, where we would just
figure out if it's a good fit.
And it was just kind of aninitial free session.
And this is when I was stillironing out how to weed people
out to make sure that I'mactually being paired with
people that I can actually help,that I'm going to provide value
with with my mentorshipsessions.
But I used to come acrosspeople that would get really
(02:20):
excited, like they are.
Just, they have a burst ofmotivation.
I really want to become adeveloper.
I am going to code 12 hours aday.
I'm going to code six to sevendays per week and I, you know,
even with my full-time job, I amgoing to be able to dedicate 20
to 30 hours per week.
I love this.
I am so passionate about coding.
(02:43):
Almost all of those people gaveup.
If I had to give an estimatedpercentage, it's probably 99% of
people to really paint apicture.
I don't know exactly why it is,but I can tell you for certain
(03:03):
that we could dig into why thatis.
You can kind of see, or atleast try to avoid some of the
pitfalls that have kind of heldpeople like this back.
But for some reason people likethis just that they experience
high intensity, emotion.
They experience like high highsand high lows, and I think
(03:27):
that's what it comes down toLike.
They are just really in thepresent and they can feel things
strongly and when they get thatburst of motivation they feel
very high on that motivation.
They're probably the same typesof people that'll watch
motivational videos just to getthem all pumped up.
They're probably the same typesof people that'll watch
(03:47):
motivational videos just to getthem all pumped up.
And if you're this person, youmight realize you're watching a
lot of these videos over andover and over to keep that
motivation high.
Eventually, the type ofdeveloper that ends up at that
finish line is the type ofdeveloper that just enjoys what
(04:10):
they do but builds good habits.
They don't just lean on ridingthat high motivation, they're
realistic, they analyze theircurrent situation.
How much available time do Ireally have when I get off work.
(04:33):
Can I really dedicate four tofive hours after an eight-hour
shift every single day?
That's really unrealistic,right?
When essentially and that'swhat it comes down to is it's
unrealistic expectations thatpeople set for themselves.
That's just really unhealthyand it's not sustainable.
And when people come to me andthey're like I'm going to
(04:56):
dedicate again four to fivehours after work and I am going
to just crank out this code andI'm going to learn significantly
and I'm they just don'tunderstand that they can't just
cram everything in and they'regoing to have to balance that
mental.
They're going to well, they'regoing to have to understand
their mental energy and how muchthey have available after a
(05:16):
full-time job.
Right, it's people that are likeyou know what, on Tuesdays and
Thursdays, I have to do thistask at work and I am mentally
drained.
I am not even going to touchcoding.
I'm going to come home.
I'm going to spend time with myfamily.
Love my kids.
They kind of helped medecompress.
Love my wife, love my husband.
I am just going to chill out.
(05:38):
We're going to watch a bit ofNetflix and that's okay, right,
but Wednesday, man, I don't havea hard day on Wednesday, or
Friday is a really easy day.
Yeah, I'm.
I might have to give up goingout on Friday, but I have a lot
of mental energy.
I'm going to take advantage ofthat.
It's that kind of mindset that Isee among successful developers
people that eventually landthat first developer position.
(06:01):
I want you to be really, reallycareful.
If you are the type of personthat I'm describing, where you
just feel incredibly motivated,super hyped up, I'm going to
dump 80 hours a week into this,I quit my job, I'm going to dump
80 hours a week into this and Iam just going to get that job
(06:21):
in six months because I amoutworking everyone, you most
likely are going to fail.
You're going to burn out.
Almost no one can overcomeburnout Without truly
understanding habits and theiravailable mental energy and
taking advantage of certaintimes and days throughout the
week where you can actually beproductive.
(06:44):
People that go to the end arepeople that have built up a
system, a schedule.
They know themselves very well,they know their weaknesses,
they know their strengths verywell.
They know their weaknesses,they know their strengths and
they build a system.
And even it comes down todecluttering your desk and maybe
going to a different locationbecause your noise is homey or
(07:06):
your home is noisy and you arejust setting yourself up for
success because you know yourweaknesses and you know how to
set yourself up for success soyou can have the proper
attention to learn, to code, toreinforce that learning, and you
(07:27):
just set your and you, you eatright.
Maybe fasting works for you,maybe like a low carb meal, um,
or like a low carb meal or likea high protein meal works for
you.
You figured out your body to beable to use your energy
correctly, to be as productiveas possible during key points
throughout your week.
That is what it takes to besuccessful.
(07:53):
That is what it takes to becomea developer.
I want to reiterate you do nothave to be passionate about this
.
I think you're going to quit ifyou don't enjoy it, but you
don't have to be passionateabout it.
But I have people that aretrying to that have requested to
become like get into mymentorship sessions where
they're just like you know what,don, and it's kind of like a
(08:16):
high energetic kind of fun call.
But I'm probably bring themdown a bit because I'm pretty
realistic by the end of it, butthey're like if I have you by my
side and I'm going to dedicateall these hours on top of my
full-time job.
I know I know you say like itmight take two plus years to
become a developer, but I know Ican do it in six months because
I have you on my side and Ihave all of this Um, like I, I'm
(08:38):
passionate about this done.
I am passionate, right, andI'll look at their GitHub a week
later.
They haven't coded anything theyhaven't complete.
If I follow up with them, theyhaven't completed anything in
their coursework.
Nothing like that.
Like you should be doing thaton your own, without my help.
And if you're not even doingthat, like you are just riding
(08:59):
the highs of motivation and youare probably someone that's just
going to fail at this.
Right, it doesn't mean thereisn't another career path for
you.
I'm just telling you what I seeis just a big red flag among
aspiring developers is when youare just unrealistic about your
situation, about your energy,about your motivation, your
(09:19):
motivation will die.
If you haven't checked it outalready I have I don't even
remember what it's titled, but alot of you probably know the
thumbnail like fuck yourmotivation, right, you shouldn't
be relying on motivation andthe intensity of that high.
That motivation is not going tobe reflective of how well
you're going to do on yourlearning to code journey.
So don't give yourself falseconfidence with that.
(09:42):
Take it day by day.
Give yourself several months tosettle in and learn to code
little by little.
Don't give yourself a huge highexpectation that you are going
to be job ready in three months,going to be job ready in six
months.
Just set a consistent scheduleto continue learning and growing
and you will grow with thatconsistency.
(10:12):
But let that excitement thatbuild naturally give you little
burst of motivation.
Be careful, because I this isone other thing that I want to
emphasize and this is where Ireject some clients as well.
(10:34):
I don't want you signing up andpaying like an annual plan for
a course because you're ridinghigh in this motivation.
I don't want you doing that fora coding bootcamp.
Most certainly I don't want youseeking out paid mentorship,
like my mentorship or anyoneelse, because you are just
riding high in that motivation.
I want you to get the valuethat you pay for but you don't
(10:57):
even know what you really needwhen you haven't crawled through
the mud and all the shit in thebeginning of becoming a
developer to realize if you evenlike it, if you actually want
this as a career, years down theroad and build that into a
(11:18):
career 10, 20 years into thefuture.
And now, granted, like 20 yearsis a bit far, but like, do you
really want to deal with some ofthe shit of becoming a software
engineer and the high pressureand constant learning to keep up
and be marketable?
And I think that's where someof this stems from too.
(11:42):
I mean, sometimes people have apersonality to just feel these
high highs and low lows, but Ithink part of it is, um, you
just have a misconception ofwhat it's like to be a software
engineer.
You haven't experienced all thefrustrations and feeling stupid
and because you can't get pastthis bug and um, going into an
(12:04):
interview and freezing up andnot being able to present your
skills well at all and gettingfrustrated with that or just
getting tons of rejection.
Like there's so much growththat's going to happen.
As a software engineer, you haveto pace yourself and that's
really the key thing.
You have to pace yourself.
Stop looking up motivationalvideos.
Just learn to code little bylittle on the days that you have
(12:27):
off code on the side.
Reinforce that, continue tobuild up that foundation so you
can build from smaller to largerand more complicated projects
over time, pace yourselves.
So if you are someone that doesget yourself incredibly hyped up
and you have that you plan outan entire three month schedule
(12:51):
and then you plan outunrealistic goals for yourself
of time commitment and then yougive up a week later, you know,
if you're this type of personand that should be a red flag to
you, it doesn't mean you're notgoing to become a developer,
but it means you are not in syncwith yourself enough.
(13:12):
You haven't built up goodenough habits over time to
really make this path efficientfor yourself, and so that should
be a signal like, hey, let'spull back, let's just focus on
today.
Here are my goals today.
Okay, cool, I accomplished mygoals today.
Let's go ahead and do a two-daygoal, a three-day goal, a week
(13:33):
goal, right and keep pushingyourself.
And if you fail that one-daygoal, if you fail that two-day
goal, if you fail that week goalor that month goal, analyze why
you failed that.
What did you fail about it?
Is it unrealistic?
You know, maybe you've yougotta dig into goal setting,
like, maybe you're trying to setyour goals based off of outcome
(13:54):
.
I'm gonna get a job hereinstead of I'm gonna code for 10
hours per week and I'm gonnaapply for this many positions
and I'm gonna do companyresearch for like 80 of these
positions.
And like your goals should beset based off of what you can
actually do and what you cancontrol.
Maybe goal setting is anotherthing you have to work on, but a
(14:19):
lot of people need to justanalyze how their week went.
Are you proud of the work thatyou've done?
If not, why not?
And what is affecting yourproductivity?
What is affecting you failingto build better habits for
yourself?
It truly is a self-analysisjourney and I'm telling you a
(14:42):
lot of people that eventuallyland that developer position.
They have grown significantlyand I'm very proud of you for
anyone that has grownsignificantly and I'm very proud
of you for anyone that has.
But pace yourself and if whatI've described is a bit of a red
flag question, look kind ofjust like analyze previous
attempts to try to accomplishsomething.
(15:03):
Are you just riding high inmotivation and you're eventually
going to quit because you don'treally have a true
understanding of how you workand your productivity and you
don't set proper goals and youhave unrealistic expectations.
Catch yourself early so thatyou can set yourself up for
success in the long run withyour learning to code journey.
(15:24):
So I just want to give you aheads up.
If you are this type of person,that's okay.
There are very high energypeople like this, but you might
need to ground yourself a bitmore and be more pragmatic about
your approach.
I hope that helps.