what's going on guys tenzin here this is
front-end web developer guide 2020 what
we'll cover in this video are the
following okay
all the technologies you'll need to
learn to become a job ready front-end
web developer and how long have time to
spend on each technology
we'll cover step by step walkthrough of
the entire journey so that you have 100%
certainty in where you're at in each
moment best resources free plus paid but
we're going to focus more on free
because this is 2020 and if you pay in
your time and work and energy you can
learn anything for free anything and
everything for free so resources to
learn all the major languages tools
frameworks and whatnot the why and how
to get really good at javascript why you
need to need to learn back-end to become
a great front-end developer what does
the future hold for front-end web
developers how to guarantee your success
and actually make it happen this is a
science there's no if there's no but
there's no hope if you put in the work
you will get it and you will get it
faster then you think how to make an
income while you're learning the code
we're not gonna touch on that too much
in this video because I have a full
video like an hour-long video coming on
that in the next few weeks so stay tuned
for that but these are some of the
things that were then cover in this
video so before we continue why follow
this guide I started learning the code
in 2010-2011 seriously okay
wrote my very first HTML CSS in fourth
grade that was like when I was in like
fourth grade and we were doing
everything with table tax there's no
flex box no grid everything with just
table tax and if any inline CSS and I
thought I was a hacker but I wasn't and
I stopped coding but I started again
between 2010 and 2011 this was like when
code Academy had
just started and I failed for over five
years
I quit many many many times okay because
I didn't know what to do I wanted to
become a web developer but there weren't
any resources or a roadmap like this
video back then so I had no idea right
so I just learned everything through
trial and error trial and error which is
the most stupid way of learning of
course but hey sometimes you gotta you
got to do what you got to do but finally
broke broke through in 2015 right then I
really committed and I was spending like
15 to 18 hours a day studying whilst
having to sleep in the car in the winter
at sub-zero temperatures temperatures
for like months and months on end up to
like eight months or something like that
it was pretty brutal but I'm very proud
of that and nobody can take that away
from me I've tutored over hundreds of
students one on one both locally and
remotely I have mentored dozens of
students one on one again most were boot
campers and some were pursuing master's
degrees as well
all of them have landed jobs most work
at local agencies and security companies
if you work at Microsoft one of my
student recently just landed a job at
Hulu and his first day was like last
week Tuesday or Monday or something like
that and some are starting their own
startups so you can say I'm pretty
qualified to talk about this stuff okay
and of course I have done this myself as
well it's not just like me spewing
nonsense things that I read online and
then I'm telling you guys no I did this
myself and then I helped other people do
it as well alright so this is why you
should follow this guide and this guide
will be very focused on minimalism doing
less not more
the magic word is focus okay in today in
the development field to this industry
there are a bajillion things you can
learn but we're not going to talk about
all of them just gonna talk about what
the most important things that actually
drive the bottom line and help you
directly to land a job or start
freelancing or whatever it is that you
want to do in this field why why should
you become a front-end web developer in
2020 I just looked it up front on the
web developer salary 108 thousand eight
hundred and twenty nine dollars okay
according to indeed.com now salary it
really doesn't matter the number what
the numbers are because it fluctuates
depending on where you live the cost of
living and all that stuff right
making hundred K in California is like
making 50k in something like Wisconsin
okay it really doesn't matter you have
to take the cost of living into account
right so if you get a job at a company
in California or the Bay Area they'll
pay you a starting salary of like 110 K
it's pretty common there but you're not
gonna find that in the middle of nowhere
like Iowa or Wisconsin you're probably
gonna get a starting salary of between
65 to 70 and that's good that's good
because that's pretty much the same
thing as getting paid like 90 to 100 K
in California if not more okay so you
got to keep that into account but the
point is it's this is a profession that
is very well paid and you know you don't
you won't have to worry about money but
you shouldn't do it just for the sake of
money because you're not gonna make it
because SH it's just hard and if you go
for money most of the times 99
9% of times you will fail you will 100%
without a doubt fail and I failed many
many many businesses because I went into
it with that mindset of just making
money and it never worked out because I
wasn't patient enough
I wasn't resilient enough and I was just
not enough because I was just going for
money but as soon as I shifted that and
changed that and I learned it again
through trial and error then a lightbulb
you know went off and the know the rest
is history right but again if you're
just doing it for money you're not gonna
make it the probability of your of your
success is very very low unless you're a
grant cardone not only are you solving
problems but you can do it create
creatively so why should you become
developer right front-end developer
specifically so you make a lot of money
but also because not only are you
solving problems like any kind of
developer back-end developer or full
stack developer you know there are many
kinds of developers but you can also do
it creatively in my opinion it is more
fun than pure back-end since you get to
work on many different aspects of the
product right we were talking about
design performance code colors
typography UX server lists like new
tools different frameworks and you even
need to interact with a customer or end
customer client especially if you're a
freelancer or something right a lot of
what used to be done by pure back-end
developers are being done by front-end
developers today ok so there's an
exponential room for growth it's much
easier to get into because to learn
back-end you have to learn in front end
first you have to start off with
front-end but it's much harder to master
because there are new tools you gotta
you have so many different variables
like different moving variables and more
variables or complexity but that also
makes it worthwhile of an industry or a
profession to get into because it's
always going to be chaotic and newbies
have an advantage right you can start
today and you can go in hard and learn
and be actually hireable in the
marketplace right if a developer on the
job today a friend and developer stops
learning and evolving today he or she is
going to be obsolete in like two to
three years because things are changing
so rapidly that you just have to evolve
and learn all the time right so that's
why it's also good it's bad because it's
harder to master but it's also good
because there's chaos right and more
chaos means there's always room for
growth if that makes sense this is
probably the worst time to become a
front-end web developer in terms of
difficulty because today there's a
septillion tools waste frameworks
languages paradigms to do things for
front-end and things are changing so
very rapidly however this also makes it
the best time to get into the field if
you're willing to put in the hard work
and invest into it 100% because the
payoffs are well worth it there's always
going to be a high demand for a good
front-end developers because there's
always going to be chaos developers
become obsolete if they don't stay in
the game for a few years okay all right
before we continue talking about HTML
CSS javascript computer science okay I
highly recommend you start learning
computer science and not jump right into
web development I highly highly
recommend it
you're gonna feel like you're going slow
but you're actually going fast and we'll
talk about that in a bit but
fundamentals cs50 by Harvard is the best
CS course on the planet without a doubt
without a doubt and I haven't looked at
other CS courses in a while but I am
still willing to bet willing to bet that
cs50 is still the best CS course okay I
have recommended cs50 to all my students
that I've ever taught mentored to all my
friends everybody and everybody has
loved it and if they didn't then that's
their fault not mine don't need to go
through all of it I just go through the
first few sections again you don't need
to go to all of it and I think they
cover a lot of a lot more other things
later down the road but the most
important sections if I remember
correctly I haven't looked at it for
like four plus years at this point the
algorithmic section where they talk
about sorting algorithms and then the
computer science part where they talk
about the history of computer science
compiling abstraction big o-notation
efficiency like sorting searching
algorithms you know history of CS how
computers work what is what's binary
right like all these things learn that
first it will make a lot of other things
later down the road much much easier
okay and it's fun it's cool now
that should take you about 50 hours not
more maybe less but 50 hours I think you
that's enough to go through the first
few sections of that course maybe a
little bit more if you have no
background in computers at all and
you're touching computers for the very
first time but 50 hours is what I think
is good enough for this okay
next preparation so Before we jump into
HTML CSS
once you have learned the basics the
fundamentals of computer science and now
you're looking into web development I
highly recommend getting a bird's-eye
view the macro view of everything that
is involved in this industry the web
development industry right like watching
this video like watching this kind of
video and then going into all the
technologies and getting a general sense
high-level overview and meaning and
definition and understanding of all
these technologies right take a look at
the industry as a whole look up all the
technologies and get a high level
understanding of all players involved
understand what computer science is what
software development is what web
development is and the differences
between all of them how the web works
what is HTTP what is a server what is a
client their relationships and all that
stuff ok and the reason why you do this
is because if you skip these things and
you skip the cs part you skip this part
you skip learning the fundamentals so
you try to go fast you're gonna crash
and burn and again we'll talk about that
as well
but everything is built on layers ok
foundational layers so very on the very
bottom you have computer science and
then you have software development and
then you have web development and then
you have front-end web development and
then you have the languages write in
JavaScript and then inside of JavaScript
you have the core like core JavaScript
and then you have the frameworks right
react and even before that you have a
layer of design patterns and then react
on other frameworks and most people they
try to jump right into like react and
then they they go what this thing is so
hard yeah
no because you have no foundation
no matter how amazing of a building you
build if it's on a weak foundation a
small windstorm is gonna mess it up
destroy it there's no point
all that energy spent learning react
it's just not worth it so
really take it slow work on the
foundations once you have done that
again bird's-eye view 5 hours maybe less
if you watch a video like this your your
set and then Google a little bit about
like some things that you don't
understand and that's it like literally
that's it all right HTML and CSS hundred
dollars you might think that's a lot of
hours but it's not you just happen it's
you just have to put in the hours all
right guys like there's no better way to
say this you have to put in the hours
HTML and CSS what HTML stands for
hypertext markup language content words
text images videos paragraphs structure
everything that you see on the page
that's HTML CSS cascading style sheet
that's the design part right colors
design layout animations positioning
responsiveness when you go on the phone
how does it look when you go on the
tablet how does it how does it look that
stuff CSS takes care of ok that's it
simple as that
best resources to learn MD end
documentation ok Mozilla developers
network it's 100% free go to a book I
always say you know the best way to
learn anything on any subject at any
point in time is going through a good
book that's it not courses not videos a
good book that's it
but I am not familiar with any HTML CSS
book that's up-to-date that's why I
recommend the mdn documentation okay if
you want me to give you a book that
would be what is that guy's name Charles
tuck it or something like that the HTML
CSS book I think was his name was duck
it or something like that and the book
is really good I won't
I won that book as well and it has like
really cool pictures and it teaches to
you visually and you know if you're
gonna teach CSS that's that's how it
should be taught right it was fun when I
had it back in the days but now there
are so many new things in CSS and I
don't know if the book is up-to-date I
don't think it is that's why I'm saying
I don't know if I should recommend that
book even but the documentation should
be up to date on the MDN be very careful
on YouTube it's very easy to waste your
time on crappy tutorials avoid crash
courses unless you know why you're doing
it and if you're a beginner you probably
don't so don't crash courses give you
this illusion this false sense of
accomplishment that you have learned so
much in reality you haven't learned
anything or you have this false sense of
accomplishment and that you you should
you should know all these things and
what that does is when you actually get
down to building a project you have no
idea how to build anything or how to do
anything because you just have a weak
understanding of the general things and
that kind of kills your confidence
because you think you should be able to
do it but but you don't but you don't
know but you can't and that kind of
messes you up here so that's why I say
avoid crash courses however later when
you have learned all that and then you
want to like refresh your memory crash
courses are amazing for that right crash
like
video of like crash course video of like
an hour if you watch it on YouTube
unlike 2x speed or one point one point
five pack speed it's amazing for
refreshing your memory and then like
getting an overview understanding of
things but I highly highly don't
recommend going through a crash course
if you are a beginner I I would much
rather have you go through the
documentation and take things very very
slowly okay and if you're going for free
material make sure they're not wasting
your time because there is an abundance
of information today and the number one
asset you have is your time and that's
that's really what you have to pay
attention to and make sure that you're
not wasting your time and focus and
energy right if you can afford it always
go for paid if you can pay to get a
shortcut to learn things faster 100
percent pay but I understand that most
people can't afford it most people are
getting into this industry for a reason
all that stuff yadi idea
that's why pay with your effort pay with
your work pay with your time right go
through the documentation how should you
go about learning it learn the basics of
the languages from a book or the first
few things that comes on Google ok am
bien again go to your favorite websites
ok so whether it be Google Facebook
reddit dribble and curate all the micro
components that you like from these
sites right these websites are just a
combination of small components they
have a search component they have a
login component they have a sign-up
component they have a navbar component
they have a hero image component they
have a contact form component they have
a footer component they have an image
slider component right it's just a
culmination of
micro components so curate everything
that you like and have a list of them
okay because when you know how to build
all of these then you can build any
large sites it's just putting it's like
LEGO pieces okay you have LEGO pieces
and then you just combine them now okay
you don't just go for a huge website and
then try to create that because you're
not gonna learn anything because first
of all that's gonna be too overwhelming
and even when you build it you're
probably gonna build it through like a
tutorial you're gonna copy it all and
then again that false sense of
accomplishment right you think you have
a project but you know deep down you
didn't really do anything and 80% of it
you didn't really get it and the things
that you got from the 20% that's still
weak so really pick something atomic
like something very very small like a
navbar or just that hamburger icon or
that or just a contact form or a footer
whatever it is something very very small
and then start building that with just
HTML and CSS okay
so learn layouts positioning flexbox
grid box model specificity and the most
important thing here is learning how to
build layout okay once you have all the
micro components then the next step is
learning how to build layout and if you
learn that part then you will really get
the CSS part because it's back in the
days I remember you know with CSS and
HTML I was just having trouble like
looking at things like a menu bar or a
nav bar and going how how does that how
does my code translate into that or vice
versa like I don't get it but that's
where the layouts come in comes in right
and that's where the box model comes in
understanding box model is very
important and then specificity flexbox
great I would say start off with flex
box and if
if you understand flexbox well enough
grid will be easier to pick up
okay these are grid is a little bit more
complicated but like again once you
understand one the next one is going to
be easier to learn so take it one step
at a time and start building don't try
to be perfect and learn about all the
HTML and CSS there is on the
documentation and then start building no
no no by the time you start building
you're gonna you you're gonna forget
most of them so as you're learning learn
something cool build something with it
build one or two things two things or
three all right start building and then
repeat so here's the process right look
for micro projects to build for example
navbar different nav bars hamburgers
different hamburger icons headers he-bro
contact form footer etc learn and build
now you have these micro components now
learn how to build them and then
actually build them and once you have
gone through a tutorial throw that
tutorial away and build something that
you have learned from this tutorial on
your own if not two or three of your own
ok don't just keep learning that's the
tutorial purgatory right that's the help
that you don't want to be in ok because
again that false sense of accomplishment
and learning you haven't learned you
just is it's just it's just a fake
Wonderland
it's a Fantasyland so be very careful of
that don't think start coding look up
tutorials on how to build a specific
thing and start building knowing without
taking action is not knowing okay if you
keep learning but you're not building
anything with it you're not learning
repeat building something once is not
enough you need repetition in a lot of
it okay building multiple navbars
multiple footers multiple hero multiple
hamburger ID
multiple contact forms maybe just write
it a bunch of times once we have
finished a tutorial tutorial just write
that same copy just look at it and just
copy it just copy like at least three
times that will help you register that
information in your head a little better
okay when you write it repeatedly so you
need a lot of repetition that's the
point more HTML and CSS responsive
design learn that learn fluid design
media queries and then typography right
you don't need to go too deep into it
but learn the basics of typography and
why it is important fluid typography
learn that as well responsive typography
and find the differences between them
like what what's the difference between
them right you don't need to go too deep
into it
just get a general sense of it and try
using it every time you're building
something focus on typography focus on
the responsive part focus on making it
fluid like you know pick one and then do
that and start implementing learn a
little bit start implementing right away
it's that instant feedback right after
learning something when you build it
that's the instant feedback and that is
what really silly
so that solidifies your knowledge okay
and you actually learn I know full stack
developers okay before that CSS is easy
to get started but difficult to master a
lot of the times you know developers and
people who call themselves engineers and
people who say oh there's a big
difference listen between engineers and
developers they have this elitist
mindset and they'll actually devalue
your CSS skills when you're learning CSS
they'll say it's not coding cool it's
not code it's not programming cool
whatever right let them say whatever the
hell but CSS is a very very valuable
skill and with ace just HTML and CSS you
can do so many many many many things all
right like help for email development
like it's all HTML and CSS you can get a
job with just HTML CSS for email
development but let's not go that far
ahead I know full stack developers with
years of experience not be able to do
very simple things in CSS okay and they
call themselves full stack developers
and the suck at design they suck at CSS
they just be they can write CSS but
write really shitty CSS code okay so
don't be one of them
don't try to be full sack just just do
one thing and that one thing well and
people will hire you when you say you
can do one thing and you do one thing
well instead of saying hey I'm full
stack and then you look at the work and
it's just mediocre job at every single
thing right then what what are you good
at take your time
learn it slow learn it well if you go
fast you'll crash so we have fast Tommy
and slow Becky on the right right slow
is fast okay knowledge compounds
knowledge compounds not just interest so
we have slow Becky here starts January
fast Tommy here starts January as well
now fast Tommy is very impatient he
wants to get there and he wants to learn
things really fast right and he will
skip steps and he will try to go to
projects and big projects and get them
done right and by April he feels really
confident like really really confident
and then something happens when he has
to build something from scratch and he's
like wait a second I learned everything
that I've learned is was a lie right and
he realizes that his understanding is
very very weak and then crash okay
and if you look at Becky you're gonna be
like Oh Becky is still behind Tom right
Tommy is still ahead
Tommy is still ahead but Becky is just
slowly chipping away at the fundamentals
and just Frankton it what strong base
okay it's very slow but she's building
this concrete base that there's and
she's putting just one brick at a time
one brick at a time one brick at a time
and then cementing it and making sure it
stays there and a long story short what
starts to happen is by September like by
October Becky is actually surpassing Tom
and this graph is actually wrong okay
let me fix it live here this graph this
boy is supposed to be up top here nope
if I can drag this that's not what I
wanted to do either how can I do this
there this that's that's what I'm trying
to do
what is going on guys okay cool so let's
wait for it to load load cool so that
Green Dot is when you're a job ready and
when you can start applying to jobs and
they'll you know you have a valuable
skill set and you're actually ready to
get a job right Tommy will never get
there because he's just oscillating to
the same spot back and forth back and
forth right because he has weak
fundamentals and he's trying to learn
all these tactics and like these tools
and these frameworks and libraries and
trying to go fast but he's never gonna
get there okay and that's why you also
shouldn't touch any CSS frameworks like
bootstrap or bulma or anything like that
no no if you learn CSS really well you
can pick a bootstrap in a day in a few
hours you're gonna be like wow this is
this is the gift from the gods from the
deepest depths of heaven okay you're
gonna be like this is so easy
but even then you're not gonna want to
write in bootstrap or write in bulma
because you're like you know what I got
a take so many things and undo CSS so
I'm not I'm actually not not even gonna
use it okay you should be disgusted
using bootstrap at some point so that's
the that's where you want to be okay
that's where you want to be and the only
way to get there is by going slow again
the process find learn and build repeat
find atomic projects or components learn
build
repeat repetition okay
enough repetition we'll make it a habit
and enough repetition of habit we'll
make it an instinct and when it's an
instance tinct oh and that then you're
dangerous all right when to move on you
have built over at least a dozen micro
components without JavaScript
you have built at least five to ten
single and multi page websites you're
comfortable with CSS fundamentals
positioning flexbox grid media queries
etc if I gave you a mock-up today you
should be able to implement that and
make it live right 90% 95% of the
markups out there for most sites you
should be able to just build it anything
you see in design you should be able to
just write in an HTML CSS and make a
live okay and the only way you get there
is by doing repetition repetition and
here focus on the words at least okay at
least at least if I told you to make a
simple navbar that collapses
responsively in mobile and tablet it
should take you no more than 15 minutes
spend about hundred hours learning and
building things with pure HTML and CSS
again don't judge
don't touch libraries don't touch
bootstrap no just don't
49% learning 51% building and the
numbers are not important here but
that's just there to prove you know
drive home a point that you should be
building more than just learning okay
always be building more like coding more
instead of just learning because again
learning without practical you know
usage that's that's not learning that's
just not learning you're not learning
all right before we move on to
JavaScript there are a few things that
you should start learning while you're
learning HTML and CSS and that or those
or these are a git github and command
line okay so the time that it takes to
learn these things and get you going it
should be like less than 5 hours 5 to 10
hours but let's just say 10 to 20 hours
to get yourself you know going and
getting to
a level where you can comfortably you
know start using the basic commands with
git and using github and command-line
okay and you should be using these
things every day every day while you're
doing HTML CSS and while you're doing
JavaScript and in the future because
these are like tools that you just need
to learn because you're gonna be using
that all the time it's like brushing
teeth and like you know tying your shoes
like these you just will be doing this
what it is a version control system I'm
not gonna go too deep into it but it's
just a backup system for your code okay
you can have many versions of your code
so if you make a mistake at any point
you can just go to an earlier version
and you know that you don't have to
start the project from scratch you can
just start that project from that
earlier version saving you a lot of time
and it also allows you to you know work
with many many teams as well team
members as well
github is just that gate version control
system in the cloud now you can share
your code you can work you know
outsource your project and whatnot I
would highly recommend looking these up
and learning them of course command-line
interface is just an interface or a
means to interact with the computer in
which you type your instructions rather
than point-and-click
so most people use this right to find
things
click all that as programmers we use
something called a command-line
interface
okay on Mac it's called terminal in
Windows we have PowerShell but I highly
don't recommend using PowerShell I
highly recommend getting git bash or
cygwin or something similar or you know
downloading the subsystem the Linux for
Windows and figuring that out I haven't
used Windows in a while so I last time I
checked I still didn't like it that much
it was still not as perfect as Linux but
hey it might be better but I highly
recommend using Linux or UNIX shell in
Windows instead of using the native
Windows shell because it's easier
so these are three things that you
should learn like start learning right
away so how should you learn these are
the resources right documentation like
if you want to learn get just go through
the github documentation or the get
documentation or just YouTube for CLI
YouTube or documentation if you're on
Windows install git bash on your
computer and start learning UNIX shell
or Linux don't use PowerShell you can
also install the next bash your bun - on
Windows and do it that way get bash it's
easiest as you're building projects
practice would get github and see a lie
and keep pushing the github a lot of
employers look now look up your github
profile to see your work okay so you
should be always deploying your projects
there so everybody can see your code and
progress and also you're documenting
your journey right which is amazing not
just for other people and your employers
and what would not be like for yourself
later down the road right it's pretty
beautiful again garyvee document
document alright
javascript 400 hours everything that can
be written in javascript will be written
in JavaScript I think Jeff Edward said
that and even though you know I don't
believe in that 100%
there is some truth to that right
there's a reason why javascript exists
still and why it is the most popular
language in the planet and the most
versatile language in the planet and
while being relatively easy and being
versatile okay so when I say easy I'm
saying easy to get started people are
going well JavaScript it's not easy
tenzin I I know I know okay just come on
it's me I'm not I'm not some somebody
else who just doesn't know what he's
talking about and just seeing some
it's easy to get into but hard to master
just to clarify
what is JavaScript right JavaScript is
the functionality that's how you have
interactivity on your website that's how
you can submit your forms sign up for
things and advanced animations that's
how you have logic games right all the
games you have JavaScript all the web
games out there you need JavaScript okay
and pretty much you can't have a website
these days like without JavaScript
running okay
best resources to learn javascript books
again I'm a huge huge fan of books so a
few of the books are JavaScript the good
parts I don't have it here I don't know
why I didn't put it oh I think I didn't
put it here because maybe it's a little
bit outdated but I still like that book
so I recommend going through it but if I
had to give you only like one book that
would be you don't know JavaScript by
Kyle Simpson or Chris Kyle I don't know
his name but that series is pretty good
you can find that free on github it has
like hundred twelve thousand stars or
something like that and for a very good
reason I like that book but before that
maybe start off with eloquent JavaScript
the third edition third edition again if
you go on the site it is free but if you
get the paper book from Amazon it's like
17 bucks or something
so these are the best resources to learn
JavaScript if you really want to learn
JavaScript go through a book not nothing
else nothing else nothing else is better
than going through a book it's not the
most fun and it's gonna be hard but it
is the best next one is mdn
documentation Nexus YouTube free courses
again be very careful not to waste your
time on crap tutorials you know some of
the good ones are a traversée media West
boss level up tutorials my channel but
really touch and leave don't go on there
and try to learn
everything about JavaScript from there
no well while going through a book when
you learn something then when you have
to learn something specific and you want
to augment that learning with something
else then you want to watch a specific
video on YouTube
whether it be learning you know
JavaScript design patterns or JavaScript
if statements or JavaScript closures or
scope whatever it is look for that
specific video and then augment your
learning like that and then when you're
building a project look for a specific
project to build whether it be rock
paper scissors or a clock whatever it is
pick that specific project build it
leave go back to the book okay so that's
how you should be learning don't just do
courses after courses on YouTube like
don't just don't spend more time on
in-depth blog tutorials for projects
okay so instead of YouTube I highly
recommend two written articles on just
blogs on Google they'll be well written
and more updated when you shoot a video
you can't edit it and change things
anymore right that's it
that's it all right you deploy it when I
deploy this website game over it's done
okay maybe you YouTube will release that
feature one day but we don't have a yet
and of course jab jab JavaScript it's a
paid product it's my course and that one
purpose is to get really good at pure
JavaScript and that's it but again I
don't want to make this into my course
and all that you know but like I said
again everything that you want to learn
is for free you can do it for free you
just have to pay in time effort and
energy and my course is just you know
just cutting that and that's it that's
why you're paying for that premium
paying that premium price but really
again I want to stress this that you can
do anything and
everything for free two things if you
want to get good at programming and
JavaScript I cannot stress this enough
guys these two things are the two things
that you should be always looking to do
if you guys are not doing these two
things it doesn't matter you're not
you're not getting better
you're not no matter what you say no
matter what you learn you're not getting
better and you're not understanding a
thing first one is solve algorithmic
challenges okay I actually have a course
coming out on just algorithmic
challenges and no it's not like the
algorithms for interviews like these
other developers have their products
going no no that's not I'm not
interested in that at all you can
definitely use it for that but for me
the course is more about helping you
think like a programmer but that's not
the point the point is learn how to do
algorithmic challenges okay do that
every day do that every day solve as
many as you can most people avoid this
most people the first question the first
thing they ask is can I just skip this
step can I skip the algorithmic
challenges I don't like it of course you
don't because it's hard I remember
looking at staring at the ceiling for
simple stupid simple problems for like
an hour or two just just to find out
later that it was so simple and you just
feel like you feel stupid but get
through it right the only ways through
and this will help tremendously and will
teach you how to think like a programmer
and which is very very important right
that's why you learn computer science
that's
why you learn this and when you're
building projects this knowledge and
things that you learn from doing these
algorithmic challenges that's going to
come into play a lot when you're
building projects you're gonna be able
to figure out everything very easily and
then there will come a point where
you're like I can do anything even
though I don't know how to do that thing
yet but I know I can figure it out and
that's where you want to be and it might
sound weird but some of you some of you
who are watching might be in this stage
right now and you know exactly what I'm
talking about if you're not there you
will be there if you continue to do this
okay and then you'll come back to this
video and go
tenzin I know what you're talking about
all right next thing is build projects
if you're not doing algorithmic
challenges you're building projects
algorithmic challenges will help you
with the logic when it comes to building
projects that's it don't quit you need
to sit with the problem longer fall in
love with the pain so when you're doing
a labret make challenges a lot of people
say you know tendon I suck at
algorithmic challenges and the reason
why you suck at algorithmic challenges
is because you don't sit with the
problem longer you give up too quickly
you don't sit with the problem longer
one thing I've realized is that things
changed when I again I learned this
through trial and error okay so this is
some real like this is not
something I heard and I'm telling you
this is something I've experienced it
and these are my insights and things
that I've learned and maybe it doesn't
apply to you maybe it's just I'm just a
one-off you know exception but like I
have a feeling that it will apply to you
because I know that it has applied to
all the students that I've mentored and
taught and the thing that I realized is
I gave up too quickly when I was
studying code and doing these
specifically doing these algorithmic
challenges like I would stare at a
problem for like ten minutes and if I
couldn't like get an idea of how to do
it I would just give up here like give
up here and I wouldn't do anything with
my like hands because I gave up here so
my fingers weren't moving okay but when
I just sat with the problem and you know
over time your ability to focus and
stare at a problem improves and then it
gets easier and easier and easier and
then you go you go into this god mode
where you just any problem you see even
though it's hard you can figure it out
you can just leave that one brick at a
time and then you're like okay I got
this okay process of elimination I can't
use this I can't use that that doesn't
make sense
okay maybe an object here nah it doesn't
make sense maybe a variable no it
doesn't make sense and that that process
you know that that thought pattern like
that that stuff takes time to build okay
so don't give up like you're you're not
you don't suck you just don't stay with
the problem longer okay when you're
doing research on a project don't quit
when you can't find a solution to your
problem within the first few pages go
through dozens of resources until you
find them it's not a question of whether
the solution is there it's if you are
going to find that solution so when
you're debugging your project and you
can't seem to figure out how to
implement a certain feature if you give
up just know that you you just sucked at
not being able to find that solution the
solution is there online the answer that
you're looking for is there but you just
gave up too easily in here it's not that
I'm so smart it's just that I stay with
problems longer Albert Einstein
the process start with a book or and a
good course if you're going through a
course just make sure the course is good
and it's not a buffet buffets are never
good you'll be full but don't they're
never good pause and think about the
purpose of the course you know I know we
know that if you do too many things you
end up getting nothing done well and a
lot of the courses out there just
promise you everything like we're going
to teach you this we're going to teach
you that's we're going to teach you
react JavaScript nodejs PHP back-end
front-end full stack you name it we're
going to teach you it's the one like
one-stop-shop developer course ok like
it everything how to make $10,000 how to
do this how to do that
you're not gonna that's not a good
course ok that's like the number one
sign that is it is not a good course
okay so if you're gonna get go through a
course make sure the course is good
that's all and always deviate away from
the book course once you have learned
something new think about what's
something small you can create with what
you have learned immediately not later
but immediately and work on that and
then come back and continue so when
you're going through a book make sure
that you're abandoning the book like
periodically when you have learned
something and then build something with
it again learn built not learn learn
learn learn learn and then built always
be building continuously okay present
continuously
this is why in my course I constantly
tell my students do one two three
problems or projects for every one thing
in my course but again I don't want to
talk about my course let's keep going
major keys JavaScript fundamentals Java
so these are the things that you have to
learn okay JavaScript fundamentals
datatypes conditionals functions logic
objects erase all that stuff right build
common micro components again find small
things that you can build and then build
those things one at a time don't try to
build a huge project right from the
get-go because again even if you do
build it
you're probably gonna copy somebody and
then that it's that false sense of
accomplishment again where you're not
learning anything it's the illusion that
you have learned something and that just
messes your confidence up okay there's
nothing but mess you up at the end of
the day so what are some micro
components right modal lists like to-do
lists a recipe list or whatever it is
navbar hamburger animations with
JavaScript right whatever it is like off
can canvas sidebar gallery side nav bar
form logic anything anything small that
you can think about do that like a
currency converter right a unit
converter like temperature converter I
have a three courses or free videos on
YouTube right now for
rock-paper-scissors currency converter
and the unit converter and then the
digital clock these are all free so
build like those small things keep
building because a big project or a
website it's just a combination of a lot
of small things and if you know how to
build build these small things at the
end of the day is just LEGO pieces and
you're just putting them on that's it
and that's pretty easy okay so you got
to learn Ajax
promises a single wait yes six of course
plus seven
eat little just you know look into it
you don't have to learn all that but
it's really about the problem so the
core problem-solving skills from
JavaScript and like understanding that
okay so learn object-oriented
programming prototypal inheritance so
this is the stuff that starts getting a
little bit harder and you will learn
object-oriented programming in
JavaScript and you think you'll
understand it you understand it when you
learn something but then two months
later you'll be like wait I don't get it
and then you'll learn relearn it and
then you'll be like oh I get it and then
a month later you'll go I don't get it
okay
but it's important that and that's why
it's so important that you follow up
everything that you learn with some sort
of project or problem or whatever it is
keep coding keep building don't just
learn and watch a video or whatever
because you're not really learning okay
so learn prototypal inheritance LP the
differences between them pure functions
pure functions functional programming
design patterns and go through a book
build small things a large website like
Amazon or Facebook is just a combination
of small components example login form
sign up form navbar like module comment
component make post component animation
stories check out Add to Cart search'
autocomplete you see what i'm saying
these are just small micro components on
their own but if you're going to build
anything and anything small no matter
how small you better make that good
if i'm going to hire you you don't need
to be the best but you better be good at
whatever you say you're good at or have
built already it doesn't matter what you
have built it's got to be good it's got
to look good it's got to feel good it's
got to work there can't be any bugs like
almost every junior developer out there
and every beginner developer out there
their projects are just ugly just most
of them are just plain ugly and then
there's there's always like a bajillion
errors like either the plus icon doesn't
work or it's like crooked or like some
weird stuff happens okay some weird
stuff happens
so always refactor your code don't just
finish something and go I've built it
now I'm gonna go to the next one no keep
looking at that project and make it sexy
and keep adding more functionality again
build your own from scratch maybe two
maybe three that's how you actually
learn and then larger projects okay once
you have built a lot of micro components
like 12 plus then jump into larger
projects and you're gonna transition
very smoothly okay so don't overthink
this look at websites that are already
built and make a mini clone of it with
the major functionalities like
e-commerce site like Amazon or forum
site like reddit social media site
music player app like Spotify right and
in this case right now at this stage you
don't have any knowledge of back-end so
you're not gonna be able to build like
build a website like amazon which has
databases and all that stuff
but you can build a front-end component
of it right without the backend
functionality or you can just store it
in local storage right so use learn how
to use local storage it's literally just
local storage just dots that item get
item it's that easy okay it's not hard
misconception large doesn't necessarily
mean the number of pages or components
it depends on the complexity and if you
still don't get it don't worry if you
have done all the for a for mentioned
things projects you'll understand at
that point design patterns this one's
huge don't touch any frameworks did I
say not to touch any frameworks build at
least 10 projects using pure JavaScript
the day you touch jQuery react angular
view and insert all the new frameworks
there that are being created every day
now before you're ready you have just
shot yourself in the foot and slow down
your rate of progress incredibly I
cannot stress that trust is enough guys
learn about different design patterns
and why they are important and then when
you learn react it's gonna be you're
gonna breeze through it okay so some of
the common design patterns are a
constructor module prototype factory
observer if a cait adapter and they're
way more but just pick three to five and
study that and that's it that's enough
you don't need to go crazy and learn
about all of them which you can
definitely do if you're really
passionate about it but five is enough
like go through three to five
and get the general overview of it like
high-level understanding of what they
are and maybe you know do some micro
projects with that try to implement a
to-do list app with you know constructor
pattern or a module pattern or prototype
pattern or factory pattern and not just
what but really understand why like the
why is way more important than what or
how all right so here's the checklist
before you move on build at least 8 to
10 micro projects keywords are at least
ok at least solve at least 5200
programming algorithms easy to
intermediate understand JavaScript
fundamentals well understand a few of
the common design patterns and why
they're important how they help don't
just make it work make it right there's
a difference between making it work and
making it right right and that's another
thing when it comes to courses you most
of the courses out there when I've
started learning and even today they're
they never teach you the right way of
doing it they just teach you how to
build something but it's code most
of them are just code and it's it's
quite bizarre
but I don't know I don't maybe it's just
me learn what pack at some point you'll
know when again slow is fast again that
the green dot is not really there ok
that green dot is like somewhere up top
I'm not gonna fix it even though I
already hit escape let's go back slow is
fast guys be Becky ok be a slow Becky
don't be a fast Joe ok or fast Tommy
don't just don't because you're gonna
is actually slower why is it taking
forever
okay two point one money at this point
you can start earning an income with
your coding skills you're like what yes
you can start making anywhere from
$1,000 to $3,000 a month on the side
very easily you don't believe me I can't
do anything about that but start
tutoring guys start tutoring start
teaching go on wise and take lessons
tutor calm code mentor like there's so
many sites there's so many sites
I know ton of people making a lot
of money just from tutoring alone and
it's not just other people doing it I
did it myself back in 2015 like 20
between 2015 and 2016 that's what I did
myself and that's where I got my big
jump start and you know I was making
more money than everybody around me just
from tutoring and a little bit of
freelancing but most of it was from
tutoring and even the freelancing
clients that I got was from the parents
of the kids that I tutored right and
then they would say hey you can code
right I have a you know this business
and we needed a new website and a new
marketing strategy and guess what I'm
like I got it so the reason why I'm not
touching on this too much is because I
have again a full video coming out in a
few weeks on that next one is no js'
Express Mongo hundred hours is enough to
get a solid understanding of the backend
and databases and all that stuff
okay and again you must learn the back
end if you want to be a good front end
developer what is no js' it is not a
language it is not a framework it is not
a library okay I see it so many people
out there on tutorials even and they're
like oh no js' is a framework no js' is
a library it's not it's not ok if
anybody says that they don't understand
nodejs they just touch nodejs and they
just making a tutorial because they want
to get views
it's a runtime and it allows you to
write JavaScript outside of the browser
which means you can do much more than
just create web applications because
javascript is a web language okay only a
web browser like Chrome like Firefox can
understand the JavaScript code but
outside of that nobody no device like my
phone can understand JavaScript my
tablet can't understand JavaScript
unless I actually you know install a
browser like Chrome right then yes
JavaScript will run but aside from that
on my computer it's not going to run so
this JavaScript runtime actually allows
us to write JavaScript outside of the
web browser okay so now you might be
asking what is a JavaScript runtime
tenzin I highly recommend looking that
up but hey because I'm nice I'm gonna
give you a very very high-level
breakdown of what it is okay I'm I kept
it as simple as simple as I could so
javascript is a language specifically a
web programming language and you write
that in a file with extent extent ssin
dot j us right ma'am demo j us hello dot
J's whatever it is AB dodge is but if
you want to run that you need a web
browser to understand and
that code and that's why you linked the
javascript file in the HTML and then you
opened that up with a chrome or some web
browser like chrome right and a web
browser like chrome contains a runtime
runtime environment which is just a
program which includes a program right
it's just a mini program inside a
program what is a program it's just code
at the end of the day and that program
is called a v8 engine okay which is
again another program which includes an
interpreter that can understand and
execute your JavaScript file and an
interpreter is just another program okay
it's just a piece of code but we call a
piece of code that does something a
program and it's called an interpreter
okay and no js' is just a program that
also contains a runtime environment with
a v8 engine but this time this runtime
environment has extra features added
that allows it to be understood outside
of just a browser computer iPad robots
machinery phone anywhere with no js' you
can write JavaScript everywhere now and
you can do way way way way more like
data science you name it you can do all
that so that's what nodejs is okay not a
language not a framework not a library
why if you want to be a great front-end
developer you must learn the
fundamentals of back-end or server-side
programming dynamic data allows you to
build more advanced websites with custom
data stored in the database in a server
blocks Facebook Likes comments videos
the reason you can like you have
Facebook friends and it shows Facebook
friends is because that friend list and
all the people in facebook is actually
stored somewhere in a database
Facebook's server okay again server is
just a program on a computer that's
sitting somewhere else in Facebook's
warehouse or server house whatever you
want to call it right there their server
room or not it's not really a room it's
the it's huge they have like like
warehouses of just servers okay what
computers so that's a reason that's
dynamic data okay
that's why you have to learn server-side
programming it's all about data
persistence when you refresh if you just
do front-end that information whatever
you have me if you have a to-do list and
you should write some things and it
lists all all that to-do lists and you
refresh it goes away right you can put
that in the local storage but even then
if you like refresh and delete your
cookies it goes away but when you have a
database and you learn server-side
programming you can actually store that
securely somewhere in a server in a
database and authenticate it and bring
it back right when you need it and then
when you add a to-do list item have a
new item and you can think about that in
like Facebook post or whatever it is
when you make a Facebook post it
actually saves it in a back-end server
in a database and then that's why it
shows up in your profile and then when
you delete it it actually deletes it
from there
that's that's why you need back-end how
learn to how to learn how to build api's
okay application programming interface
and understand the difference between
API versus REST API okay what are the
differences between them again mdn
documentation is still your best bet you
tube crash courses blog tutorials again
just folk just make sure you're not
wasting your time ok make sure it's a
good tutorial Express databases Mongo so
you got to learn that as well Express is
a nodejs framework and a framework is
just a piece of code written by somebody
else that you can use in your code base
so that you don't have
do everything from scratch yourself
thereby saving you a lot of time when
you're building something from scratch
in this case I guess you're not building
it from scratch because you're using
Express right so learn about databases I
highly recommend going with MongoDB
instead of sequel because again I just
want to give you what you need to learn
instead of giving you options like hey
you can do this or you can do that you
can do this or you can do that and you
might think options are a good thing but
let me tell you son it's not a good
thing it is the worst possible thing
possible causes paralysis by analysis
and you don't get anything done and then
you just go into the debates and one
thing is better than the other and all
that just go with Mongo call it a day go
with Xpress call it a day go with nodejs
call it a day go with JavaScript if
you're doing web development call it a
day
done pick that one thing and learn that
one thing until you freaking master it
okay until you get so good that people
can't can't ignore you okay
but to-do list what the database so it
doesn't disappear upon refresh a blog
build anything that takes data from
front-end and stores data in the backend
right so start with building like a
simple to-do list app with a database in
the backend and then build a blog or
anything that takes data stores data in
the database and then communicates
between front-end and back-end next step
once you have learned nodejs it's time
to finally learn react and once you have
learned you know nodejs try to build a
little bit more projects you know like
three five maybe even ten projects but
build more projects at this point if you
have done all the things in the past
like it should take you a lot less time
to build projects you should be busting
our projects like every two days or
something like it should be so easy for
you okay at this point you should be
flying through tutorials like you should
have this confidence deed confidence in
your heart that you can you can you can
figure it out
react 100 hours probably less again
before jumping into react make sure you
understand JavaScript and make sure you
go through design patterns many
frameworks decide stop overthinking and
debating on which framework is the best
is vue.js better than react ensign is
react better than view what about
angular is it dead nobody cares go with
react if you want to go with view go
ahead just stop stop thinking about it
stop debating stop analyzing it stop
contemplating over it pick and start
there is no best options is a terrible
thing it causes paralysis by analysis
stop start learning and building you
learn one well that's it you can learn
you can pick up view very easily if you
stand react and even before that if you
understand JavaScript you can pick up
anything easily
I recommend react more demand done view
Jas has more stars on yet up but react
still has more things going on and it
was with Gatsby Jas and I'm doing some
you know having fun with Gatsby these
days for the past six months or so so I
I really enjoy react why helps you build
JavaScript applications faster more
scalable and maintainable you know you
can do everything with pure JavaScript
doesn't mean you should do all the time
there's a reason why frameworks exist
learn why don't just jump into it learn
the why don't just learn the what and
how learn why this react exists in the
first place why can't I just use pure
JavaScript right and because I'm such a
nice human being I'm gonna give you why
a little bit okay but before that if
what oh what am I saying here flow if
react Jas or a view Jas or angular seems
hard and you find yourself super
overwhelmed and frustrated and you don't
seem to get it
it's not a react problem most likely
your understanding of pure JavaScript is
very weak it's a pure JavaScript problem
a lot of people come up used to come up
to me you know when you're they're
learning react and view and there'd be
like Tenzin what is going on here I
don't understand this thing in react and
it's giving me a give me an error and
they think it's a react problem but I'm
like that's just regular good old
JavaScript problem and you should feel
excited while learning react Jas you
should all constantly be having thoughts
like wow that's all hi I have to do this
is it
that's it
again it gives from the deepest like
depths of heaven like that's how you
gotta feel you should be grateful when
you learn react not hating it not like
going crazy learning react okay like
what this is all I have to do oh my god
no more state UI sync nightmare okay
let's see do I talk about it yep
so again the reason one of the main
reasons why a framework exists is
because keeping the state your data in
sync with your view the UI is very hard
especially as your app grows for this if
you use pure JavaScript you have to use
specific proven design patterns to build
applications for scalability and
maintaining maintainability long term
you can definitely do it with JavaScript
but sooner or later as your app grows
bigger you will end up creating a
framework like react because you want it
to be scalable maintainable over the
long run but this is really why react
and these frameworks exist to make this
easier so that you can build JavaScript
applications faster okay if you think
about a Spotify app right you can go on
my site jab jab JavaScript comm and
scroll down and look at a spot look at
the Spotify app project you know you
have this play module here right and
then you have a lot of songs here and
when you play and then you have the
loader for the song itself when you
click this button the state of playing
this button has to send the signals to
two modules here and at the loader and
that thing is hard to do when you have a
big application and then now when you
have to do vice-versa right you have
play buttons here as well
and then when you click here you got to
send the message here and here and then
when you're up up top
when you're clicking on you know the
loader bar when you're seeking and
clicking on it it also has a send
messages to the other modules so it's
not that big of an app but already
there's a lot of complexity okay it's
not that complex but you can easily see
how complicated it can get as you add
more modules more features more things
okay again you can make it work but
making it right it's hard build
everything you have built with pure
JavaScript thus far implement all of
them with react and then learn redux but
really learn react well and then jump
into redux now at this point you are job
ready if you have done everything you
have spent the time you have put in the
work you are job ready okay all the
other things they're not important you
whatever you might see on job
applications and the years of experience
and all that it doesn't matter if you
have invested the time hours years
doesn't matter because what a person can
spend say I spent a year learning
JavaScript but just an hour coding every
week that's 52 hours or if somebody can
say yeah at least you know learn
JavaScript for six months but yeah I
spend like on average 10 to 12 hours
every day yeah that is 30 times 3 6 1880
that's 1,800 hours son am I doing that
math right 36 3 6 1880 times 10 on 1800
hours versus 52 hours but hey six months
year start applying to jobs like a
madman
before you apply have a simple yet
beautiful beautiful portfolio that
showcases everything you know
don't tell me show me design is
important guys design is important make
sure it doesn't look like at least
design matters go to sites like behance
dribble and look at phenomenal designs
by great UX designers and up your eye
for design ok people think you're born
with some eye for design like it's no
you it's all mate it's your mind it's
like a computer storage as it lets in
information that's how you form your
thoughts that's how you form your taste
that's how you form your eyes for design
whatever that means so get used to it
go to these sites look at what
professional designers are designers
doing don't trust your gut don't think
you're good at design because you're not
when you think you're good you're not
okay just know that what at any point in
time you think you're good
just know that you suck I even go
through this today like every day I go
through this with everything that I can
think about every time I go I'm pretty
good next day I'm like yeah I'm not
actually suck it's the dunning-kruger
effect or whatever you can look it up
work confidence is a memory of working
hard and winning hey confidence is a
memory of winning have massive work
under your belt and nobody can say
nobody when you work hard when you grind
when you hustle you're the confidence
that that deep layer not just fake
confidence okay that deep confidence
when I slept in the car and went through
all that and nobody can take that
away from me nobody nobody I'm not
saying that's the hardest you know the I
I've had the hardest situations and
things in my life no okay
like when we were small we were really
poor we had to walk two miles every day
to just get clean water and bring it
back at like 5:00 a.m. because if you
don't people other people to get it and
then the water would run out nobody can
take that away that dad that's like
that's I always call it like unfair
advantage okay it's fair but like at the
same time it's unfair because that
confidence from hard work and being
through tough things like nothing can
replace that and nothing can beat it so
half work under your belt don't just
talk like just work your github activity
should look like this okay your heat map
on your github profile should look
something like this maybe not as crazy
as like this right hey I think somebody
took a break here but it should look
something like this throughout the whole
year again work at the end of the day
you gotta have a good product in this
case the product is yourself and your
skill set if you got the skills it'll
pay the bills as cliche as it sounds
ten plus microprojects one to two large
projects case studies of one or two of
your projects where you talk about what
you learned the journey the obstacles
cool things you tried etc tell a story
like this thing I I haven't seen anybody
do this maybe once or twice but like you
gotta have right case studies for your
projects like talk about it like what
did you learn what did you learn what
what were you thinking before tackling
this project what did you learn
afterwards what did you go through
during and then talk about it right even
when you are freelancing your you gotta
have case studies of clients not just
testimonials you gotta have case studies
and it does magic
tell a story okay it doesn't have to be
long either as long as you hit the point
it can be short and still be a case
study but usually case studies are
longer and here at least ten plus micro
projects at least one to two large
projects and then 100 press hundred plus
algorithmic challenges solved okay at
this point if you're doing things right
you will have soft hundred-plus easily
even when you're doing projects you're a
solving algorithmic challenges you have
to solve them because it's just up again
just like a bunch of little algorithms
it's like problem solving and then that
builds the project and when you apply to
jobs there are many ways you can do it I
say there are two ways first way both
are legit both work the first one is the
brute force method okay and it's
guaranteed you'll get a job guaranteed
guaranteed just a matter of time you're
just a matter of time apply to at least
20 jobs every day fine ten that's 300 in
a month that's supposed to be a ten even
if you convert at one percent that's
still three jobs you have a job in a
month
most people don't apply enough be ready
to move to a different location if you
get a job when you get a job right the
guy who got a job at Hulu last week he
moved to where did he move I totally
forgot Ontario or some Portland or
something like that I have no idea I
completely forgot
but the point is be ready to move apply
everywhere don't just apply to where you
live because you might be living in the
middle of Ohio or or Maine and you might
not have any jobs there so apply it
everywhere and be ready to move be
hungry okay most people who come up to
me and say tenzin I can't get jobs
I asked one thing how many jobs have you
applied to in the last month and they'll
say um four four no you don't deserve a
job I know people in person my close
friends and they're applying to like 250
to 300 jobs and then getting like four
or five interviews maybe like ten
interviews and then it won't go to like
five and then they'll go to the five and
then they'll go to continue with the
three and then at the end they'll get
one come on be realistic guys like don't
don't think just because you send one
application you're gonna get it no
you're not gonna get it don't worry
about not qualifying still apply as long
as it's somewhat similar you can learn
things quickly at this point you can
learn any technology whether it be
coding language or whatever it is you
can learn it pretty easily so just keep
applying like apply like a madman apply
apply apply as long as it's somewhat
similar if it says you need two years
and you only have one month of react
just apply and then on the interview
just say one month I've only done one
year but I have spent three times the
amount of hours that a regular developer
who's learning react might spend you
know stress on that highlight your
strengths not your weaknesses if you
have followed all the process so far and
you haven't landed a job in six months
of doing this hit me up and I'll give
you a job this is recording like six
months ten jobs up two applications
every day 303 618 come on come on like
you're telling me you're not gonna
convert with 1800 job applications all
right so we have the brute force method
right and the big o-notation of that is
x squared it's not very scalable and
it's not it's uh you know it works but
it's not very smart so here's the
sophisticated monkey method okay
smart method select three to five
companies or maybe five to ten companies
that you really would love to work for
learn about them profile them profile
their decision-makers recruiters or
whatever it is go talk to people hit
them up on LinkedIn like employer not
employers employees there hit them up on
LinkedIn and say hey I'm really trying
to get a job there you know and I want
to get a sense of how it the culture is
like how the job process works like the
application process I would love to take
you out for a 15-minute coffee I promise
I won't you know take much of much of
your time it wouldn't mean a lot to me
that's it that's it and then you do the
same thing with recruiters or whatever
it is and learn how to sell tons and I
don't know how to sell go through a
freaking book
make a strategy alright make a strategy
just think pause
delete Instagram delete everything sit
in pain the HOD how you find peace is by
sitting in a shit-ton of pain that's how
you find peace if you want peace you got
to go right through the problems
everytime I try to run away from
problems they just they just keep
getting bigger they don't go away send a
direct message or personalized email to
the decision-maker and take them to
coffee jab jab right hook can't land the
hook if you don't jab never ever guys
like if you don't jab you're not gonna
land the hook if you don't jab you're
not gonna land the hook okay if you
don't give you're not gonna get simple
is that that's why you know people who
give a lot people who are kind they just
seem to be successful right even though
when they do things you're like they're
not taking anything they're not getting
anything why are they doing it but at
the end of the day either they're happy
either they're successful whatever it is
they just seem to be successful right
there's a reason for that and I have you
know in my life right now I'm going
through that and really every day I have
to remind myself I'm like man I got a
job I got a job jab jab jab and don't
even expect the hook but a lot a lot of
the times that hook will land against
your own will because success is the
residue of good design and when you are
jabbing you're making that design like
you're setting yourself up for success
basically you're designing your flow of
success and you're increasing the
probability your chances of being
successful or landing the hook in this
case getting a job or whatever it is
taking them to coffee and always think
what can you do to stand out be more
personal more human do you really give a
surprisingly giving a and hard work
is a crazy competitive edge now it is
crazy every time every time - all my
problems usually it's just the same
answer do I give a and do it did I
work hard if those two things are yes I
I won't be there I will not have a
problem but usually I'm having a problem
because I didn't do one of these two
things that's it good marketing starts
with a good product Steve Jobs enough
said
so good they can't ignore ignore you ok
so that's a book by Cal Newport it's an
amazing book and it talks about how you
know if you're good you don't you don't
have to worry about marketing because
good marketing starts with good product
and because marketing becomes so easier
it's just like you're not doing any
marketing but you're of course doing
marketing but it becomes so easy ok
because you're so good
so again man have work have work
projects and things under your belt work
hard like and when you have that nobody
can say ok so I highly recommend
this book I highly highly recommend
reading this book number six while
you're applying to jobs don't stop
learning solidify explore ok and time
hundred hours or really keep exploring
keep learning things because happiness
is
as progressing if we don't evolve in
progress where we're gonna be miserable
every time I've been miserable and not
as happy is because I'm being
comfortable I am uncomfortable being
comfortable if that makes sense
and it's not just me it's you it's
everybody if you think you're not you're
wrong
read a book or get some data on it
don't settle for enough polish your
understanding of CSS and JavaScript
again fundamentals the difference
between master and somebody who's new is
that they both might know how to do for
loops they both night know functions and
opie and all that but at the end of the
day the master knows how to use those
same tools in way way more difference in
scenarios okay
you know there's a Stack Overflow post
where it talks about the guy asks a
question oh wait do all programmers copy
then what's the difference then some
developer probably who's a senior
developer goes a senior developer a
junior developer just copies but senior
developer knows what to copy okay so
when people say oh everybody Google send
gets everything from Google and copies
Google no it's not the same it's not the
same when Elon Musk or Warren Buffett
says work hard it is completely
different than me saying work hard
because when they say work hard it's a
loaded it's a loaded statement they have
billion billions of dollars behind those
words and years of wisdom and all those
things behind those two words right
whereas mine is like hundreds of
thousands of dollars which is nothing
which is like they just be it's nothing
ok but that's what I'm trying to get at
it's it's there's their levels to this
stuff right so keep learning the
fundamentals and they really tighten up
your skills learn sass learn bam bam
stands for block element modifier so it
helps you
it's a CSS methodology so it helps you
write CSS clean in a more cleaner way ok
and learn sass if you learn understand
CSS well learning sass will take like
two days again two days I'm not
exaggerating guys like you can ask any
developers who are in the field for
three to five years or more and ask them
like how long does it take for them to
get comfortable and get started with a
new language or whatever it is they'll
tell you like yeah just a couple hours
five hours or less there's a reason why
build larger react readouts projects
okay once you have done all the small
ones keep building more build more guys
keep building more build more and again
keep applying to jobs keep applying to
jobs and you know again I'm not touching
on freelancing too much because I'll
have a video coming up on that but keep
applying to jobs because what is a job
it's just a client client with some
baggage quits with some things that you
don't want but also some things that you
like like job security like insurance
right security performance SSR so
security and performance they're huge so
learning that as well accessibility
that's another one again you don't need
to be the best at these things just just
to learn them it's it's not rocket
science if you just spend the time it's
it's really everything is hard until it
gets until it is not
serverless is the future so check out
Gatsby
I've been again like I said I've been
having a lot of fun with Gatsby in the
last six months or so Jam stack is
pretty cool
learn a new language like closure scheme
or C++ if you're bored closure is really
fun I learned like little schemers is an
amazing book by the way scheme is
amazing it completely changes the way
you think about code don't just learn
some similar language like Ruby or like
PHP or Python unless you really need to
learn something different like closure
functional programming or like C++ you
know something very like more like see
something very low-level learn build
things that excite you by the ways for C
like if you go to go through cs50 they
actually make you go through C which is
a bit tough but hey it's okay you can do
it I did it you can do it learn build
things that excite you congratulations
if you have made this far you're in the
very very small minority of people who
didn't give up and actually made it
through there are so many people trying
to get into this industry and most
people quit like how I quit dozens of
times most people have given up at this
point it makes sense it's hard work but
you love hard work we love hard work and
hard work is our competitive edge
decision so my story again right I would
start then quit start that and then quit
and my progress just oscillated to zero
at the end of the day just like oh so
don't do that
okay I wasted so many years doing that
just take your time go slow in the
beginning ask yourself do you really
want to do this but when you have made
that decision I don't care if it takes
you two months to make that decision but
when you have made the decision commit
then don't don't try to do any new idea
don't jump to any
ideas like just say alright for the next
two years I'm just gonna do this and I'm
gonna breathe eat sleep live this thing
and you will make it obsession guys you
got to be obsessed
then I commit it I decide it and then
that's it one thing right I'm like you
know what I've been dabbling too much
I've been dabbling in my businesses as
well and I was like I'm just gonna
commit and I made a decision and then in
2015 you know magic happens when you
just focus and just go crazy like go
crazy like a maniac and most people fail
to take action because of uncertainty
uncertainty means you got doubt doubt
means paralysis by analysis and
paralysis equals inaction lack of action
equals guilt now you've got the cocktail
of the devil kids it's the feedback the
ultimate disgusting feedback loop of
Hell okay so I'm telling you right now
don't quit I'm telling you that you can
do it I think I'm giving you certainty
right now with this video that if you do
the things in this video and you put in
the time and you think not just here and
not just follow a monkey see monkey do I
actually think you'll make it not just
because I did it because I have seen
many people regardless of age regardless
of have taught as all that's like 49
like 45 year olds change careers
completely 180 degrees he works as a
software engineer now like
I'm telling you right now that I'm
certain each and every one of your faces
can make this happen
action the beauty of action is that it
is loyal it will you work you'll get
results and it doesn't care about your
history you could be a loser for the
past waited for the past ten years ten
months whatever it is but today now when
you when you start acting you you start
getting results immediately it's pretty
it's pretty amazing compound interest is
the eighth wonder of the world Albert
Einstein says that and remember
knowledge compounds as well and if you
just do small things every day
like just one atomic thing every day
that's it you'll be successful and it
compounds and it looked like in the
beginning you look like you're not
you're not getting anything done but
there'll hit a point there will be a
point where everything just happens at
once right that's why we have so many
overnight success but it's not really
overnight success right 1% improvement
and at the end you have like this crazy
growth rate like x squared and that
exponential growth is growth happens
because you're consistent every day
don't aim to do crazy things like 12
hours right I did 15 to 18 hours for
like 6 to 12 months but I don't
recommend it and fine honestly people
can't do it because I was at a service
like survival mode I don't recommend it
it's not healthy
my died was my sleep was and I
was learning slower because I was tired
all the time whereas my friend was
sleeping in the nice like memory foam
bed his mom cooked her cooked him
breakfast and like everything whereas I
was sleeping in the car in the winter
but hey nobody can take that away from
me right that's also something beautiful
but I don't recommend you like spending
12 hours every day if you can do it go
ahead and if you like it go ahead but
sleep you'll learn faster and again
success equals micro work times time
squared
okay that's the equation for success of
any kind like this year you know I went
from nineteen point six percent body fat
to like 15 point five right now or
fifteen point three this morning you
might say it took me six months or even
a year but that's not true I have been
trying to work out and do this thing
since high school
and I kept giving up and I kept coming
back on my kept trying I kept trying you
know there are so many people who are
always like Tenzin you're just gonna
give up anyway so what's the point of
trying shut the hell up doesn't matter I
just I just keep trying okay I just keep
trying and guess what now I'm at fifteen
percent like fifteen point three percent
body fat while maintaining some of the
muscle and I'm probably gonna hit like
fourteen percent by the end of December
and then my plans are to bulk till like
hundred seventeen and then cut back 260
and then do that you know just have fun
and all I do is instead of getting mocha
in the morning I just fool my brain and
even though I want mocha a cha chocolate
or whatever when I'm walking into the
Starbucks or whatever all I do is I go
like I say some gibberish from my mouth
like I'm like black coffee black coffee
black coffee black because I gotta wait
in line right so I just distract myself
and I'm like a coffee black coffee and
my girlfriend and everywhere around me
thinks I'm crazy but like I'm like black
coffee black coffee and then when my
turn comes I'll
say black coffee to the server or the
receptionist or whatever right cashier
and she'll be like okay black coffee is
that a tall or a grande I'm like just
grande whatever and there it is instead
of 400 calories there's just 15 calories
I just dodged it and and that's it
that's all you have to do one thing
every day
success equals microwork times x squared
net worth of Warren Buffett okay look at
that right here everybody laughed at him
like everybody laughed here everybody
laughed oh it's nothing oh it's nothing
and then like fifty eighty eight point
five billion I mean most people would be
very happy here right but I think this
is just net worth so but even then so
there's no such work as small work it
could be small but it's important
because if you skip one day it doesn't
really mean you're pushing your success
by one day you're actually taking the
momentum out of that equation and now
you're pushing that success by like week
if you skip for a week you're not
actually pushing your end goal by a week
you're actually pushing it by like
multiple weeks or multiple months
all right conclusion you got to work
eight hundred two thousand hours and if
you do things intelligently and follow
the right roadmap you can definitely do
it for less probably six seven hundred
but in my experience eight hundred two
thousand hours hours is what it takes
for me it took that long for others it
has taken that long for some it took
even more because they kept making a lot
of mistakes
I mean honestly for me it took way more
than that because I kept wasting a lot
of time
the beginning but when I actually
started like end of 2014 or something
like that like 800,000 hours and I was
solid and then I landed my very first
job and all that but I didn't really
need it because I was freelancing
successfully but I really quit that job
in five days
if you guys want to hear that story
comment below sleep at least seven hours
a day if you want to be successful sleep
more don't rush
life is long have fun while doing it if
Viktor Frankl can find peace happiness
in the camps you can definitely do it
while learning to code your your view
and your perspective and your mindset on
life matters okay your identity that you
carry and your beliefs that you carry
around certain things they matter a lot
okay you can have fun while coding it
and have fun in the process like a
journey and it sounds cliche but
works dude works it's it's real
it's real all the problems solutions in
the for most of the problems in the
world are just simple but we just want
to think that there's some amazing
complex solution but no it's just very
simple things giving a hard work
that's it and I highly recommend man's
search for meaning book by Viktor Frankl
it's it's good every single one of you
can do better than me question is are
you going to put in the work or put in
more work than me
that's the question not it's not a
question of evey if you can do it better
than you or not it's just the question
of whether you're going to put in more
work than me or more or you can do even
less work but more intelligent work
right don't just do it for the money
you won't last just do the research you
know just listen to the billionaires
like listen to people who have already
made it and listen to what they say they
don't just say it for
at this point I'm I have finally
internalized like this year I finally
internalized what this means and it's
it's doing wonders it's doing wonders
jab jab jab and keep jabbing and then
the hook just lands guys bonus unfollow
everybody on Instagram and social media
disable all notifications on your phone
except for phone calls why well for most
of you your phone is dictating your life
your everyday life your phone is telling
you when to check it when to check the
messages when to do what all that no
it's got to be other way around you want
to go on Instagram and that's why you
check it ok not because Instagram tells
you to ok these companies have billions
of dollars invested into keeping you on
the phone keeping your attention on the
phone like try going on Instagram right
now you'll come back like two hours
later unfollow everybody like literally
unfollow everybody because if you
unfollow everybody because if you delete
Instagram you're probably gonna
reinstall it next week anyways but if
you unfollow everybody it's it's a lot
harder to go after each one and track
each one and follow
so just unfollow everybody hit the gym
eat cleaner sleep I cannot stress sleep
enough when you sleep you have energy
you have more energy and you you will
make harder decisions when you are tired
and you're sleep-deprived you think it's
not a big deal right I used to brag
about this now I'm finally again this
year you know I finally realized the
importance of sleep and what I realize
is you know I I don't have good quality
to see I haven't had good quality of
sleep for the last many years I'm
finally starting to fix that and it's
doing wonders I have energy now I'm
willing to do hard projects and before I
used to think it was all about my
willpower and I'm like man
lazy I'm lazy no I'm not I'm not
lazy I know that but what it was is I
would I was teeth I had teeth grinding
right because because of sleep apnea or
something like that it was just a mix of
this bad cocktail okay so I started you
know wearing a night guard and then that
stop the teeth grinding which stop the
sleep apnea and then I had much more
energy and then I would do cool stuff
and hard projects whereas before I would
just postpone everything because I just
tired all the time right
so definitely sleep eat cleaner hit the
gym and you have a sacrifice going out
drinking vacations parties if you're not
sacrificing for your dreams you're
sacrificing your dreams for that if
you're not sacrificing for your dreams
you're sacrificing their dreams
you just got picked go to meetups and
find like-minded people because your
environment is the ultimate predictor of
your success not your willpower success
is the residue of good design and you
know again this year I've realized that
not just you know I've known this for a
while I've understood that for a while
but you know this at each level this is
a different level of understanding your
knowledge compounds that the tens in
three years ago when he heard work hard
he didn't really get it that's henson
today when he hears work hard it's
different it's different it's the same
words but it's different so find people
who are like-minded like you and who had
the same goals and values and let me
tell you that will do more and help you
more than you know your willpower and
whatever tools and tactics and calendar
and meditation that you try to do
yourself environment if you design your
environment it just flows it just flows
okay yours everything becomes a lot
easier right that's why people get
mentors and all that and that's why I
have mentors and that's why I spend
money because I want I don't want to
repeat and do trial and error and then
learn it that way because I've done that
enough and it's not fun but when you
can't afford it you got to pay with your
time work and effort that's it
peace
[Music]