There is actually a pretty good ted talk about the 10,000 hr assertion about learning a skill. It does not take that long but as in everything it just takes time. Faster for some slower for others. Side note: BFA is in three days!!!
Kaczynski and return functions are those functions that do stuffs in the function block (like in curly braces in function(){}) and when they are done they give u a value,like "return X" it gives U X... If u combine both examples: Function looping(){ Variable X =0; for(I=0,I
0:00-Intro 2:50-Building momentum 3:47-Diversify your learning 5:16-Projects and your portfolio 5:48-Find a Mentor/Community 6:39-Outside Influence 8:30-Closing
Good warning about outside influences! When I first started coding, I was so excited. I had a plan all figured out about what I would do and how I would get my first coding job. I had a schedule for my learning, I had a list of projects I wanted to do for my portfolio. My older brother is in IT but not a coder, but I was excited so I told him all about my plans. He literally laughed in my face. His exact words were "Sorry Honey, that's not going to happen. No one's ever going to hire you." I spent the next month panicking because I had already quit my job at a library to work on learning coding to change my career. After talking to some people that are actually working in the field I feel a lot better about my plans. But for a while I was seriously thinking about quitting coding and just getting a minimum wage job shlelpping boxes at a local warehouse. I'm glad I didn't do anything I would regret for the rest of my life.
@@johnnastrom9400 I learned programming in Python since the age of 13, scored an A on a college course in Python when I was 14, and today can program any application or website and another 10+ languages, yet I mostly call it "coding" because the word "programming" is to long to spell or pronounce. The only different between the terms "coding", "programming" and "developing" is that coding refers to the actual typing in the keyboard to produce sourcecode, programming is creating an algorithm and integrate it into a bigger system, like you program a robot. Development is when you build or contribute to build the whole system from scratch. - development of a website, development of a platform.
20 year game dev vet here. I just spent 7 hours debugging a hobby car sim I'm working on. Tires wouldn't collide with one of the track triangles. Turned out I had a + sign instead of a - sign in an equation. So yeah, that happens a lot.
The 10000 hours thing was popularized by Malcolm Gladwell, but he did not mean for it to become the ironclad principle it is today. Take it with caution.
@MrTron But it's nebulous - there's breadth vs depth. What exactly would you work on for 10,000 hours? HTML and nothing else? Javascript? Bootstrap? Or a bundle of ten or fifteen languages / frameworks / processes?
Dude I love your videos, you're so genuine and you're really trying to help people, not like some channels where they make videos just to make a video on youtube to get views!
first time coding i made my first project an encoder. pretty simple. making the decoder did take a few weeks though, even though i were discuraged by those around me, i still finished it because i felt like it was something i wanted to do. and damn it felt good when i finished it. i had no real knowlege of what i was doing when i started at all, but it works, and i created it on my own.
I was only supposed to make the zumo go in a square, but I made it spin, backtrack, go fwd and back, charge at the spectators, and then twirl at the end. The last lot of acrobatics took one hour to program. The square took, on and off, a year....
Practise whatever skill you are learning. A small project incorporating each, or most, of those concepts can be a motivator. When you are learning the new skill or concept, write a few trivial programs before incorporating the skill / knowledge into the small project previously mentioned. Accept the reality that you will spend 90% of your time debugging and 10% of your time moving forward with the project.
Good video! I felt very related with 2 things 1 ideas that snowball, think a small bad thing and you dont do it eventually, think positively and youll go do it eventually. 2 also some time ago i learned the "start with something small" thing. I would always procrastinate but i learned that if i only write one line of code the rest comes out of your fingers so easally instaed of thinking oh i need to program this 1000 line thing now. Its all about the mindset
yea my mother has critiqued every venture outside her knowledge set that I have wanted to pursue. it had taken me years to realize this contributed to me losing interest in things.
Here is my "stab" at why people quit learning (to code, or anything ). People have this idea that you must be a gifted / high IQ person to learn to code, because its a "computer nerd" thing to do. As for me, I spent about 2 years learning to code in my spare time, just practicing from tutorials and trying things on my own. I would learn one thing, then another and so on until I got motivated enough to go into programming full time. If you went to college, you would spend 4 years working on a CS degree, another 6 months or so doing an internship to land a junior position. So really, if you are going the self taugh route, spending 4 years, to get the hang of it is not bad, that just the learning curve.
@@cautarepvp2079 nothing called too old, it's just a word you put in your mind, the oldest student that learn C# programming to me is 75 years old, he learn it so he can motivated his grand child to be a game programmer instead of just playing game, in the end he can make some cool simple game by himself and show it to his grand child
@@cautarepvp2079 that's true. One of my uncles asked me if he's too old to code, but the fact is you're never too old to code. Don't care about what other people think.
@@anonofDeath the problem is not if you are to old to code, but if you are good and marketable enough to make a living out of it and in good circumstances lots of money
@@cautarepvp2079 you see, this is the problem. You code for the sole purpose of money and not exploration and the engineering process. Of course, money is attractive but it should be a by-product of why you want to code, not the goal of it.
In my experience do not talk about your visions because people will mostly just down you for it and it discourages you. Most people has little to no vision for their life. Do not let them drag you down. Just have your vision and fucking surprise them.
10,000 hours = A scare tactic to prevent people from starting a new hobby or skill. An excuse as to why they are not good at something. 100 hours = will make you better at something than 99% of people. As 99% of people are unlikely to be learning what you are. 1000 hours = To get as good as you can at something and reach your ceiling. ...I hope this helps.
No, Jacob. That's definitely not true for a job. Spending 100 hours at a job (which you will do within three weeks) does not make you a master at whatever job you just started. Far from it. How could you make this assertion? The 10,000-hour number comes from Malcom Gladwell's "Outliers" book, wherein he wrote about an elite group of individuals who had achieved excellence in a certain field that made them stand far above the average. Those individuals had usually put in at least 10,000 hours of practice into their craft.
I agree that 100hr will make you better at something than 99% of the people, but that is still basically just entry level. When I went to do my AWS Associate Cert, I started from zero AWS knowledge, and it took me approx 300hr of studying to feel confident enough to attempt the test (I passed it, but it was not easy. I thought I failed originally). And ironically, AWS Associate Cert is still basically just an entry level Cert, useful for showing you understand the basic concepts, but don't ask me to work on your Lamda functions or clean up your IAM roles, 'cause I'll have to hit the books again to refresh my memory.
Damn josh your so right I haven’t studied coding for the past 6 days. Your right studying a little bit everyday is better than doing nothing at all. From this day on even if it’s for 15 minutes I’m going to do something everyday. I was supposed to see this video. Thank you!!!!
I spent a month learning code and made a game but it was slightly buggy and I figured out having a simple leaderboard or anything multiplayer plus getting rid of bugs was so much more work that it was really something I had to be ready to commit my working life to. So I was smart enough to not try to solo develop my dream game but I still underestimated just how much extra effort there is between making something that kind of works versus making something that is a consumer product. How many people want to play simple games these days that do not have leaderboards or multiplayer? Not many.
I hate the 10000 hours. It's 10.000 hours to "MASTER" something. To become the Steve Vai (or some other virtuoso) of the thing you learn. You only need 20 hours to be able to play. And then you play around to your hearts content. And through play you learn. And then you can use what you've learnt to build something epic. Though i'm learning code for fun so the motivation might be different.
Even putting in half-assed effort pays off over time. Do something! Try! Fail! Keep at it! Every little thing you do in pursuit of your endeavor brings you incrementally closer to achieving some mastery at some thing.
I keep running into issues with loops, so i have been using different books/sites to try to better visualize how they work. Also working on the basics over and over again until I truly understand. I really want to do stuff that is applicable to my work, but I know I have to master the basics first before getting to that point, no matter how annoying it is.
Back in the day before OOP and GUIs became popular coding was easy, You'd learn one language and you'd learnt the rest . Now coding seems to have become an insidious endeavor in objectting and addressing code even though alot of code may only be for its sole purpose. What ever happened to keep it simple I don't know, ? We got red onions overriding green onions and I don't know where the spring onions fit in LOL.
@1:50 Arnold Swarchenegger also had this mind set. In his book he talks about days he didn't want to go gym ofcourse he would rather run around in sun with some hotties. But he said he just forced himself to go and the motivation comes while he was there.
I hate talking about my passion very few will encourage they be like "Why don't you wanna talk about it? weird" *talks about it "Lol just let it go" *instantly feeling down ... Don't even mention it, just go for it in the shadow.
1:00 exactly nobody sees the backend and the effort a individual puts in that made him big all people see is that one or two moment where you achived the goal
I'm a programmer and I fall into that trap. I feel like I need to learn a thing in a couple hours. I blasted through data science and could barely get the concept of neural networks. Then sat down to code and drew a blank on the first step.
you look better and fresher and chiller when your hair is short, but everything you say is what discouraged people like me to go on and try again, thank you Joshua
Never thought about learning code in my life. Avoided higher education like the plague, hated math, problem solving etc. That about disqualifies me from learning code
How I got good at programming: - brush teeth and thing of what coding stuff to do for the day - eat breakfast while watching coding videos - get paid hourly while programming (uni student, I got an on campus programming job) - teach a student code on Saturdays - assume I know everything and dive into a project I find interesting (game dev, app dev, etc.) - read stackoverflow - watch anime to destress - avoid social interactions unless the interaction involves programming
Do you know what ? I have no idea of how many hours I needed to become an expert. My first coding was in 1981 and so I have quite a bit experience -- I still find much to learn about in Programming.
Best way to learn coding: - pick a project that revolves around something you like. Example: you want to learn about databases and also love cooking? Make a small cookbook application - set a time limit - per day and time spent in total for the whole project - be persistent - no excuses (except life-altering injury, death or zombie apocalypse) - be on point - it's easy to get distracted once you start doing research This is a general rule and applies to everything new you think it might be useful to you in the future.
Beginning your studies with the JAVA certification exam prep class, and getting a non-verbal teacher, who ocassionally uses proper nouns, but mostly indefinite nouns, the one who refused to answer any of your questions after the first week of class? Just re-read the beginner, intermediate, and certification text books three times, and begin coding after that? Find a teacher who will use the correct jargon consistently to describe the concepts and code, or you do it?
This seems to be more about 1. why learning to code is good. 2. how to learn Maybe I missed the part about 'why people fail'? Funnily I had an idea today about why I have failed in my several attempts to learn to code. (When I first tried I was 38 btw.) My reason: I imagined a finished thing that was kinda complicated, and very often was kinda creative, and got bogged down, so that was discouraging. Another reason, in the books and videos typically there is a complete lack of big picture view, it just launches into 'do this, then do this, then do this.' This is fine for a lot of people, many smart people are "abstract sequential" in their processing style. But more divergent thinking typically are "abstract random" in processing style, so we in the latter category have a hard time processing isolated strings, without a view of where that bit fits into the bigger picture. For example, I would have loved to start with a relatively large amount of code, let's say 100 lines, and have someone point out the functions and what they're doing, and gradually get down to the expression level. Which everyone "knows" would be the "wrong" way to approach it.
All of your comment resonates with me, especially the "do this, then do this" thing. It is my least favorite style of teaching to follow. I stopped with video tutorials and used college textbooks (combined the courses with the college's bookstore/book list, then got the book however it was most accessible to me) because being told what to do without knowing why or what exactly I'm doing never sat well with me. The textbooks usually explain what something does/what situation you would use the new concept in, then give you an exercise to do that would use it after explaining, and they're usually not exact copies/parallels of the examples that they taught with. I have to actively think in order to make my code work instead of just listening to someone tell me what to do, I do it just as they said, then I encounter a problem and have little way of figuring out where my understanding fell short. The standard way to be taught, which just feels like I'm being presented with unconnected concepts at random, makes me lose interest in a subject. Thinking about this now reminds me of when students would ask why they have to learn math, then get surprised and struggle with word problems, especially ones that present the problem as a practical situation to figure out. I always felt the same way about history, but I learned eventually that tracking the actions of a person and the events of an area can help me understand a culture and be more informed when selecting a leader/understanding a new problem. The way a subject is presented by some teachers can make it seem like it doesn't have anything to do with anything. I say all of this to say that I love college-chosen textbooks because I have to actively learn the how and why of concepts in order to get through them. I'm still trying to figure out if I'd be okay with paying thousands to teach myself and just have certified proof that I could pass the tests about it when I've been able to access this information for free or close to it on my own, but that's not the topic. Right now, I'm working through "The ANSI C Programming Language" and Javascript's official guide. ANSI C in particular takes the approach that you mention at the end, presenting the reader with code and explaining what's happening, line by line. Maybe those types of things would fit you better than someone else's lesson plan.
@@typhlosionisbest Haha, your response brings back a memory. I was in a university program where there was a required course in Visual Basic. I had bought a textbook and was trying to do as you are describing. One day I was at my mother's with the book. She was English. In VB there's a command "dim sum," which I think had to do with declaring variables. My mother and I had been to a Chinese restaurant for dim sum, which as you may know is a very un-English brunch of chicken feet, squid, tofu and other exotic foodstuffs ordered from petite women pushing carts from table to table, which my mom hated. One day for some reason she looks at the programming book in which the first chapter has this phrase "dim sum," and that just sets her off. She was a little "eccentric" in some ways. For several minutes she's like, why is this book talking about dim sum? That's so stupid, what does dim sum have to do with computers? blah blah blah. I'm sure she was imagining slimy things with unusual flavours and languages she doesn't understand. She went on a rant against dim sum! It seems to activate some conversational loop in her mind. I'm like, mom, it's just an abbreviation, it's nothing to do with squid and chicken feet, really, it's a programming thing, it's for declaring variables. She's like, why would you need to declare anything, that's stupid. "Declaring, indeed!" and so on She wouldn't listen - it was her big chance to protest against eating chicken feet, and other things she found weird in general. I did eventually get a few pretty simple things to run in VB. But I always preferred my dim sum at the restaurant with people who know what it really is, and like it! : )
@@teach-learn4078 That's hilarious! I'd definitely think of the dish before anything else if I saw that phrase. That's something that I've always wanted to try.
So I'm a freshman in college and I enjoy coding but I definitely don't practice every day. I'm in an intro to coding Haskell class. I do the homework and whatever but those run out quickly. Are there resources for beginners like me to practice basic problems or what are some other things I could do day to day to practice?
Boomer Kingsley if you're doing an intro to Haskell I would look into some intro algorithms. Haskell is a very functional language and that will be the majority of your problems.
I don't understand where these 10,000 hours to become a master come from and how you even try to measure it. It really depends on which skill you want to learn and how fine-grained you define it. So e.g. 10,000 hours to become a master in programming, what does it mean? If you put 10,000 hours into one field like web development, is this already enough? Or does it mean you need to know about many different fields like game development, embedded systems, audio engineering? And if you learn a language, you will probably as an English native speaker not require as much time mastering French as you need for mastering Chinese.
i got really excited about learning to code and told my sister in law/ roommate about it. (keep in mind i’ve been working my ass off day and night trying to learn while she’s been sitting on her ass, jobless and refusing to even clean around my house) and she told me that only bimbos looking to impress men in IT get into programming. it was so discouraging:/ luckily i have my husband to encourage me and give me feedback.
and it sucks when my school only gives me four weeks to digest C grammar and already expects me to do breadth search in the 7th week. it's killing me ...
I love coding and I'm about to start a coding bootcamp. Been learning HTML, CSS and focusing on Javascript and ReactJS on my own time. HOWEVER, I have a hard time even implementing the simplest algorithms, for example: drawing a pyramid in Javascript. I now question if I can even be in this field?!?!? I've been hearing all these people grinding challenges on leetcode when I can't the easy ones. I didn't have a computer science degree; I had a useless economics bachelor's degree and want to career change. My question is: is it possible to be weak in solving algorithms but still be a great full-stack developer?
I'm a teacher and I've taken some time off to teach myself programming ( in thailand its super cheap to live here). So let me give you some reassurance. what you describe is natural...also I think teachers regardless of subject try to get students to do things to fast. There is a difference between input (learning) and output ( applying). Output is not learning...but its what we all want to do! Input is reading and listening, out put is writing and well talking.. If you have to constantly look things up to know how to do them...that's great! do that for 1-2 month and it will eventually sink in as the key to learning is repetition. Think of learning a language like french or chinese imagine how many times you have to hear a word how many times you have to hear some one speak it in a sentence so you get the syntax right? Programming is no different. focus on input, input input and repetition. try code combat.com for that. Don't worry about solving problems right now. you don't have enough information for that. You havnt seen enough examples, you've only learned the alphabet or sentences...its to soon to write a story.....but you can look at others peoples stories, (im told the best programers often do this anyways) , even use some of their lines and with time you will just get it because that is what the brain does..
Yea for sure man. Don’t sweat it if your having a tough time with algorithms at first, that shits hard. And it’s definitely different from what you’ll be doing day to day as a developer. However you should definitely practice algorithms as well until you feel like you have a good handle on thinking logically and breaking down large problems into smaller parts it will definitely help you in the long run. But overall focus on being able to actually create Websites and servers and making real projects
Great video mate, the points around Seinfield's Xs, being able to teach someone, outside influence, making time (urgency vs option) really resonated with me. I'll come and join you guys on discord some time :P A quick q, how much greater value would you say there is in doing a Bootcamp, like Lambda School, vs attempting to self-learn everything in the beginning?
Boot camp 3 months, your in your out. Welcome to a sea over other devs. 10-20k. Lambda 7.5months. no cost until job then probably 20k, also it has lambda next which is an entire 8-5 program like a boot camp but for getting a job. self taught no costs, not timeline.
If somebody finds it difficult to find the time - or get the motivation to find the time then that person is NOT for that profession. You have to be nuts to be in that profession -- if you are a regular guy then it is not for you -- do accounting or something else.
Software development is crap as soon as you get started working on the job, you should only do it if you really willing to put up with alot of bs. So unless your really passionate about quality and realize that people lives depend on your code you should quit early. There's always mis stuff or web stuff, there's no shame in that and hard work.. and be prepared to ruin your life. If your still willing to go through that, then you'll be fine. But it's getting more automated. Don't believe every post and talk to older developers, they have the real knowledge. That's where the gold is.all nighters are for losers. To succeed one way is not to fail intentionally. Now remember that , forget all that I said and get to work.
@@roytating4915 No it isn't. Many, many people are under the impression if you simply throw time at something and grind it you'll get better regardless, that's not necessarily the truth. There is good and bad practice, you can entrench yourself in inefficient ways that require more practice time to undo than it took to develop.
My biggest problem Joshie, I look at a tutorial on UA-cam n when i try it out I wanna customise it n do some way different. People say being adventurous in coding is good but i feel like it sets u up for failure if u dont know what u doing(how the actually syntax works)
How come some are highly creative in coding and some just need a spread sheet to code? I found that most coders can't really make things in their heads.
My biggest problem is that there is so much to learn and I feel like if I don't know everything I can't work with it. Now I'm focused more in the .NET stack and working a lot with ASP.NET Core and MSSQL and I enjoy writing backend code more than frontend. But I want to know CSS more, I tend to fall back on bootstrap a lot on my own projects. But then you want to know React as well, so then you do some React apps for a while.. guess it will come naturally after school when I start working. Also when I have a school project I feel way more motivated, because I know the demands for the task and I have a deadline and want to push for the highest degree. When I sit in my spare time I can't think of anything to do so I just feel demotivated.
10,000 hours to become a master at something hmm? I guess that makes me a master at watching videos!
Apparently I'm a master at world of warcraft
There is actually a pretty good ted talk about the 10,000 hr assertion about learning a skill. It does not take that long but as in everything it just takes time. Faster for some slower for others. Side note: BFA is in three days!!!
Giselle Rabe, yeah I think I saw that one a while back, it was pretty good.
Joshua Fluke that makes two of us
let hi = getElementById("hallo" ). innerHtml = "Change this";
If you're tired take rest as much as u want but don't you dare quit
i am tired as fuck i still can't understand for loops and return function in python pls someone help meee!!!
Kaczynski loops are those functions which runs as many times as the condition is true (I m JS coder not Python but concept is similar). Like for(X=0,X
@@NoOne-om9bb wait a second it prints the 1 2 3 4 but they are also not greater than 5 ?
Kaczynski and return functions are those functions that do stuffs in the function block (like in curly braces in function(){}) and when they are done they give u a value,like "return X" it gives U X...
If u combine both examples:
Function looping(){
Variable X =0;
for(I=0,I
@@NoOne-om9bb but i understood the concept it adds 1 at every part
0:00-Intro
2:50-Building momentum
3:47-Diversify your learning
5:16-Projects and your portfolio
5:48-Find a Mentor/Community
6:39-Outside Influence
8:30-Closing
Good warning about outside influences! When I first started coding, I was so excited. I had a plan all figured out about what I would do and how I would get my first coding job. I had a schedule for my learning, I had a list of projects I wanted to do for my portfolio. My older brother is in IT but not a coder, but I was excited so I told him all about my plans. He literally laughed in my face. His exact words were "Sorry Honey, that's not going to happen. No one's ever going to hire you." I spent the next month panicking because I had already quit my job at a library to work on learning coding to change my career. After talking to some people that are actually working in the field I feel a lot better about my plans. But for a while I was seriously thinking about quitting coding and just getting a minimum wage job shlelpping boxes at a local warehouse. I'm glad I didn't do anything I would regret for the rest of my life.
If you are still calling it "coding" you truly have no idea what is involved.
@@johnnastrom9400 Give them a break, they're just starting.
Same 😭
@@johnnastrom9400 what do you call it
@@johnnastrom9400 I learned programming in Python since the age of 13, scored an A on a college course in Python when I was 14, and today can program any application or website and another 10+ languages, yet I mostly call it "coding" because the word "programming" is to long to spell or pronounce.
The only different between the terms "coding", "programming" and "developing" is that coding refers to the actual typing in the keyboard to produce sourcecode, programming is creating an algorithm and integrate it into a bigger system, like you program a robot. Development is when you build or contribute to build the whole system from scratch. - development of a website, development of a platform.
9000 more hours of programming to go
9999.5 hours ⌛to go.
20 year game dev vet here. I just spent 7 hours debugging a hobby car sim I'm working on. Tires wouldn't collide with one of the track triangles. Turned out I had a + sign instead of a - sign in an equation. So yeah, that happens a lot.
Or } halfway through C code, making it loop back to the start. 10 hours' worth of futzing...
That sounds awesome! How is it going now?
@@southernkatrina8161 brace order has messed me up in the past, but my fav is when someone copies into defs.h: #define TRUE 0
#define FALSE 1
Also } , and ;
The 10000 hours thing was popularized by Malcolm Gladwell, but he did not mean for it to become the ironclad principle it is today. Take it with caution.
Facts
@@JoshuaFluke1 totes
@MrTron But it's nebulous - there's breadth vs depth. What exactly would you work on for 10,000 hours? HTML and nothing else? Javascript? Bootstrap? Or a bundle of ten or fifteen languages / frameworks / processes?
@@jkovert building projects apps
But i still, practicing so much will make soo good, in 2-5 years you can earn good $$
@@will-wowdk1930 Of course, I grind. I GRIND.
Using a calendar as modivation to not break the streak is actually amazing! I'm going to definitely use this
I approach this by trying to have something in my notebook accomplished each day. No page goes blank.
Michael Did you try the Seinfeld method? And how has that worked for you these past 4 months?
i've quit smoking this way ^^
Even better make your own raspberry pi calendar and put it on your portfolio
thats honestly one of the main reasons i chose github
Dude I love your videos, you're so genuine and you're really trying to help people, not like some channels where they make videos just to make a video on youtube to get views!
I think 1337 hours is perfect for any skill, but when I want be OP in a skill, over 9000 is where it's at.
Dragonball is leet.
One thing...
Don't tell yourself "I NEED to get this done."
Say "I WANT to get this done."
Don't say, just do.
Dont do just make it happen
Or really want something or do something you really want
dont think, just do
Like is AN INSTINCT
Don't do. Just give up.
first time coding i made my first project an encoder. pretty simple. making the decoder did take a few weeks though, even though i were discuraged by those around me, i still finished it because i felt like it was something i wanted to do. and damn it felt good when i finished it. i had no real knowlege of what i was doing when i started at all, but it works, and i created it on my own.
I salute you. Congrats.
I was only supposed to make the zumo go in a square, but I made it spin, backtrack, go fwd and back, charge at the spectators, and then twirl at the end. The last lot of acrobatics took one hour to program. The square took, on and off, a year....
thats the spirit
Practise whatever skill you are learning. A small project incorporating each, or most, of those concepts can be a motivator. When you are learning the new skill or concept, write a few trivial programs before incorporating the skill / knowledge into the small project previously mentioned. Accept the reality that you will spend 90% of your time debugging and 10% of your time moving forward with the project.
Good video! I felt very related with 2 things
1 ideas that snowball, think a small bad thing and you dont do it eventually, think positively and youll go do it eventually.
2 also some time ago i learned the "start with something small" thing. I would always procrastinate but i learned that if i only write one line of code the rest comes out of your fingers so easally instaed of thinking oh i need to program this 1000 line thing now.
Its all about the mindset
Good stuff man. One month into my bootcamp and getting all the reality checks. Along with practicing all the time having the right mindset is key.
yea my mother has critiqued every venture outside her knowledge set that I have wanted to pursue. it had taken me years to realize this contributed to me losing interest in things.
Here is my "stab" at why people quit learning (to code, or anything ). People have this idea that you must be a gifted / high IQ person to learn to code, because its a "computer nerd" thing to do. As for me, I spent about 2 years learning to code in my spare time, just practicing from tutorials and trying things on my own. I would learn one thing, then another and so on until I got motivated enough to go into programming full time. If you went to college, you would spend 4 years working on a CS degree, another 6 months or so doing an internship to land a junior position. So really, if you are going the self taugh route, spending 4 years, to get the hang of it is not bad, that just the learning curve.
but after a certain age you are to old to start coding
@@cautarepvp2079 nothing called too old, it's just a word you put in your mind, the oldest student that learn C# programming to me is 75 years old, he learn it so he can motivated his grand child to be a game programmer instead of just playing game, in the end he can make some cool simple game by himself and show it to his grand child
@@cautarepvp2079 that's true. One of my uncles asked me if he's too old to code, but the fact is you're never too old to code. Don't care about what other people think.
@@anonofDeath the problem is not if you are to old to code, but if you are good and marketable enough to make a living out of it and in good circumstances lots of money
@@cautarepvp2079 you see, this is the problem. You code for the sole purpose of money and not exploration and the engineering process. Of course, money is attractive but it should be a by-product of why you want to code, not the goal of it.
Also don't go into self pity when you failed and do nothing. Never say sorry, just don't do it again! Your actions will lead to results.
In my experience do not talk about your visions because people will mostly just down you for it and it discourages you. Most people has little to no vision for their life. Do not let them drag you down. Just have your vision and fucking surprise them.
It’s great to see this video and the way people have replied. I thought I was alone in this. It’s time to roll up my sleeves and get to work!
10,000 hours = A scare tactic to prevent people from starting a new hobby or skill. An excuse as to why they are not good at something.
100 hours = will make you better at something than 99% of people. As 99% of people are unlikely to be learning what you are.
1000 hours = To get as good as you can at something and reach your ceiling.
...I hope this helps.
They just want to leave some leeway to blame yourself, in case you are not successful, or should they decide to sabotage your life?
No, Jacob. That's definitely not true for a job. Spending 100 hours at a job (which you will do within three weeks) does not make you a master at whatever job you just started. Far from it. How could you make this assertion? The 10,000-hour number comes from Malcom Gladwell's "Outliers" book, wherein he wrote about an elite group of individuals who had achieved excellence in a certain field that made them stand far above the average. Those individuals had usually put in at least 10,000 hours of practice into their craft.
I agree that 100hr will make you better at something than 99% of the people, but that is still basically just entry level. When I went to do my AWS Associate Cert, I started from zero AWS knowledge, and it took me approx 300hr of studying to feel confident enough to attempt the test (I passed it, but it was not easy. I thought I failed originally). And ironically, AWS Associate Cert is still basically just an entry level Cert, useful for showing you understand the basic concepts, but don't ask me to work on your Lamda functions or clean up your IAM roles, 'cause I'll have to hit the books again to refresh my memory.
Damn josh your so right I haven’t studied coding for the past 6 days. Your right studying a little bit everyday is better than doing nothing at all. From this day on even if it’s for 15 minutes I’m going to do something everyday. I was supposed to see this video. Thank you!!!!
How are you supposed to retain information from all of these languages?
Out of all of the videos I've watched on learning / taking up coding, this was the simplest and most resourceful. Thank you :)
Man this was the video I needed right now. Lots of stuff spoke to me as I am learning and about to start a bootcamp. Thanks man.
Chasing Brews hope your bootcamp went well
I spent a month learning code and made a game but it was slightly buggy and I figured out having a simple leaderboard or anything multiplayer plus getting rid of bugs was so much more work that it was really something I had to be ready to commit my working life to. So I was smart enough to not try to solo develop my dream game but I still underestimated just how much extra effort there is between making something that kind of works versus making something that is a consumer product. How many people want to play simple games these days that do not have leaderboards or multiplayer? Not many.
Just find the right libraries
I hate the 10000 hours.
It's 10.000 hours to "MASTER" something. To become the Steve Vai (or some other virtuoso) of the thing you learn.
You only need 20 hours to be able to play. And then you play around to your hearts content.
And through play you learn.
And then you can use what you've learnt to build something epic.
Though i'm learning code for fun so the motivation might be different.
I'm pushing myself through a game project. Just working on issues one at a time and learning everything I need to know.
Even putting in half-assed effort pays off over time. Do something! Try! Fail! Keep at it! Every little thing you do in pursuit of your endeavor brings you incrementally closer to achieving some mastery at some thing.
I am feeling lucky that I subscribed to your channel. All your videos are so motivating.
That skill circle was dope lol
So random lol
That's what I do best
The eldest part of waking uuuuuuppppp is motivation in your cuuuup
I keep running into issues with loops, so i have been using different books/sites to try to better visualize how they work. Also working on the basics over and over again until I truly understand. I really want to do stuff that is applicable to my work, but I know I have to master the basics first before getting to that point, no matter how annoying it is.
The eldest part of waking uuuuuuppppp is motivation in your cuuuup
Back in the day before OOP and GUIs became popular coding was easy, You'd learn one language and you'd learnt the rest . Now coding seems to have become an insidious endeavor in objectting and addressing code even though alot of code may only be for its sole purpose. What ever happened to keep it simple I don't know, ? We got red onions overriding green onions and I don't know where the spring onions fit in LOL.
Thank you for making this video, it really helps. Keep it up!
@1:50 Arnold Swarchenegger also had this mind set. In his book he talks about days he didn't want to go gym ofcourse he would rather run around in sun with some hotties. But he said he just forced himself to go and the motivation comes while he was there.
Thank you Joshua for the info that you provide.
Thanks, Joshua! I needed the encouragement.
very well thought out video, sir. thank you. this is very helpful to me.
I hate talking about my passion very few will encourage they be like "Why don't you wanna talk about it? weird" *talks about it "Lol just let it go" *instantly feeling down ... Don't even mention it, just go for it in the shadow.
1:00 exactly nobody sees the backend and the effort a individual puts in that made him big all people see is that one or two moment where you achived the goal
The 10,000 hours rule is more of a guideline than a rule. The truth is that some of us master skills in far less time while some require more.
I'm a programmer and I fall into that trap. I feel like I need to learn a thing in a couple hours. I blasted through data science and could barely get the concept of neural networks. Then sat down to code and drew a blank on the first step.
Yup! I mark my calendar everyday, just to see my progress. Try 25 min increments, before you know it, you've been coding for an hour or 2...
6:54 I feel you're energy here, everything you say is scary relatable.
you look better and fresher and chiller when your hair is short, but everything you say is what discouraged people like me to go on and try again, thank you Joshua
Have a good day.
You too dude!
That was a good one... keep going mate.. good luck
Never thought about learning code in my life. Avoided higher education like the plague, hated math, problem solving etc. That about disqualifies me from learning code
How I got good at programming:
- brush teeth and thing of what coding stuff to do for the day
- eat breakfast while watching coding videos
- get paid hourly while programming (uni student, I got an on campus programming job)
- teach a student code on Saturdays
- assume I know everything and dive into a project I find interesting (game dev, app dev, etc.)
- read stackoverflow
- watch anime to destress
- avoid social interactions unless the interaction involves programming
I realy enjoyed your opinion on this topic. Thanks for the clear statement.
your videos are so motivating. Thak you!
Do you know what ? I have no idea of how many hours I needed to become an expert.
My first coding was in 1981 and so I have quite a bit experience -- I still find much to learn about in Programming.
RICK AND MORTY!!!!!
Programming is not for everybody. It can be tedious and frustrating.
Best way to learn coding:
- pick a project that revolves around something you like. Example: you want to learn about databases and also love cooking? Make a small cookbook application
- set a time limit - per day and time spent in total for the whole project
- be persistent - no excuses (except life-altering injury, death or zombie apocalypse)
- be on point - it's easy to get distracted once you start doing research
This is a general rule and applies to everything new you think it might be useful to you in the future.
Beginning your studies with the JAVA certification exam prep class, and getting a non-verbal teacher, who ocassionally uses proper nouns, but mostly indefinite nouns, the one who refused to answer any of your questions after the first week of class? Just re-read the beginner, intermediate, and certification text books three times, and begin coding after that? Find a teacher who will use the correct jargon consistently to describe the concepts and code, or you do it?
Love the videos!
thanks, I found it great useful tips
Civil engineers!! Represent!
If you're Tired , Learn To Rest And Not To Quit -
_ Bansky
Very Motivate, thank you.
This seems to be more about 1. why learning to code is good. 2. how to learn
Maybe I missed the part about 'why people fail'?
Funnily I had an idea today about why I have failed in my several attempts to learn to code. (When I first tried I was 38 btw.) My reason: I imagined a finished thing that was kinda complicated, and very often was kinda creative, and got bogged down, so that was discouraging.
Another reason, in the books and videos typically there is a complete lack of big picture view, it just launches into 'do this, then do this, then do this.' This is fine for a lot of people, many smart people are "abstract sequential" in their processing style. But more divergent thinking typically are "abstract random" in processing style, so we in the latter category have a hard time processing isolated strings, without a view of where that bit fits into the bigger picture.
For example, I would have loved to start with a relatively large amount of code, let's say 100 lines, and have someone point out the functions and what they're doing, and gradually get down to the expression level. Which everyone "knows" would be the "wrong" way to approach it.
All of your comment resonates with me, especially the "do this, then do this" thing. It is my least favorite style of teaching to follow. I stopped with video tutorials and used college textbooks (combined the courses with the college's bookstore/book list, then got the book however it was most accessible to me) because being told what to do without knowing why or what exactly I'm doing never sat well with me. The textbooks usually explain what something does/what situation you would use the new concept in, then give you an exercise to do that would use it after explaining, and they're usually not exact copies/parallels of the examples that they taught with. I have to actively think in order to make my code work instead of just listening to someone tell me what to do, I do it just as they said, then I encounter a problem and have little way of figuring out where my understanding fell short.
The standard way to be taught, which just feels like I'm being presented with unconnected concepts at random, makes me lose interest in a subject. Thinking about this now reminds me of when students would ask why they have to learn math, then get surprised and struggle with word problems, especially ones that present the problem as a practical situation to figure out. I always felt the same way about history, but I learned eventually that tracking the actions of a person and the events of an area can help me understand a culture and be more informed when selecting a leader/understanding a new problem. The way a subject is presented by some teachers can make it seem like it doesn't have anything to do with anything.
I say all of this to say that I love college-chosen textbooks because I have to actively learn the how and why of concepts in order to get through them. I'm still trying to figure out if I'd be okay with paying thousands to teach myself and just have certified proof that I could pass the tests about it when I've been able to access this information for free or close to it on my own, but that's not the topic. Right now, I'm working through "The ANSI C Programming Language" and Javascript's official guide. ANSI C in particular takes the approach that you mention at the end, presenting the reader with code and explaining what's happening, line by line. Maybe those types of things would fit you better than someone else's lesson plan.
@@typhlosionisbest Haha, your response brings back a memory. I was in a university program where there was a required course in Visual Basic. I had bought a textbook and was trying to do as you are describing. One day I was at my mother's with the book. She was English. In VB there's a command "dim sum," which I think had to do with declaring variables. My mother and I had been to a Chinese restaurant for dim sum, which as you may know is a very un-English brunch of chicken feet, squid, tofu and other exotic foodstuffs ordered from petite women pushing carts from table to table, which my mom hated. One day for some reason she looks at the programming book in which the first chapter has this phrase "dim sum," and that just sets her off. She was a little "eccentric" in some ways. For several minutes she's like, why is this book talking about dim sum? That's so stupid, what does dim sum have to do with computers? blah blah blah. I'm sure she was imagining slimy things with unusual flavours and languages she doesn't understand. She went on a rant against dim sum! It seems to activate some conversational loop in her mind. I'm like, mom, it's just an abbreviation, it's nothing to do with squid and chicken feet, really, it's a programming thing, it's for declaring variables. She's like, why would you need to declare anything, that's stupid. "Declaring, indeed!" and so on She wouldn't listen - it was her big chance to protest against eating chicken feet, and other things she found weird in general.
I did eventually get a few pretty simple things to run in VB. But I always preferred my dim sum at the restaurant with people who know what it really is, and like it!
: )
@@teach-learn4078 That's hilarious! I'd definitely think of the dish before anything else if I saw that phrase. That's something that I've always wanted to try.
So I'm a freshman in college and I enjoy coding but I definitely don't practice every day. I'm in an intro to coding Haskell class. I do the homework and whatever but those run out quickly. Are there resources for beginners like me to practice basic problems or what are some other things I could do day to day to practice?
Boomer Kingsley if you're doing an intro to Haskell I would look into some intro algorithms. Haskell is a very functional language and that will be the majority of your problems.
Is that really the name of the book? Intro to Coding? Coding usually just means typing in the code, but not doing any design/development.
Thanks. I needed this!
I don't understand where these 10,000 hours to become a master come from and how you even try to measure it. It really depends on which skill you want to learn and how fine-grained you define it.
So e.g. 10,000 hours to become a master in programming, what does it mean? If you put 10,000 hours into one field like web development, is this already enough? Or does it mean you need to know about many different fields like game development, embedded systems, audio engineering?
And if you learn a language, you will probably as an English native speaker not require as much time mastering French as you need for mastering Chinese.
i got really excited about learning to code and told my sister in law/ roommate about it. (keep in mind i’ve been working my ass off day and night trying to learn while she’s been sitting on her ass, jobless and refusing to even clean around my house) and she told me that only bimbos looking to impress men in IT get into programming. it was so discouraging:/ luckily i have my husband to encourage me and give me feedback.
I am an absolute beginner in coding. Idk where to start.
and it sucks when my school only gives me four weeks to digest C grammar and already expects me to do breadth search in the 7th week. it's killing me ...
Fuckin hell it's hard enough to learn one language not to mention 2 AT THE SAME TIME!
Great video. Perfect!!!
some very valid points.
This was an interesting video I was just gonna quite learning python lol pathetic I know but I shall persist
What you think about writing the pseudocode and then googling the syntax as you go????
I love coding and I'm about to start a coding bootcamp. Been learning HTML, CSS and focusing on Javascript and ReactJS on my own time.
HOWEVER, I have a hard time even implementing the simplest algorithms, for example: drawing a pyramid in Javascript.
I now question if I can even be in this field?!?!? I've been hearing all these people grinding challenges on leetcode when I can't the easy ones.
I didn't have a computer science degree; I had a useless economics bachelor's degree and want to career change. My question is: is it possible to be weak in solving algorithms but still be a great full-stack developer?
I'm a teacher and I've taken some time off to teach myself programming ( in thailand its super cheap to live here). So let me give you some reassurance. what you describe is natural...also I think teachers regardless of subject try to get students to do things to fast. There is a difference between input (learning) and output ( applying). Output is not learning...but its what we all want to do! Input is reading and listening, out put is writing and well talking.. If you have to constantly look things up to know how to do them...that's great! do that for 1-2 month and it will eventually sink in as the key to learning is repetition. Think of learning a language like french or chinese imagine how many times you have to hear a word how many times you have to hear some one speak it in a sentence so you get the syntax right? Programming is no different. focus on input, input input and repetition. try code combat.com for that. Don't worry about solving problems right now. you don't have enough information for that. You havnt seen enough examples, you've only learned the alphabet or sentences...its to soon to write a story.....but you can look at others peoples stories, (im told the best programers often do this anyways) , even use some of their lines and with time you will just get it because that is what the brain does..
Yea for sure man. Don’t sweat it if your having a tough time with algorithms at first, that shits hard. And it’s definitely different from what you’ll be doing day to day as a developer. However you should definitely practice algorithms as well until you feel like you have a good handle on thinking logically and breaking down large problems into smaller parts it will definitely help you in the long run. But overall focus on being able to actually create Websites and servers and making real projects
Gpav
Great video mate, the points around Seinfield's Xs, being able to teach someone, outside influence, making time (urgency vs option) really resonated with me.
I'll come and join you guys on discord some time :P
A quick q, how much greater value would you say there is in doing a Bootcamp, like Lambda School, vs attempting to self-learn everything in the beginning?
Boot camp 3 months, your in your out. Welcome to a sea over other devs. 10-20k. Lambda 7.5months. no cost until job then probably 20k, also it has lambda next which is an entire 8-5 program like a boot camp but for getting a job. self taught no costs, not timeline.
If somebody finds it difficult to find the time - or get the motivation to find the time then that person is NOT for that profession.
You have to be nuts to be in that profession -- if you are a regular guy then it is not for you -- do accounting or something else.
💯👍
Big goals get achieved by the achievement of a thousand much smaller ones.
Where do u find projects to reverse engineer?
Pretty much any public project on github: github.com/explore.
This needs more views.. 👍
Software development is crap as soon as you get started working on the job, you should only do it if you really willing to put up with alot of bs. So unless your really passionate about quality and realize that people lives depend on your code you should quit early. There's always mis stuff or web stuff, there's no shame in that and hard work.. and be prepared to ruin your life. If your still willing to go through that, then you'll be fine. But it's getting more automated. Don't believe every post and talk to older developers, they have the real knowledge. That's where the gold is.all nighters are for losers. To succeed one way is not to fail intentionally. Now remember that , forget all that I said and get to work.
I agree. If you can't even motivate yourself to learn coding you will hate your job.
5:19 Thanks for this...
Practice doesn't make perfect- perfect practice makes perfect.
Peak.
Isn't it already implied in that saying? Do we really have to specify things these days?
@@roytating4915 No it isn't. Many, many people are under the impression if you simply throw time at something and grind it you'll get better regardless, that's not necessarily the truth. There is good and bad practice, you can entrench yourself in inefficient ways that require more practice time to undo than it took to develop.
100 hours to make a zumo robot turn in a square. Oh dear.
I switched from a developer job to a qa job
My biggest problem Joshie, I look at a tutorial on UA-cam n when i try it out I wanna customise it n do some way different. People say being adventurous in coding is good but i feel like it sets u up for failure if u dont know what u doing(how the actually syntax works)
Your way is the best way
@@JoshuaFluke1 thanks bro
10k hours?! I have been doing coding from past 2 years, still failed at coding interview of google 😶
Wow... What was the question still a beginner
Is it possible to learn multiple languages at the same time?
That Rick and Morty though.
You're a lefty! Explains everything.😃
It's not coding that I fail in, it's hacking. I wanted to learn how to hack in games, but I often fail. It just doesn't work
How come some are highly creative in coding and some just need a spread sheet to code? I found that most coders can't really make things in their heads.
Is reverse engineering really efficient? At what stage is it recommended?
My biggest problem is that there is so much to learn and I feel like if I don't know everything I can't work with it. Now I'm focused more in the .NET stack and working a lot with ASP.NET Core and MSSQL and I enjoy writing backend code more than frontend.
But I want to know CSS more, I tend to fall back on bootstrap a lot on my own projects. But then you want to know React as well, so then you do some React apps for a while.. guess it will come naturally after school when I start working.
Also when I have a school project I feel way more motivated, because I know the demands for the task and I have a deadline and want to push for the highest degree.
When I sit in my spare time I can't think of anything to do so I just feel demotivated.
Nice video 👌👌
This is exactly what I have been dealing with. Subscribed.
10,000 hours? Huh. I must be a master bater
The 10,000 hour thing is actually a myth. But generally the more you practice the better you get.
Thanks for sharing your thoughts. Learnt something new.
9:32 Well, TrenBlack recently uploaded a video about him programming his first videogame, a lol clone, and it came up reeal good lol
What a beast imo
* Research has shown. Yeah right, can you please cite the study? Last time I checked the 21 day thing was debunked as myth.
Nope. I can't. Because you're right and this is an ancient video and I'm dumb.
@@JoshuaFluke1 We've all been there mate ;)
10000 hours. Which is around 3-4 years of learning a skill for doing it 6 hours everyday. Wow.