- learn from the fundamentals - build real project - use resource that have good reputation - stay consistent - focus on one thing at a time - if you are stuck on a problem for a long time, just do something else, refresh your mind and come back
this is like legit the complete opposite of what i have done, somehow works wonders for me lol - multi tasking 10 languages at once - work 6 hours every other 5 days - never finish any project
Give yourself time to learn things thoroughly - Don't burn yourself out by doing projects as quickly as possibly to get the job. Also practice EVERY DAY is a great tip!
@@Carramoz You would burn out. If you don't take enough time to grasp the concepts before a job, then on the job you'd need to put on more hours after work to learn and catch up. So you'd be spending your nights and weekends doing that. 14 hours or more a day just to catch up would burn you out quickly. It happened to someone I know. Burn out can be really tough to deal with once it happens. You'd have to stop from all of that and either take a break or never get back to it.
Notes for self and for others 1. Learn the *Basics First* and don't just dive into advanced just to look cool. 2. *Google Stuff* that you don't understand, don't just skim over. 3. Learn from *Standard Material* and not from random, unrated/less rated material. 4. *One thing at a time* . (For myself- Focus on Java DSA. Leave JS for some free weekend, Addon for another, CPP for 3rd sem and C# for 3rd sem weekends. Don't pick any new things, you've already many things to do. For Drawing, make time.) 5. *Code Consistently* . 1 hr for 6 days is better than 6hr in weekend. (Because Memory curve) 6. Take your time. *Relax when exhausted, take a walk then restart* . 🙂
@@atifshaik No 🥲😔 1. I dived into advance topics just to look cool. 2. I didn't googled and cleared my doubts. 3. Didn't read Standard material 4. Tried many things at a time(Java DSA, C DSA, Cpp OOP, Android, Cyber security, web, and what not. But continued none🥲). 5. No consistently, I came back to write this reply with a coding break of about 3 months. 6. Initially I didn't relax and exhausted myself almost at a regular basis. Hope that I fix atleast some of the things.
Good stuff. Coding daily is soooo important. So many things to remember when programming so muscle memory is so important. Even if it's just 20 minutes a day. Code daily! Great as always Nick
1.) Learn fundamentals/basics: Do you actually know the pre-requisites? Are you getting ahead of yourself? 1:37 2.) Google what you don't understand: Including single words. Comprehend thoroughly to retain information 3:07 3.) WRITE CODE: Build a project sooner than later, otherwise you are wasting time 4:07 4.) Reputable resources 5:08 5.) Stay consistent: Practice every day. Muscle memory 5:36 6.) One thing at a time: One project at a time etc. 6:12 7.) Re-fresh your mind: Relax your mind when you find yourself in a block 7:02
As someone who entered college with below highschool grade math, it is rough to pick things up. But having a solid foundation makes everything easier down the road. Dont skip!
@@russtoo just focus on logic, math in programming is not a big deal, the problem is that in college they teach a bunch or useless stuff and that includes complicated math problems with no actual use outside of academic environment
Thanks for the advice! It's true, when you first start learning it can be very overwhelming and the thoughts "am I focusing on the right thing?" and "what should I learn next?" are a daily occurrence! I'm still in my learning stage, been teaching myself for 3 months now and still going. I have to say, doing it every single day has been a game-changer. Looking forward to more content!
The video starts at 1:31. You better choose 1.25x speed (so you won't waste your time) 1:37 learn the fundamentals, don't skip the prerequisites 3:03 google every unknown word, don't skim 4:08 build real-world projects 5:05 use only reputable resource 5:32 be consistent 6:12 focus on one thing at a time 6:57 if you're stuck, close your laptop and relax
my best advice: while covid is still going on, screw going out with friends and partying. you got discord for messaging IF needed. sit in your room, defog the brain, get a white board or paper and start getting that brain running with practicing algorithm basics, learning to talk to your brain about what you are learning, software engineering basics by finding a framework and find applications for your basic algorithms. master 1 language, build a project, refine it and stay consistent.
@@bobanmilisavljevic7857 some people forgot about the importance of communication skills, networking, and balance healthy life. What's the point of sitting in front of the computer for 5-6 hours long where half of the time spent procastinating because your brain can't focus on anything for too long. They can tell themself that they're hardcore learners and those who use their time for social activities are lazy, wasting people. However, in the end, they can still seat on their basement all day long wondering why they've tried so much but still not get the jobs while those "lazy" people keep getting more and more offers by having friends refer them when applying.
@@bobanmilisavljevic7857 I used to be skeptical about improving social life, friend circle, etc until I got an internship which at the beginning I passed the screening round thanks to one of my friends referring me. It's true that learning new things contributes greatly to your career, but the importance of networking cannot be demeaned
Cool bro but how to do that with backend language like Java? How to "start" building if you need learn almost all the language first? Front end languages it's a bit simple i think, you write 2 lines of code and run live server and you see whats going on the screen.
@@huutriet2045 Even when I have brain fog and know I won't learn anything I put in 2 hours minimum. It is more about maintaining the habit than about learning because I know in the long run not breaking the habit leads to more learning.
i Love you , because you just spoke the truth, and your bodylanguage is telling that you are a professional.... instead of super hyping people , you are very relaxed, and you communicated the message very well... thank you
i've been trying to learn new tech and have been constantly stressing myself why am i unable to get concepts as easily as i thought i could, burning myself out and not touching it again for a couple of days. this video couldn't have come at a better time. thanks, love your content man
Data in and data out. Write concepts down on paper like your logic and how you think the data should be transformed then use the tools in your language to help shape that.
This video has actually opened my mind. I have a final year project that i am currently working on and just realized that i skipped the basics of the technology and framework that i am using and just jumped into doing the project. thanks man.
What I've found extremely helpful is going back to my completed programs and rewriting them with the new knowledge I've gained. Making them cleaner, more efficient, using better and more complex concepts and methods within the language.
I find learning best by trying to have a problem that needs solving, or thing that needs doing. Then you burrow down in to it and learn so many new things.
I'm grateful that you did this. I'm a total beginner and I've been learning to code for about a week now, and your advice on coding every day, not sparing fundamentals and learning one thing at a time is just gold for me. I never rush until I actually fully understand each new concept. Thanks a lot ❤
it's hard to get a guy to talk pure truth. He's taking the words right out of my mouth. Especially the part with reading it and understanding the words instead of just skimming over it (which i always do). When you actually break it all down by googling the jargon its starts to get easier.
I think the advice of just taking a break when you are genuinely stuck is great. There were times in my algorithms class when I would literally look at my computer for 5+ hours straight with no progress. In that time I could have worked out or done really anything. Sometimes all you need is a fresh mind to get the task at hand done instead of brute forcing it.
This video is for me... I am trying to save time. Sometimes is so frustrating: I study things, take tons and tons of notes (in Italian, 'cause English is not my first language), even do exercises... After I don't use them, then... Time passes I forgot all and I have to re-study again. Thanks for the tips... There are errors I've heard that I actually do.
I can confirm on the skateboard analogy. I got an e-skateboard and went 3-5 mph on the first week. In my mind, something was telling me to hurry up and go faster. I ignored my thoughts and went with the flow. After a month of non stop skating, 30 minutes a day, I was pushing 22mph. Fast forward 2 years later, im pushing 35mph. Just enjoy what you’re doing and don’t force yourself to learn.
I started watching your videos few months ago and i really started to like those.... and it goes like when ever i saw your video, i stop watching other videos and continue to yours's... you deserver more than you have now(subs)
This is the BEST advice I’ve heard on TH-cam for learning how to code! You might be the only person who stresses the prerequisite part of the process, which is so helpful to hear. Thanks!
Agree. One sign of a bad programmer - only wants to get a job. You gotta love the tech, that means you gotta learn the fundamentals. What I don't really agree is that you can't really avoid wasting time. Usually the guy who tells others not to waste time is the one who has wasted lots of time struggling with difficult problems and climbing a steep learning curve...
I have been always confused with concepts, whenever I start following some tutorial I found many vocabs and concepts that makes me confused and I ask myself "Should I open a new tab to google that concept?" because I always think that this is just wasting of time.. But now you confirmed that it was just the opposite, and it was the right thing to do. So thank you so much, sir, you got my subscription with a Like and this comment that I made with love.
Fact of the matter.. learning is not fun until you know what you're doing. I PROMISE that once you understand the fundamentals, coding and building software feels like ART. It becomes FUN. You just need to learn to walk before you run, and you need to learn to crawl before you walk. Don't worry about security, setting up ci/cd pipelines, what dependencies you need, about coming up with a scalable design. Forget CORS, disable all. Forget the front end. just start by building a serviceable API. As you learn more, you'll learn how modular everything is. You can add security over your app later. You can add exception handling later. You can add logging later. You can add swagger later. JUST, MAKE, IT, WORK. If I send a request to your API, I get the data I want back. end of. Add things one by one. Don't move on to another framework until you master the one you're currently using.
sorry i had to rush to film & edit this video in the span of a few hours to do a last minute promo for tech skills day tomorrow 😁 future videos will be higher quality!
Thanks for your video and insights. I'm new to coding and learning Python. I agree with all your points and tips and have known about and used the same ideas in all my endeavors and they always work for me. So, though I didn't come away with anything new from you, it does validate my own thoughts and methodologies. You and I agree on every point. Thanks for the video!
Really good advice, especially for learning one thing at a time. I could find myself 'stuck in motion', not moving into any meaningful direction by taking part on way too many projects I could handle at once and mixing stuff up.. Projects shall have their own timelines to be managed efficiently.
Learn Fundamentals - There are fundamental things you need to know before you jumped in to more advance things. - Question yourself, whether you having some improvements whether you having impatient and you are trying to learn more advance than you should be or maybe take a step back and think do you learn fundamentals. - Make sure you understand all fundamentals. Google what you don't understand - You might see words that you don't understand, if you don't understand something, you should look this things up and learn those. Actually write code - Recommend to build real world projects and it can help you a lot. Make sure you use repeatable resource You should be coding everyday - You really need to practice consistent because in coding you can forget things pretty quickly. Focus on one thing at a time - Focus on one thing and be good at it because it will lead you to success Take a break and do something - If your mind is in not in the right state, take break. - Relax yourself, there's no reason to stress yourself
hi Nick! Thank you so much for these advices especially the first one! coz i personally make this mistake and need to learn to slow things down and give my brain the liberty to process things . and yes i should stop 10hr long coding grind sessions and instead practising coding 2 hr/day. these tips will definitely help me survive and i guess be at better position at the end of this college semester!
I live in a rural area but need to touch and see items for coding, do you get what I'm saying? Give me a tip to start and use real objects for coding, please.
True, I’ve been using c and c++ a lot and recently been getting Python and started on page 1 even though I know the basics because it helps bring back things you’ve forgotten and helps with new syntax too.
Coding is hard! I'm glad you like Austin! Thanks for the videos. Hopefully, down the line we can just download knowledge via neuralink. I really only want to learn programming so I can work on VR/AR google glass. If I had 1 billion dollars I would invest it all in google glass, it's the future. but before all that I need to learn how to encipher/decipher a text...lol.
Keep your eyes open for other projects too! Meta's quest 2 is dominating the VR scene at the moment with market share and incredible price/performance. Also, they're working on AR with project cambria which is unreleased but worth noting as it has potential
The biggest time waster when learning as a beginner: trying to make it perfect. So instead of writing code and making it work you spend days tryin to do it in a "right way". It has to follow the best practice, it has to apply design patterns and most modern approach. And month later instead of having 10k lines of code that do something you have 500 lines that do nothing. Just make it work. And then if you want you can come back and improve things. But you don't have to. You can start new project and make sure you do it better then the last time. Refactoring can improve your knowledge but as a beginner there is a greater value in simply starting more projects. Especially if you don't have university degree, your hobby projects will be your "diploma" when looking for the first job.
kinda disagree here. It's true that before jumping into these concepts, you need to do some projects to get yourself a little bit of experience. But still, if you just blindly rush into projects without acquiring skills such as writing good test, clean code, refactoring, your code would still be rubbish. I'm not saying we have to learn all about testing, refactoring as a beginners because some techniques and scenarios require a long exposure to that matter to really get it. However, you have to learn them along side with doing projects to know which part of your code is unreadable, unmaintainable to get your project improved in the future. Also, you can practice the good practice at the beginning and don't have any bad habits at the long run. Lastly, I don't think coming back and improving your old projects is not necessary. You can see what mistakes you had earlier, practice to improve old ugly code (legacy's code), and from that, you can learn to avoid those bad practices and write cleaner code in the future.
@@huutriet2045 "You can start new project and make sure you do it better then the last time." is key. I guess it also depends on the project the example I would give is that my first kernel project was compiled on gcc with like 20 flags then i did it again "better than last time" using a cross compiler, and other better practices
@@dumbfailurekms did I disagree to that? I mean going back and trying to improve your old projects is not an unnecessary thing since if you can improve them, your've improved yourself.
Dang, you just described me, I quit school in the 9th grade, and I’m struggling hard with college algebra, and I’m also taking the advanced developer course, guess I’m in for it.
I have coded since 1981 and I know less about it now and hate it more now than I did 43 years ago. Fuck programming. I will leave that to those who invest their entire lives into it. I will stick to proving math theorems. It is what I love, what makes me happy.
people, pls dont be mad when I say this, but if you're wasting time to get to learning, you should just stop. I mean it, I applied these step(s) in my life and it really changed me for my better final self. Remember folks, its not about the journey, it's about.
That last one is true. I can't count on both hands how many times I got up from a project I was on because I had no idea what I was doing and wasn't making in progress, so I would get up and leave the computer. When I would return, the entire project seems easier. As if I knew the answer the entire time. Also, there are times when you are taking a break that the solution will come to your head without you sitting at the computer staring at a screen.
Hes right. Google the definition of API. APPLICATION PROGRAMMING INTERFACE. Then google definition of Application, programming and interface. Never assume you understand anything.This method is gold.
My two cents as a newbie, ChatGBT has been great assistance/tool. It’s like having a tutor to answer questions you would pose to a teacher. It’s great for explaining things with detail
I think comparing it to math is the perfect comparison. Whenever i was teaching myself math while getting ready to go back to college. I had to stop.. and humble myself when I literally had to go back and learn 5th grade math concepts i'd forgotten. It is humiliating to be watching a math antics video designed for children, as a full grown adult, but it was necessary because things seemed far more difficult to understand than they should have.
Counterpoint to looking up every word you don't understand: Moderation is key. If you're like me, you might find yourself falling down a wiki rabbit hole, and never finish the original article/etc. If you feel you can approximately understand the concept, great, write down the term, and move on for now.
Unless you are learning programming for the first time ever I disagree with learning the basics before more advanced stuff, that's how you get into tutorial hell and never learn anything useful. If you try to build something complex you will end up dividing the features into small tasks and learn the basics while you are trying to code those tasks. I learned React before javascript, I ended up learning javascript while trying to build something with react. I wanted to learn redux so instead of watching videos of people building todo lists and wasting money on courses I decided to create a spotify clone straight away, only needed the documentation and learned a lot because I was solving problems myself instead of copy pasting code. You can try to understand some advance stuff (one at a time) and while doing so you will search information and learn about the basics and keep that information in your brain easier
Hey guys, I'm a developer and I want to add on to this for those that are just finding this video like me. Question Everything: If you google a solution to a problem and someone says "Do X" and maybe X looks pretty confusing or convoluted, then you find yourself asking "There must be a better way," most of the time, there is a better way. Question it, do more research, and even attempt to come up with a solution yourself. It's worth it to spend the time finding the root cause to issues rather than making a hotfix or workaround that will likely be forgotten about later. Keep that in mind and your code will look much cleaner and you'll gain a lot more experience! Eventually, you'll gain a 6th sense for whether something is the right way to do it or not. Happy programming guys
Good advise but really irritating and overpowering (foreground ) music. While nearing the end, I could hardly hear what you were actually saying. Appreciate your good intent, thanks a lot.
Retention ability is crucial and simply reading something once or watching some tutorial you don't actually understand isn't helping you. It's just making you feel like your "working". Aside from a vague understanding of the topic (sometimes not even that) ... you aren't getting much and you'll remember none of it in a week.
I've learned "Computer Science" for 6 years, worked as a Software Engineer for 4 years, I would be "mediocre" at best because I literally did almost everything you suggested *NOT* to do. Right now I'm in a state where I don't know what to do and I also can't do a lot of things that I should do. Sorry, that was my rambletalk but great video, only wish I had this 10 years back.
he ash what are you programming what language? is no problem everybody is confused LOL , I started very motivated...wanted to be a self thaught developer to switch careers into programming...it was a long time ago since I programmed..I did formally in C language ..but I want to learn C#, Python, Javascript ..and some backend ...though I totally let it go for now...
I also started with giga huge project and ended up frustrated as i wasnt able to deliver and see what i wanted to see. it was a disaster so its good idea start slow and increase speed as you go.
I am struggling big time and nobody wants to help me . What makes it even more difficult is that I am a disabled man and can not afford college or bootcamp . I know a little python and even less Lua . I guess you can say I know a little C# and c++ I am trying to learn coding for game development . I would also like to make apps and website but my main goal in programming is to make games .
Some of this is disheartening. I get bored, WAY too easily, and I need to see tangible, significant results quickly or else I can't go on, and unfortunately I can't change any of that. Trust me, Ive wasted SO much time trying. So thanks for your insights, but I need to take a different approach.
I’m plan on moving to Austin hopefully in a couple years from Michigan . Thank you for the Software engineering coding tips. It can be hard at times struggling I’m taking a ten week boot camp with coding temple the classes are from 9-5pm mon-Friday with video on. It can be overwhelming definitely a lot info .
There are certainly exceptions, but most of what you will probably do in your first few years of professional development work is fix bugs and add features to a code base written by someone else, likely someone not even with the company anymore. So starting a bunch of projects from scratch where you’re the only developer is an incredibly unrealistic simulation of your future job. Go find a complex codebase somewhere you can contribute to (preferably in a language or framework you don’t know well) and start doing merge requests and getting code reviews. That’s way better experience for the actual job market.
![BOWKYLION - วิงวอน (ex-change) [Official MV]](http://i.ytimg.com/vi/cLdnZWDaO-w/mqdefault.jpg)
- learn from the fundamentals
- build real project
- use resource that have good reputation
- stay consistent
- focus on one thing at a time
- if you are stuck on a problem for a long time, just do something else, refresh your mind and come back
Copied and pasted in my notes
Great recap 😊
Thanks bro you saved my 8 mints
this is like legit the complete opposite of what i have done, somehow works wonders for me lol
- multi tasking 10 languages at once
- work 6 hours every other 5 days
- never finish any project
@@ed_iz_ed To each his own I guess
Give yourself time to learn things thoroughly - Don't burn yourself out by doing projects as quickly as possibly to get the job. Also practice EVERY DAY is a great tip!
I’ve never been able to keep a strong consistency to anything it sucks. Sometimes I think I have adhd idk
@@solomonKachi7000 Dude I also have a big problem with maintaining consistency and keeping up motivation. It's kind of something we all struggle with.
This is a very great advice but many people won't follow this advice....and I don't know why
I don't know bro, as sooner as you get the job you'll actually be practicing daily😅
@@Carramoz You would burn out. If you don't take enough time to grasp the concepts before a job, then on the job you'd need to put on more hours after work to learn and catch up. So you'd be spending your nights and weekends doing that. 14 hours or more a day just to catch up would burn you out quickly. It happened to someone I know. Burn out can be really tough to deal with once it happens. You'd have to stop from all of that and either take a break or never get back to it.
Notes for self and for others
1. Learn the *Basics First* and don't just dive into advanced just to look cool.
2. *Google Stuff* that you don't understand, don't just skim over.
3. Learn from *Standard Material* and not from random, unrated/less rated material.
4. *One thing at a time* . (For myself- Focus on Java DSA. Leave JS for some free weekend, Addon for another, CPP for 3rd sem and C# for 3rd sem weekends. Don't pick any new things, you've already many things to do.
For Drawing, make time.)
5. *Code Consistently* . 1 hr for 6 days is better than 6hr in weekend. (Because Memory curve)
6. Take your time. *Relax when exhausted, take a walk then restart* .
🙂
Did you complete JAVA DSA?
@@atifshaik No 🥲😔
1. I dived into advance topics just to look cool.
2. I didn't googled and cleared my doubts.
3. Didn't read Standard material
4. Tried many things at a time(Java DSA, C DSA, Cpp OOP, Android, Cyber security, web, and what not. But continued none🥲).
5. No consistently, I came back to write this reply with a coding break of about 3 months.
6. Initially I didn't relax and exhausted myself almost at a regular basis.
Hope that I fix atleast some of the things.
@@kumarutsav1123 Same happened with me and I took 6 months break as lost interest in programming but just started from scratch learning Java
Good stuff. Coding daily is soooo important. So many things to remember when programming so muscle memory is so important. Even if it's just 20 minutes a day. Code daily! Great as always Nick
Just the practice of reading code is so crucial
1.) Learn fundamentals/basics: Do you actually know the pre-requisites? Are you getting ahead of yourself? 1:37
2.) Google what you don't understand: Including single words. Comprehend thoroughly to retain information 3:07
3.) WRITE CODE: Build a project sooner than later, otherwise you are wasting time 4:07
4.) Reputable resources 5:08
5.) Stay consistent: Practice every day. Muscle memory 5:36
6.) One thing at a time: One project at a time etc. 6:12
7.) Re-fresh your mind: Relax your mind when you find yourself in a block 7:02
As someone who entered college with below highschool grade math, it is rough to pick things up. But having a solid foundation makes everything easier down the road. Dont skip!
hey, have the same problem? and I'm forced to take a lower course. have any advice?
@@russtoo just focus on logic, math in programming is not a big deal, the problem is that in college they teach a bunch or useless stuff and that includes complicated math problems with no actual use outside of academic environment
If you don't understand anything and feel like you are falling behind don't worry ,just learn at your pace , not everyone learns in the same speed
Thanks for the advice! It's true, when you first start learning it can be very overwhelming and the thoughts "am I focusing on the right thing?" and "what should I learn next?" are a daily occurrence! I'm still in my learning stage, been teaching myself for 3 months now and still going. I have to say, doing it every single day has been a game-changer. Looking forward to more content!
The video starts at 1:31. You better choose 1.25x speed (so you won't waste your time)
1:37 learn the fundamentals, don't skip the prerequisites
3:03 google every unknown word, don't skim
4:08 build real-world projects
5:05 use only reputable resource
5:32 be consistent
6:12 focus on one thing at a time
6:57 if you're stuck, close your laptop and relax
my best advice: while covid is still going on, screw going out with friends and partying. you got discord for messaging IF needed. sit in your room, defog the brain, get a white board or paper and start getting that brain running with practicing algorithm basics, learning to talk to your brain about what you are learning, software engineering basics by finding a framework and find applications for your basic algorithms. master 1 language, build a project, refine it and stay consistent.
@@bobanmilisavljevic7857 talking to women is easy. there are more important priorities these days.
@@bobanmilisavljevic7857 some people forgot about the importance of communication skills, networking, and balance healthy life. What's the point of sitting in front of the computer for 5-6 hours long where half of the time spent procastinating because your brain can't focus on anything for too long. They can tell themself that they're hardcore learners and those who use their time for social activities are lazy, wasting people. However, in the end, they can still seat on their basement all day long wondering why they've tried so much but still not get the jobs while those "lazy" people keep getting more and more offers by having friends refer them when applying.
@@bobanmilisavljevic7857 I used to be skeptical about improving social life, friend circle, etc until I got an internship which at the beginning I passed the screening round thanks to one of my friends referring me. It's true that learning new things contributes greatly to your career, but the importance of networking cannot be demeaned
Cool bro but how to do that with backend language like Java? How to "start" building if you need learn almost all the language first? Front end languages it's a bit simple i think, you write 2 lines of code and run live server and you see whats going on the screen.
@@huutriet2045 Even when I have brain fog and know I won't learn anything I put in 2 hours minimum. It is more about maintaining the habit than about learning because I know in the long run not breaking the habit leads to more learning.
i Love you , because you just spoke the truth, and your bodylanguage is telling that you are a professional.... instead of super hyping people , you are very relaxed, and you communicated the message very well... thank you
i've been trying to learn new tech and have been constantly stressing myself why am i unable to get concepts as easily as i thought i could, burning myself out and not touching it again for a couple of days. this video couldn't have come at a better time. thanks, love your content man
Data in and data out. Write concepts down on paper like your logic and how you think the data should be transformed then use the tools in your language to help shape that.
This video has actually opened my mind. I have a final year project that i am currently working on and just realized that i skipped the basics of the technology and framework that i am using and just jumped into doing the project. thanks man.
What I've found extremely helpful is going back to my completed programs and rewriting them with the new knowledge I've gained. Making them cleaner, more efficient, using better and more complex concepts and methods within the language.
I applied these tips and I no longer waste any time when learning code, thank you 🙏
@@bobanmilisavljevic7857 Bro changed his entire life in 3 business days XD
I don't know whether you wanted to support him in a nice way, or wrote a sarcastic comment with a sarcastic buddisht way of thanking him!
but you still wasting time watching youtube clips *LOL*
L O L @ this 🤦🏻♂️🤣
+kenny did you get featured in interstellar?
I find learning best by trying to have a problem that needs solving, or thing that needs doing. Then you burrow down in to it and learn so many new things.
I'm grateful that you did this. I'm a total beginner and I've been learning to code for about a week now, and your advice on coding every day, not sparing fundamentals and learning one thing at a time is just gold for me. I never rush until I actually fully understand each new concept. Thanks a lot ❤
great stuff. love how you calmly delivered the message not unnecessary yelling and emphasis.
it's hard to get a guy to talk pure truth. He's taking the words right out of my mouth. Especially the part with reading it and understanding the words instead of just skimming over it (which i always do). When you actually break it all down by googling the jargon its starts to get easier.
I think the advice of just taking a break when you are genuinely stuck is great. There were times in my algorithms class when I would literally look at my computer for 5+ hours straight with no progress. In that time I could have worked out or done really anything. Sometimes all you need is a fresh mind to get the task at hand done instead of brute forcing it.
This video is for me... I am trying to save time. Sometimes is so frustrating: I study things, take tons and tons of notes (in Italian, 'cause English is not my first language), even do exercises... After I don't use them, then... Time passes I forgot all and I have to re-study again.
Thanks for the tips... There are errors I've heard that I actually do.
I can confirm on the skateboard analogy. I got an e-skateboard and went 3-5 mph on the first week. In my mind, something was telling me to hurry up and go faster. I ignored my thoughts and went with the flow. After a month of non stop skating, 30 minutes a day, I was pushing 22mph. Fast forward 2 years later, im pushing 35mph. Just enjoy what you’re doing and don’t force yourself to learn.
Was wasting time on yt while coding so I clicked on this video.
Then I immediately closed the video to get back to coding, thanks man!
😂😂😂
🤣🤣🤣
Hahahaha
😂😂😂😂
Instead of wasting my time...Im watching a TH-cam video about how to not waste my time
Thank You So Much for this wonderful video..............🙏🏻🙏🏻🙏🏻🙏🏻🙏🏻🙏🏻
I agree with you on what you said.
Note: The music was high than your voice, so next time if you lower it, it would be great.
Daily practice is the key, rightly said.
I started watching your videos few months ago and i really started to like those.... and it goes like when ever i saw your video, i stop watching other videos and continue to yours's... you deserver more than you have now(subs)
This is the BEST advice I’ve heard on TH-cam for learning how to code! You might be the only person who stresses the prerequisite part of the process, which is so helpful to hear. Thanks!
Agree. One sign of a bad programmer - only wants to get a job. You gotta love the tech, that means you gotta learn the fundamentals. What I don't really agree is that you can't really avoid wasting time. Usually the guy who tells others not to waste time is the one who has wasted lots of time struggling with difficult problems and climbing a steep learning curve...
I have been always confused with concepts, whenever I start following some tutorial I found many vocabs and concepts that makes me confused and I ask myself "Should I open a new tab to google that concept?" because I always think that this is just wasting of time..
But now you confirmed that it was just the opposite, and it was the right thing to do.
So thank you so much, sir, you got my subscription with a Like and this comment that I made with love.
Fact of the matter.. learning is not fun until you know what you're doing. I PROMISE that once you understand the fundamentals, coding and building software feels like ART. It becomes FUN. You just need to learn to walk before you run, and you need to learn to crawl before you walk. Don't worry about security, setting up ci/cd pipelines, what dependencies you need, about coming up with a scalable design. Forget CORS, disable all. Forget the front end. just start by building a serviceable API. As you learn more, you'll learn how modular everything is. You can add security over your app later. You can add exception handling later. You can add logging later. You can add swagger later.
JUST, MAKE, IT, WORK. If I send a request to your API, I get the data I want back. end of. Add things one by one. Don't move on to another framework until you master the one you're currently using.
I seriously luv you low key approach Nick. Keep it up!
seems like good tips for learning stuff in general, not just for coding
The music is too loud and distracting. Otherwise, good advice.
sorry i had to rush to film & edit this video in the span of a few hours to do a last minute promo for tech skills day tomorrow 😁 future videos will be higher quality!
Thanks for your video and insights. I'm new to coding and learning Python. I agree with all your points and tips and have known about and used the same ideas in all my endeavors and they always work for me. So, though I didn't come away with anything new from you, it does validate my own thoughts and methodologies. You and I agree on every point. Thanks for the video!
Really good advice, especially for learning one thing at a time. I could find myself 'stuck in motion', not moving into any meaningful direction by taking part on way too many projects I could handle at once and mixing stuff up.. Projects shall have their own timelines to be managed efficiently.
The third one is very useful. You really have a gift in making complicated things easier to understand. Keep the good work!
Also try to reduce as many distractions as you can when learning to code or if you're coding for practice.
Learn Fundamentals
- There are fundamental things you need to know before you jumped in to more advance things.
- Question yourself, whether you having some improvements whether you having impatient and you are trying to learn more advance than you should be or maybe take a step back and think do you learn fundamentals.
- Make sure you understand all fundamentals.
Google what you don't understand
- You might see words that you don't understand, if you don't understand something, you should look this things up and learn those.
Actually write code
- Recommend to build real world projects and it can help you a lot.
Make sure you use repeatable resource
You should be coding everyday
- You really need to practice consistent because in coding you can forget things pretty quickly.
Focus on one thing at a time
- Focus on one thing and be good at it because it will lead you to success
Take a break and do something
- If your mind is in not in the right state, take break.
- Relax yourself, there's no reason to stress yourself
hi Nick! Thank you so much for these advices especially the first one! coz i personally make this mistake and need to learn to slow things down and give my brain the liberty to process things . and yes i should stop 10hr long coding grind sessions and instead practising coding 2 hr/day. these tips will definitely help me survive and i guess be at better position at the end of this college semester!
this came in the right time
I live in a rural area but need to touch and see items for coding, do you get what I'm saying?
Give me a tip to start and use real objects for coding, please.
You know he’s a good software engineer by the dead sleepless eyes, he looks like the riddler from Batman.
True, I’ve been using c and c++ a lot and recently been getting Python and started on page 1 even though I know the basics because it helps bring back things you’ve forgotten and helps with new syntax too.
Coding is hard! I'm glad you like Austin! Thanks for the videos. Hopefully, down the line we can just download knowledge via neuralink. I really only want to learn programming so I can work on VR/AR google glass. If I had 1 billion dollars I would invest it all in google glass, it's the future. but before all that I need to learn how to encipher/decipher a text...lol.
Keep your eyes open for other projects too! Meta's quest 2 is dominating the VR scene at the moment with market share and incredible price/performance. Also, they're working on AR with project cambria which is unreleased but worth noting as it has potential
Thank nick white 🙏 for sharing your great knowledge with us 👌
Nick White, The Great 🎉
Keep up the great work!!!
I dig your advice one. Yeah, you shouldn't waste your time by trying to understand things way above your level. Good one!
Thanx for this, I think I was in need for such advice 🧡
So many gems here, I would say the same goes for learning data science!
or anything really
Thanks for the video!
I had some fundamentals from college and doing some hacky stuff for work. I am now developing a game breaking it down into parts to make it manageable
I discovered your channel yesterday, and I want to thank you! Your videos are really helping me :)
The biggest time waster when learning as a beginner: trying to make it perfect. So instead of writing code and making it work you spend days tryin to do it in a "right way". It has to follow the best practice, it has to apply design patterns and most modern approach. And month later instead of having 10k lines of code that do something you have 500 lines that do nothing.
Just make it work. And then if you want you can come back and improve things. But you don't have to. You can start new project and make sure you do it better then the last time. Refactoring can improve your knowledge but as a beginner there is a greater value in simply starting more projects. Especially if you don't have university degree, your hobby projects will be your "diploma" when looking for the first job.
kinda disagree here. It's true that before jumping into these concepts, you need to do some projects to get yourself a little bit of experience. But still, if you just blindly rush into projects without acquiring skills such as writing good test, clean code, refactoring, your code would still be rubbish. I'm not saying we have to learn all about testing, refactoring as a beginners because some techniques and scenarios require a long exposure to that matter to really get it. However, you have to learn them along side with doing projects to know which part of your code is unreadable, unmaintainable to get your project improved in the future. Also, you can practice the good practice at the beginning and don't have any bad habits at the long run. Lastly, I don't think coming back and improving your old projects is not necessary. You can see what mistakes you had earlier, practice to improve old ugly code (legacy's code), and from that, you can learn to avoid those bad practices and write cleaner code in the future.
@@huutriet2045 "You can start new project and make sure you do it better then the last time." is key.
I guess it also depends on the project
the example I would give is that my first kernel project was compiled on gcc with like 20 flags
then i did it again "better than last time" using a cross compiler, and other better practices
@@dumbfailurekms did I disagree to that? I mean going back and trying to improve your old projects is not an unnecessary thing since if you can improve them, your've improved yourself.
Really good and simple things to keep in mind! Reminding them from time to time will be definitely beneficial. Thanks a lot!
Thank you. Im like a week into starting and this is important as heck to hear!
Dang, you just described me, I quit school in the 9th grade, and I’m struggling hard with college algebra, and I’m also taking the advanced developer course, guess I’m in for it.
I have coded since 1981 and I know less about it now and hate it more now than I did 43 years ago.
Fuck programming. I will leave that to those who invest their entire lives into it.
I will stick to proving math theorems. It is what I love, what makes me happy.
people, pls dont be mad when I say this, but if you're wasting time to get to learning, you should just stop. I mean it, I applied these step(s) in my life and it really changed me for my better final self.
Remember folks, its not about the journey, it's about.
That last one is true. I can't count on both hands how many times I got up from a project I was on because I had no idea what I was doing and wasn't making in progress, so I would get up and leave the computer. When I would return, the entire project seems easier. As if I knew the answer the entire time. Also, there are times when you are taking a break that the solution will come to your head without you sitting at the computer staring at a screen.
This is more like a metaphor for how not to be a complete failure in life, than a coding philosophy
really appreciate this, thanks Nick.
Hes right. Google the definition of API. APPLICATION PROGRAMMING INTERFACE. Then google definition of Application, programming and interface. Never assume you understand anything.This method is gold.
Some very basic concepts, but so true. Great info
I'm new to your channel,day 1 in learning how to code,great content btw.
Thanks a lot, I am a freshman in CS, and I found your video really helpful😊
wow! this is exactly what I'm going through! Thank you!
My two cents as a newbie, ChatGBT has been great assistance/tool. It’s like having a tutor to answer questions you would pose to a teacher. It’s great for explaining things with detail
great tips Nick
this is a good, candid take. Great stuff. ty
I think comparing it to math is the perfect comparison. Whenever i was teaching myself math while getting ready to go back to college. I had to stop.. and humble myself when I literally had to go back and learn 5th grade math concepts i'd forgotten. It is humiliating to be watching a math antics video designed for children, as a full grown adult, but it was necessary because things seemed far more difficult to understand than they should have.
This is honestly much better advice than I usually hear on youtube lol
I agree; reduce the music volume by 0.5x
Is it possible for someone to summarise it? @nick
thank you very much for this wonderful piece of information.
same, alot of information you need to grasp in coding whilst being competent in society also i am a freelancer. Sleep is a sacrifice
Counterpoint to looking up every word you don't understand: Moderation is key.
If you're like me, you might find yourself falling down a wiki rabbit hole, and never finish the original article/etc. If you feel you can approximately understand the concept, great, write down the term, and move on for now.
Unless you are learning programming for the first time ever I disagree with learning the basics before more advanced stuff, that's how you get into tutorial hell and never learn anything useful. If you try to build something complex you will end up dividing the features into small tasks and learn the basics while you are trying to code those tasks. I learned React before javascript, I ended up learning javascript while trying to build something with react.
I wanted to learn redux so instead of watching videos of people building todo lists and wasting money on courses I decided to create a spotify clone straight away, only needed the documentation and learned a lot because I was solving problems myself instead of copy pasting code.
You can try to understand some advance stuff (one at a time) and while doing so you will search information and learn about the basics and keep that information in your brain easier
Please reduce back ground music. it is too loud
Dude thank you so much. This is such a good video to keep on my head while im learning how to code 🤙🏼🔥😘
Thank you lot for this great video and hope I can find something similar for web development too in your channel.
Thanks! I really liked your advice.
Hey guys, I'm a developer and I want to add on to this for those that are just finding this video like me.
Question Everything: If you google a solution to a problem and someone says "Do X" and maybe X looks pretty confusing or convoluted, then you find yourself asking "There must be a better way," most of the time, there is a better way. Question it, do more research, and even attempt to come up with a solution yourself.
It's worth it to spend the time finding the root cause to issues rather than making a hotfix or workaround that will likely be forgotten about later. Keep that in mind and your code will look much cleaner and you'll gain a lot more experience! Eventually, you'll gain a 6th sense for whether something is the right way to do it or not.
Happy programming guys
Good advise but really irritating and overpowering (foreground ) music. While nearing the end, I could hardly hear what you were actually saying. Appreciate your good intent, thanks a lot.
Retention ability is crucial and simply reading something once or watching some tutorial you don't actually understand isn't helping you. It's just making you feel like your "working". Aside from a vague understanding of the topic (sometimes not even that) ... you aren't getting much and you'll remember none of it in a week.
great video, but just something I wanted to point out on the recent vids, sometimes the volume of the music is overpowering the voice.
Thanks for the inspirational video.
I love and agree with the angle you are coming from. Thank you. what are the fundamental pre- courses necessary to take before I take a coding course?
I've learned "Computer Science" for 6 years, worked as a Software Engineer for 4 years, I would be "mediocre" at best because I literally did almost everything you suggested *NOT* to do. Right now I'm in a state where I don't know what to do and I also can't do a lot of things that I should do.
Sorry, that was my rambletalk but great video, only wish I had this 10 years back.
he ash what are you programming what language? is no problem everybody is confused LOL , I started very motivated...wanted to be a self thaught developer to switch careers into programming...it was a long time ago since I programmed..I did formally in C language ..but I want to learn C#, Python, Javascript ..and some backend ...though I totally let it go for now...
Hey I live in San Marcos!!! Welcome …. Come down to the river
I also started with giga huge project and ended up frustrated as i wasnt able to deliver and see what i wanted to see.
it was a disaster so its good idea start slow and increase speed as you go.
I am struggling big time and nobody wants to help me . What makes it even more difficult is that I am a disabled man and can not afford college or bootcamp . I know a little python and even less Lua . I guess you can say I know a little C# and c++ I am trying to learn coding for game development . I would also like to make apps and website but my main goal in programming is to make games .
For me Calculus was very easy and I understood it quickly.
Helpful vid thank you mr. nick.
Some of this is disheartening. I get bored, WAY too easily, and I need to see tangible, significant results quickly or else I can't go on, and unfortunately I can't change any of that. Trust me, Ive wasted SO much time trying. So thanks for your insights, but I need to take a different approach.
Muy bien Nick, gracias bro
I’m plan on moving to Austin hopefully in a couple years from Michigan . Thank you for the Software engineering coding tips. It can be hard at times struggling I’m taking a ten week boot camp with coding temple the classes are from 9-5pm mon-Friday with video on. It can be overwhelming definitely a lot info .
sheesh. good luck! absorb as much as you can
There are certainly exceptions, but most of what you will probably do in your first few years of professional development work is fix bugs and add features to a code base written by someone else, likely someone not even with the company anymore. So starting a bunch of projects from scratch where you’re the only developer is an incredibly unrealistic simulation of your future job. Go find a complex codebase somewhere you can contribute to (preferably in a language or framework you don’t know well) and start doing merge requests and getting code reviews. That’s way better experience for the actual job market.
instructions unclear, am now a Lego engineer.