Up next in 10
Am I Too STUPID To Be A PROGRAMMER_
911 views
Feb 6, 2024
"Am I Too STUPID To Be A PROGRAMMER?" is a motivational and introspective video that tackles the common self-doubt many aspiring programmers may face regarding their intelligence and abilities. The video likely challenges the misconception that programming success is solely dependent on innate intelligence, instead emphasizing qualities like perseverance, problem-solving skills, and dedication as key determinants of success in the field. Through personal anecdotes or examples, the video may inspire viewers to overcome their doubts and pursue programming with confidence, highlighting that anyone can become proficient in coding with the right mindset and determination. Overall, the video aims to encourage aspiring programmers to believe in themselves and their potential, regardless of any perceived limitations or doubts about their intelligence.
View Video Transcript
0:00
Am I too stupid to be a programmer
0:03
In this video, I'm going to talk about why you are too stupid to be a programmer, and then
0:07
I'm going to talk about some of the qualities needed to become a good programmer
0:11
When it comes to math, if 2 plus 2 equals 4, then you're golden to become a programmer
0:16
If, 2 plus 2 equals 8, you are definitely too stupid to be a programmer
0:21
If 2 plus 2 equals 22, then you might actually become a good programmer
0:26
If you'd rather spend 10 years working on the most perfect sculpture instead of making 10 excellent sculptures during that same time period, then you're probably too stupid to be a programmer
0:37
If you think that sushi is a form of martial arts or you don't know how to hit the like button, you're definitely too stupid to be a programmer
0:44
All jokes aside, you may think that you are too stupid to be a programmer, but you probably aren't
0:49
You're probably actually smarter than you think and more capable than you think. Because most of what we do as programmers are things that you're
0:56
you can learn to do. It'll just take time and it'll take effort. Most of the traits that are needed
1:01
can be acquired. Here's some of the things that you should be developing if you want to become a programmer
1:07
Do you like to learn? Learning is a very important part of being a program. Everything we do involves
1:12
learning new things as we try and figure out and solve problems and learning new technologies and
1:16
programming languages, tools and how to deploy things and, you know, become better at what we do
1:22
more efficient, write more performant code and things like that, there's a lot to learn
1:27
And even learning is something that you can learn to do if you apply yourself and practice
1:33
Now, one of the tips that I have for learning is that as you get started learning about programming
1:38
and stuff is to really focus on learning the essentials, the basics, the things that are going to be
1:45
used on a practical basis. Don't get off into the weeds, trying to learn all of the little nuances
1:51
of any given programming language. You know don spend time or waste time trying to learn these you know obscure ways to do 100 different bitwise operations and things that you know you actually never see in any code that is being written
2:07
Because what will happen is if you learn that step, first of all, you may forget most of it
2:11
But even if you do remember, if it's not something that most people are using and you go and put it in code
2:16
And this has happened for my own personal experience. I saw something that I was like, oh, that's really cool
2:20
Way to do it. I did it. And then everyone was scratching their heads during the poll request of like, what are you doing
2:25
I've never seen this before. That makes sense. And sometimes when people encounter that, they'll be like, oh, that's cool
2:30
That makes sense in a good way. In my personal case when that first happened, it was in a bad way because it was just confusing to other people and having to explain it
2:39
And if you have to like write and put in comments to explain what should be like a simple operation
2:45
whatever you did to simplify things, didn't simplify things. It actually just made it more complex
2:50
So don't get into the weeds with that stuff. Focus on the core things and how you do
2:55
that is by actually building things because if you're building things then you are
2:59
learning stuff you need to solve problems related to actually building things and I
3:04
would like to call that just in time learning instead of like reading from cover to
3:09
cover is you're gonna learn things as you actually need them and you find out what you
3:14
actually need as you encounter them while actually building stuff another trait is you
3:18
need to be self-motivated in this industry you're gonna have to work really hard to
3:22
you know solve problems and you're gonna be a expect to do that without having your handheld by a lot of other people. Because if you're
3:30
tying up other people's time, software engineers are paid a lot of money and companies aren't
3:35
going to want to have someone who is constantly using a lot of other people's time and
3:41
preventing them from delivering value. It's very common and normal to ask questions and that's
3:45
totally okay. It's just you need to be able to do most of your work on your own. And if you aren't
3:52
someone who likes to just get in there and work hard without being told what to do then you might not do well as a programmer It also important to be a problem solver rather than a problem creator or complainer
4:06
Everything we do is solving problems for customers and finding solutions and how to solve those problems more effectively and how to do it in a way that we don't
4:16
have to keep solving the same problems over and over again. But if you like solving problems and figuring things out and how to make things work
4:23
good stuff that's definitely a quality of a good programmer. If however, you get frustrated really
4:29
easily and especially problem solving and you encounter a problem you just can't work through
4:34
and you spend eight hours trying to figure out how to make this one small thing work, if that
4:41
frustrates you and you get angry and upset and can't control your emotions, then you definitely
4:46
aren't cut out to be a programmer. There are times where you might have a bug that you're
4:50
trying to reproduce and you may spend all day trying to reproduce it unsuccessfully. You might be in
4:57
this situation when there's a really tough deadline and something needs to be fixed ASAP and a lot of
5:03
people are getting antsy up in management about why isn't this fixed and it's a very obscure bug
5:09
and you need to be able to have patience not let those emotions of frustration cause you to get overwhelmed
5:15
and you just need to stay focused and keep working through things. But if you're easily like
5:19
frustrated and get angry when things don't work out the way that you want, you probably aren't
5:24
going to be a good programmer. It's not that you're stupid. You're just lacking an area where you need
5:28
to have more patience. Also, if you want to be a programmer, you should be able to type at least
5:32
90 words per minute. If you don't, you aren't going to cut it. Just saying. I'm just kidding
5:39
You don't need to type that fast. You do need to be able to type and preferably not chicken pecking
5:44
If you're chicken pecking, you probably do need to work on some of those skills and that is a skill you can
5:48
acquire with practice to be able to type at a reasonable pace. But as programmers, we are not typing
5:54
nonstop for eight hours a day There a lot of time spent where we pause We think about what we going to be writing trying to figure out the best way to do it and then we type you know write out some of the code
6:07
and then we might pause and think about it and stuff. So I mean, typing fast is good because you're going to be more productive, but you don't
6:13
need to be like some amazing, you know, person that is able to type at crazy speeds
6:18
You also need to be able to take constructive criticism. time when you go to check in your code and merge it into the main code base, there's going to be
6:27
something called a poll request where you request that other software engineers, review the changes
6:33
that you've made, give feedback if there's something that they see could be improved upon
6:38
and then you make those changes before actually merging into the code. What this does is it helps
6:43
improve the overall quality of the code. And as we get feedback from other software engineers
6:48
then we learn better ways to do things. And it doesn't mean that every piece of advice you're giving
6:55
or every correction that someone suggests is necessarily the right correction because there's a lot of things where it is just opinion
7:01
But there are going to definitely be times where there will be things that you could do
7:05
to improve the code. And maybe it's because you were rushed or maybe it's just because you hadn't looked at it
7:10
from a different perspective. But by having more eyes on the code
7:14
the code will become better and you will become better as a programmer over time. So being able to take that criticism without taking it personally and using it as an opportunity to learn and improve is definitely an attribute needed for being a good programmer
7:30
All right. And now that you know that you probably aren't too stupid to be a programmer and you have an idea of some of the traits to develop to become a programmer, you should watch this video on how to become a programmer in nine months
7:40
And I'll see you in the next one, Lates. You know
#Education
#Programming