Learn Coding Fast - Subtítulos bilingües
Yo-yo, how you doing?
Step here.
So this video, I'm going to give you nine tips on how to learn coding very very quickly.
In fact, if you follow these nine tips, you're going to learn how to code much more quickly than you could possibly otherwise.
All so number one.
You want to do a minimum of 20 minutes a day, four to five days a week.
20 minutes a day, four to five days a Why do I suggest this?
Hey, guys, this video is sponsored by PenPod at PenPod dot app.
This is an online visual editor for your web layout.
Very powerful, supports full grid in their brand new 2.0 version.
It's free,
by the way,
it has all kinds of capabilities in there,
group asset management, easy collaboration amongst team members, annotations, and so much more, check it out, PenPod dot app link is below.
it's pretty powerful and it's free.
Let me put it this way.
frequency of exposure, the more often that your brain your brain is exposed to coding, the more quickly you will learn to code.
It's not necessarily about how much time But it's about the number of times that you put in per week now
I say four to five times a week because if you do too much You're gonna overload yourself.
You got to give your brain a chance to rest because when you're learning something new you're creating new connections in the brain
And these are physical connections.
So as any bodybuilder will tell you,
if you're building new muscle, you're building new mass, you've got to give your body a chance to rest.
So four to five days a week, 20 minutes a day minimum.
Now, when I mentioned for you.
being more important than the actual raw time.
Let me give you an example.
Let's say you were working on coding an hour a four days a week.
So that's four hours a week.
Or on the other hand, let's say you just said on Sunday I'm gonna do seven hours.
Even though you're doing three more hours then The previous person was doing four one-hour sessions per week.
The person who is training four times a week is going to get better progress because when you expose yourself daily an hour,
you give yourself a rest, another day an hour, you give yourself a rest.
and so Those separate occasions are going to have more impact in terms of how quickly you learned to go.
Then if you sat down one day and did seven hours.
Frequency of exposure is more important than the actual time.
So when I say do 20 minutes a day,
four or five,
four to five days a week,
the 20 minutes is to bear It's a psychological trick to say 20 minutes because what that does, it creates less resistance in your brain.
So if you are, let's say it's Monday and you just don't feel like it, I don't feel like coding today.
Uncle Steph, I don't want to code today.
Just do your 20 minutes.
20 minutes is far easier to start than an hour or three hours.
So just do that 20 minutes a day.
A lot of times at 20 minutes, by the way, we'll turn into half an hour, 40 minutes.
That's so important that even in my training software, I develop my own training platform that a bunch of schools use.
In that training platform is actually designed around that premise where the system makes
it easy for you to do that minimum of 20 minutes a day.
How it works is when you log in, you have these short little lessons that are six minutes each on average.
You do your quizzing.
So if you do just three or four little lessons,
you've got your 20 minutes in and if you don't feel like it,
you can just leave and then the system remembers where you left off so you go back, boom, you up again.
That's why when you have courses where they have 30-minute and 40-minute long
lectures and not too much quizzing and they're not news effective.
Anyway, you four or five days a week, minimal 20 minutes.
Why four or five days a week?
Why not seven days a Well, because you've got to give your brain time to rest.
As I said, just like bodybuilders will tell you they train, they train, then they got to rest.
They got to have rest days.
You got to give your brain a little rest time,
a little downtime so that it can assimilate the new information that you're giving it the new information being the code.
Nothing the best for Uncle Steph,
a mid-cafe action to get the brain Tip number two, you want to learn more than one programming language, ultimately.
So you don't jump around.
So let's say you decide you're going to learn Python first, for whatever reasons.
You Python, you do the Python course, you do the whole thing, you sure you complete it.
The worst thing you can do is start a course and not complete it.
So, good foundations, Python course, boom, you that off for a good foundation, JavaScript course or a good foundations, PHP course, doesn't matter the language.
But you want to pick that first language,
learn from A to Z, do the basics, you're not going to learn the whole thing because these languages are vast.
Even the professional developers knows everything about a particular language, even one that they use daily.
So example, I've written software nine languages over the years.
And my main language for several years was...
My main language for several years was Java.
But I maybe used 10%
of Java at best,
even though I was aware of the other aspects, the swing in AWT and threading and so forth, but I hardly, if ever, used them.
And I was a pro Java guy, a very, very, pretty high level there for years.
So don't worry about learning everything about a language,
a good course will pick out the things that you need to know and then you move on from there.
If you don't know my content,
something one of my principles that I teach in software development is that you have to have,
excuse me, there are aspects of programming that are Those are the key fundamentals, as I call them.
Don't confuse fundamentals with basics.
The fundamentals include the basics, but the fundamentals also include some pretty advanced stuff.
So you get the key fundamentals,
and then you have this category of technology within languages, within the whole program ego system, I call it the need to nerd stuff.
The stuff that you've got, Oh, we need to learn on a per-case basis.
When comes up, oh, I'll learn this.
So once you've learned that first language, the fundamentals of the first language, you should learn a second language.
Why?
Because by learning the second language, it will give you insights into the first language.
So for example, you started with Python in this hypothetical.
And then the next language you decide to learn for whatever reasons is, we'll say, JavaScript.
By learning JavaScript,
first of all,
you're going to learn JavaScript in a fraction of the time because you're going to see that Python,
JavaScript, C-sharp, Java, PHP, Ruby, they all share many, many, many of the same principles and ideas.
There's differences here and there, but they're very, very similar.
Anyway, so you're learning JavaScript as your second language.
You get a fundamentals course on JavaScript.
You that, boom.
You're going to learn it first of all in a fraction of the time.
Second all,
by learning how,
for example, JavaScript handles data types, how JavaScript handles functions, how JavaScript handles arrays, you're going to compare that the way Python does.
And you're going to see the differences and the nuances.
And will happen is you're going to have a deeper understanding of Python arrays and data types and methods and functions.
It's just give you that contrast and comparison is gonna give you deeper insight into both languages, really.
It's like learning to drive, it's like learning to drive a car.
You don't really know what kind of vehicle you like until you've driven SUVs, sports convertibles, whatever, pickup trips, whatever you want.
Electric versus gas, whatever you want.
You have to drive multiple cars before you really figure out what's best for you, what you kind of like.
Everybody's different.
Tip number three,
a key aspect of the daily exposure to code in the four or five days a week is that you actually have to write code.
It's very, very important.
I made the mistake early on when I was learning this stuff back in the 90s,
was to get too much, get too caught up in the theoretical.
I would buy these big thick nerd books, and would read them and study and take notes, learning this stuff.
And in my mind, and theoretically, I had a grasp of concepts.
But when I actually sat there, sat down to write the code, it was like I was a total new.
It was crazy to me.
I all these books.
I took all these notes.
I could answer always theoretical questions.
But when I actually came down to writing code, it was terrible.
So you have to write the code, even if you don't understand the code.
That's common by the way.
A lot of times when you're learning to be writing code.
And you get a little chunk of code to work.
But then you don't understand why it's parts of it are working.
Like, why is there a return type?
Why I'm doing recursions?
So why am I instantiating this class?
What's the point of this?
What's the point of creating a variable?
These will be unclear to you at first.
But write the code.
Comprehension.
comes from practical application.
People tend to think of it in reverse, because of the lunacy of colleges and universities.
They tend to get focused on the theoretical, assuming that if they're theoretical masters, they'll be able to implement the practical effectively.
That's total bullshit.
It's the opposite in fact.
Through practical applications comes theoretical comprehension.
When we say that again, through practical applications, who are actually writing a code for real, will understanding happen.
It's a weird phenomenon.
You're going to be writing code, you're not going to understand, you're going to writing code, you're not going to understand.
I've even written commercial code,
meaning I got paid to write code and I wasn't quite sure what the hell the code was doing, but I just knew it worked.
And then one day you'll wake up and your brain will make those neural connections, and I'll send all that stuff was unclear to you.
daily code, write daily code, write daily code, just little bit of a Even if it's like, just write a couple of you're doing JavaScript.
Write a couple of functions,
run through an array, you if you're working with JavaScript in the DOM, do some DOM targeting, you very simple, 20 minutes, daily exposure.
tells the brain
that What you are learning is important what you're exposing to it is important
So the brain is going to put effort into creating those neural connections so that you learn faster
Remember your brain is designed to save energy because for most of humanity,
we were hunter-gatherers, we didn't have McDonald's to go to 20,000 years ago, right?
And the brain was, which uses a ton of energy.
About% of your energy, I believe.
Learning something new takes a lot of energy.
That's why you're tired after an intense day of learning or intense day of coding, where really thinking hard.
It a of So you, the brain by design is looking to save energy.
So the time,
so if it deemed something unimportant,
it will not put energy into it and you're gonna forget about it or you won't have comprehension, you won't understand it.
But if you teach the brain about what you're trying to do here,
in this case,
learning to code, if you teach the brain that this is a brain that then the brain will put effort into learning this stuff.
It will put energy into the process.
And do you tell the brain?
One way to tell the brain that this is important is by daily exposure, daily exposure, daily exposure.
Practical exposure.
Tip number four.
Once you get your code to work,
so let's say you're working on a chunk of code,
you get your function to work,
you validate that email as an example, or you get that gaming loop to happen, or get the collision detection working.
What you want to do next is you want to break the code,
you want to purposefully break the code that you just got Break it and look at the error messages that are produced.
Look the behavior.
By getting code to work,
breaking it, watching its behavior, watching the error messages, then it and then fixing it, then breaking it in another way, watching the error messages.
This is a nice hack that will speed up the learning process, okay?
It's because you're going to start.
Seeing what error,
what problems in your code create what errors and what behavior,
which will make it much easier for you to debug, which a big part of your coding life will be debugging by the way.
Tip number five, take breaks, take coffee breaks, take walking breaks, go exercise.
Just like if you were lifting weights, training, you have to give yourself breaks.
You to give your mind time to assimilate the knowledge.
So take breaks.
Again, going back to tip number one, where said you learned to code four or five days a week, you've got to take days off.
You learn Monday, Tuesday.
Take Wednesday off.
take Saturday off, Sunday off, and again Monday.
Something like that.
Take breaks.
Don't be afraid to take breaks.
Even, let's say you're on a marathon coding session, you got to take breaks.
It's good to take breaks just to give your mind to rest.
You know,
if you're sitting there for an hour,
you don't If you're finding you're getting a little strained,
get up, go walk around for half an hour, go exercise, do away from the screen.
Take a break.
Tip six, drink water.
You want to be very hydrated.
Drink of water.
How much water you should drink depends on how big you are, your body weight, you can look that up online.
Generally speaking, when you go to the bathroom, if it's not.
you need to drink more water.
That's the general rule.
So, yeah, drink water, it helps lubricate everything, it will help you think better.
Tip number seven, again, people are going to freak out, exercise, healthy body, healthy mind, healthy mind, healthy body.
This old, old information, nobody disputes this, get in shape.
If your body fat percentage is over 20% as a man, you don't exercise on a regular basis, you are inhibiting your cognitive capacity.
That's just plain and simple.
So, if you're overweight and you're pretty good, I'm down, if you get in shape and you get lower body fat percentage, you're going to think much better.
It's just the way it is.
Number eight, this is something that more, very high performance people understand, meditate.
It's good to clear your mind and do some basic meditations,
mindfulness meditations, and there's all kinds of different types of meditations you can look up.
It's really very, very impactful in terms of your psychological self, your self.
and this, of course, coding is a very mentally intense endeavor.
Meditation will help, may want to start including meditation two or three times a week.
I know some people who run very big corporations and meditations are crucial.
They daily guided meditation.
for them to stay performant.
So yeah,
if you want to really start refining your methodology,
you want to really start supercharging your coded your code learning processes and all their aspects of your life, start meditating.
And tip number nine,
the last tip, You want to spend no more than three to four hours max coding or learning to code in a particular sitting.
Why?
Because something new,
anything new, especially something complex like coding, And the brain can only work at maximum efficiency for the average individual three, four hours.
Some people can push the five to pay on how healthy you are and so forth.
But to four hours is typically maximum peak efficiency.
After that, your cognitive capacity plummets, and it's kind of pointless.
Like you know,
if you're going back to bodybuilding,
if you train in the gym eight hours a day,
you're just going to, you're going to do the opposite of it, have gained, you're actually going to be hurting yourself.
I talked to physiotherapists, they've told me an exercise specialist said most athletes over train, they damage their bodies, they're actually inhibiting progress.
Same thing with learning to cope.
So you try to do too much in one sitting, you five, six, eight hours a day, you're just going to slow your own progress.
You've got to give your brain time to rest.
So maximum on a particular sitting when you're learning.
Even if you feel it, I've done my four hours about discipline.
You've your first go exercise, go walk, go do anything but be in front of a screen.
Very So you go.
Those are the nine tips.
These tips, by the way, are based on a few figs.
A, I've been a professional developer since the 1990s.
I several commercial products, including my own SaaS product.
and on top of that,
I've been in education for over a I curriculum and software to school,
so I understand this stuff very well because I've just been in the game for so long.
So there you go.
That's follow these tips and you will learn how to code far more quickly than you would otherwise.
I'm Michael Steph, if you're interested in my Check out UncleStep.com links below, or you can take my solo learning courses on my platform.
Unique platform,
and because of, well, it's unique because we developed it from scratch, working hand in hand with a whole bunch of districts over the years.
It's super refined.
Thanks for watching.
like and comment all that kind of stuff if you have any questions about any of
the content let me know below in the comments if you like this content let me
know in the comments don't be afraid to share the video as well.
Cheers guys!
.
Idioma de traducción
Seleccionar
Desbloquea más funciones
Instala la extensión Trancy para desbloquear más funciones, incluyendo subtítulos de IA, definiciones de palabras de IA, análisis gramatical de IA, habla de IA, etc.
Compatible con las principales plataformas de video
Trancy no solo proporciona soporte de subtítulos bilingües para plataformas como YouTube, Netflix, Udemy, Disney+, TED, edX, Kehan, Coursera, sino que también ofrece traducción de palabras/frases de IA, traducción inmersiva de texto completo y otras funciones para páginas web regulares. Es un verdadero asistente de aprendizaje de idiomas todo en uno.
Navegadores de todas las plataformas
Trancy es compatible con todos los navegadores de plataformas, incluida la extensión del navegador Safari de iOS.
Modos de visualización múltiple
Admite modos de teatro, lectura, mixtos y otros modos de visualización para una experiencia bilingüe integral.
Modos de práctica múltiple
Admite modos de dictado de oraciones, evaluación oral, opción múltiple, dictado y otros modos de práctica.
Resumen de video de IA
Utiliza OpenAI para resumir videos y comprender rápidamente el contenido clave.
Subtítulos de IA
Genera subtítulos de IA precisos y rápidos para YouTube en solo 3-5 minutos.
Definiciones de palabras de IA
Toca las palabras en los subtítulos para buscar definiciones, con definiciones impulsadas por IA.
Análisis gramatical de IA
Analiza la gramática de las oraciones para comprender rápidamente los significados de las oraciones y dominar puntos de gramática difíciles.
Más funciones web
Además de los subtítulos de video bilingües, Trancy también proporciona traducción de palabras y traducción de texto completo para páginas web.