live_tv
Livestream Starting Soon
00
Hours
:
00
Minutes
:
00
Seconds
Up next in 10
Coding Was HARD Until I Learned These 5 Hacks! Dive into the world of coding effortless mastery with me as I unravel the essential hacks that transformed my programming journey. From overcoming common obstacles to implementing life-saving shortcuts, these strategies are a game changer for beginners and seasoned coders alike!
Whether you’re smashing your first lines of code or debugging nightmarish errors, these tips will supercharge your coding skills! Don’t let coding overwhelm you any longer! Join me in this ultimate journey from confusion to clarity!
Hit that subscribe button for more coding wisdom! #CodingHacks #ProgrammingSkills #TechTips
Show More Show Less View Video Transcript
0:00
I was looking at all this math you need
0:01
to learn in order to become a software
0:03
engineer and there are so many
0:05
Technologies and programming languages
0:08
that it feels like you'll need your
0:09
whole life in order to catch up and then
0:12
on top of that you'll see all these
0:14
teenage prodigies coding 10 times faster
0:17
than you and it just makes you feel dumb
0:20
for context I've been a software
0:23
engineer at a different company for
0:24
almost 4 years now and I've gained quite
0:27
a lot of confidence in my skills but it
0:30
wasn't always like that at first I
0:32
actually struggled quite a lot to learn
0:34
programming but that was until I learned
0:36
these five lessons that I'm going to be
0:38
sharing with you today in this video
0:41
Welcome to to policy point and don't
0:43
forget to subscribe the number one
0:45
lesson I'm going to teach you is to
0:47
learn by doing the reason why people
0:49
struggle to learn how to code is the
0:51
same reason why people are bad at math
0:54
people are just too lazy to practice
0:56
problems and power through adversity
0:59
instead will look for shortcuts that
1:01
will get them the job done without
1:03
really taking the time to
1:05
practice I see so many people online
1:08
complaining about how much time they
1:09
spend learning how to code and then when
1:12
you ask them to show you their code they
1:14
haven't written a single line they just
1:17
spend countless hours watching YouTube
1:20
videos without actually putting in the
1:22
Reps the same way you wouldn't expect to
1:25
learn how to play the piano by just
1:27
watching YouTube videos you can't expect
1:30
the same for programming you won't learn
1:32
how to code unless you actually code a
1:34
lot so my advice to you is to first pick
1:37
something that you want to build let's
1:39
say a website and then figure out which
1:42
Technologies you need to learn in order
1:44
to build that website and then once
1:46
you've built the website you will have
1:48
learned a ton more than if you just sat
1:51
at your desk all day watching YouTube
1:53
videos and on top of that you will have
1:55
a piece of software that actually works
1:58
and that you can add into your
2:01
portfolio the number two lesson that I'm
2:03
going to teach you is to learn to
2:05
program not a programming language this
2:08
is a very common misconception
2:10
especially beginners often confuse
2:12
learning a programming language that is
2:14
syntax and grammar with learning to
2:16
program which is the actual difficult
2:19
part sure in order to be able to program
2:22
you will need both programming language
2:24
and knowing how to program but if
2:27
initially you just focus on learning the
2:29
syntax you will be just memorizing and
2:33
you won't be actually understanding the
2:35
underlying concepts of how to program
2:38
and memorizing and programming don't go
2:40
well together so don't do that it
2:42
doesn't really make sense to memorize an
2:44
algorithm in a certain programming
2:46
language algorithms need to be
2:48
understood on a conceptual abstract
2:51
level completely independent from the
2:53
programming language so let's say I have
2:56
this code snippet I'm just iterating
2:58
through an array the actual code is
3:01
secondary I only need to know that I
3:03
need a way to access each and every
3:05
element in the array how exactly I do
3:08
that depends on the language
3:10
implementation so it doesn't really
3:12
matter which programming language I
3:15
wrote this code I could do this exact
3:18
thing in every other language so what
3:20
you need to internalize is the concept
3:23
of going through an array not just the
3:26
actual syntax of how to do that this
3:28
abstract or conceptual learning becomes
3:31
even more important when you start
3:32
learning data structures and
3:35
algorithms it's hardly ever necessary to
3:37
be able to recite the implementation of
3:39
an algorithm in a particular programming
3:42
language but it's very important to
3:45
understand the algorithm on a conceptual
3:47
level so you can then implement it in
3:49
any given language that's why most tech
3:52
companies will let you do your interview
3:54
in any language that you want because
3:56
the important thing is not the syntax
3:59
but the ACT ual underlying
4:01
Concepts the number three lesson that
4:04
I'm going to give you is to create a
4:06
road map for yourself as beginners many
4:09
people just search python on YouTube and
4:12
start mindlessly watching YouTube videos
4:15
just because they heard that python is
4:17
popular so I'm going to Learn Python no
4:20
that is not the way to approach this
4:23
there are so many programming languages
4:25
there are so many technologies that you
4:27
can learn the first question question
4:29
that you need to clarify is what do you
4:32
want to build once you figure that out
4:35
you can work backwards to understand
4:37
what are the Technologies and
4:38
programming languages that you need in
4:41
order to build this thing so for example
4:44
if you want to build a website you will
4:46
need to learn about front-end
4:48
Technologies like CSS HTML and
4:52
JavaScript by getting Clarity on the
4:54
things that you want to build you'll be
4:56
able to create a road map that suits
4:58
your goals and it's not just mindlessly
5:01
learning anything that's out there
5:03
luckily online there's plenty of free
5:06
and paid resources that you can use in
5:09
order to get started on your software
5:11
engineering Journey now my number four
5:14
lesson is to
5:16
prioritize understanding over
5:19
everything this is probably the simplest
5:21
yet the most important advice that I can
5:24
give you in this video you have to take
5:26
the time to understand what you're doing
5:29
let's say you're coding and all of a
5:32
sudden you get this error and you don't
5:33
know what it means you go on Google you
5:36
search it the first link takes you to
5:39
stack Overflow you copy the solution you
5:42
paste it it works but you have no idea
5:45
why it works does that ring a bell this
5:49
situation can never happen to you when
5:50
you're coding and something works but
5:53
you don't actually know why it works you
5:56
need to make it a point to take time to
5:58
understand some of you might say okay
6:01
but I'm just getting started with
6:03
programming if I start to understand
6:05
every single thing it will take me
6:08
forever to learn how to code but think
6:11
about it this way if you don't take the
6:13
time to understand this problem today
6:16
whenever you face it again it will take
6:18
you the same time to solve the problem
6:22
whereas if you take the time to
6:23
understand this now you will never face
6:26
the problem again and you can move on to
6:28
bigger and more difficult ult problems
6:30
and that's the only way you have to grow
6:33
this is the best time investment that
6:35
you can make as a programmer for your
6:37
growth some of the best ways that you
6:39
can learn is by searching on Google
6:41
obviously but the best place that you
6:43
can reference is always the
6:46
documentation the official documentation
6:48
of that programming language it's super
6:51
detailed and way more accurate than any
6:53
short answer on stack
6:55
Overflow then if you don't seem to find
6:58
the answer online just make sure to ask
7:00
your colleagues your friends your senior
7:02
Engineers don't be afraid to reach out
7:04
to people and look dumb because everyone
7:07
has gone through this and then if you're
7:09
working on a very difficult problem that
7:11
is very Niche and no one seems to have
7:12
the answer to it you can always ask
7:14
online you can write a new post on stack
7:17
Overflow and if you have that question
7:20
probably someone else is going to bump
7:21
into the same issue in the future so by
7:23
asking the question on stack Overflow
7:26
you'll help people in the future to
7:28
solve the problem way faster last but
7:31
not least the number five lesson that I
7:33
want to teach you is to get used to
7:35
failing learning as a concept is simple
7:38
but it's not easy in practice when you
7:40
win you don't learn anything it's only
7:43
when you lose that you actually learn
7:45
something new therefore if you don't
7:47
fail at all you won't learn anything at
7:49
all myself at work I fail every single
7:53
day I face new issues and I overcome
7:56
them and that's when I grow if I didn't
7:59
take the time to learn from my mistakes
8:01
and face adversity I wouldn't be growing
8:03
at all so basically in order to become a
8:07
good software engineer you not only need
8:09
to get comfortable with failing but you
8:12
actually need to seek failure for me
8:15
whenever I'm at work and I notice some
8:17
tasks that I'm low-key scared to take or
8:20
that I'm not sure how to approach I
8:22
force myself to take that task and face
8:25
that so I can grow from it even though
8:28
it might seem scary at first I end up
8:31
learning so much more than if I didn't
8:33
take it and now I'm way more equipped to
8:36
face new problems and more difficult
8:38
challenges I feel like this image from
8:40
strange Planet sums it up pretty well no
8:43
discomfort no expansion so these are the
8:47
five lessons that helped me become a
8:48
better programmer so I hope that they
8:51
are helpful to you as well as always
8:54
thanks for watching and don't forget to
8:56
subscribe to policy point for more
#Programming
#Education
#Training & Certification
#Educational Software
#Computer Education