@@rMjojo “reading the docs” just means whatever you are working on has some documentation associated with it (hopefully), and whenever you want to use a specific feature you should be able to find it in there. Also it’s good for configs and debugging.
If your using scratch, do a tutorial , look at the code and with the note feature anaylze what it does and what problem it solves , look a t a platformer game , look at there code maybe remix it and note down what the code does , and that's how to improve code in scratch ,
What? No it's not, this is a video to help you start actually learning, tutorial hell is when you don't learn anything because you're just copying tutorial code.
3th option is just 🔥. The "WHY" in reading people's code and trying to understand or come with a new idea can develop your skill way faster. Also i try to code as much as i can after a tutorial but without going to the parts when i get stuck and when i feel finished kinda, then i go and see where i did wrong from the tutorial. It helps remember essencial things faster and maybe sometime think outside the box. It works for me personally :)
When I first got into programming I got into tutorial hell for 3 years and didn’t know why I didn’t know anything. So happy I got out of it 9~ ish months ago
@@zakyvids6566 If you are just starting I suggest learning python as it is easy to learn for beginners and fun to make projects with. If you are confident with it and are familiar with other coding knowledge after learning it you can branch out to other languages (in my opinion that would be js).
I got started by the guy in the tutorial teaching me something, then telling me to apply on the bigger picture of a project by myself as a challenge. Then once I finish the project, I try to do one completely on my own with the help of googling of course, but then I feel so proud when it works
I get you. As I spent hundreds of hours learning and not doing anything with that knowledge I got nowhere. Once I started my personal automation project, everything just clicked. Whatever I forgot, I just opened the tutorial I subscribed to and it helped. And for any problems I got into, there was always SO, Google, and GH. Just awesome, I am very close now to turning my scripts into GUI app so I can share my project with other people in the same position as me in my company.
Not gonna lie, I’ve started my boot camp on udemy like 2 days ago and it felt so good trying to solve a problem on my own rather than going back into the course to see what I mad a mistake on. Took me like 10 minutes but at the end I was super happy I had solved my first problem
This one guy’s introduction to Java (for writing Minecraft mods) series had videos in-between the tutorials where he would have something for you to program using what he had taught so far. First there was “Program a simple trivia game” and eventually “Program a fully-functioning Tik Tak Toe game”. He also encourages messing around with the code however you want, suggesting you make a simple game of your own.
Stopping watching tutorials helped me a lot. I also explained the task, code and problems & resolutions in documents. It helped me remember and understand code better
Honestly, the fastest way I’ve ever learned anything computery (coding, 3D modeling, etc.) is just by coming up with an interesting problem to solve in that realm and then researching everything I need to know to solve it one step at a time. I always end up learning WAY more doing that than just going along with written documentation or tutorials
I learned web development in the early 2000s reading code available on the internet... At first, i didn't know why or how a piece of code would do something, i just knew it did. Little by little, reading the documentation, i learned how. Then i read a complete tutorial to make sure i didn't miss a piece of knowledge. Reading other people's code is really helpful.
Tutorial hell hits me the most.. especially when transitioning or learning a new programing language. Honestly these tips apply not just with programing language but with other tech topics such as k8s, IOT, DB, networking etc... Training or tutorial are a good start but applying the tutorial to real world scenarios is the best way to learn.
Thank you for this. At least let's me know that all the work I've put into this skillset has been in the proper direction so far. And you seem trustworthy and knowledgeable. I'll take it.
How I learned: making a new project without reading any documentation or watching a tutorial, so far I have extended myself up to 12 programming languages.
I found that watching tutorials at 2x speed inadvertently made type a lot faster, not sure why. At one point I was like how are these guys typing so fast, then I remembered it was 2x speed. It ended up being was a two fold reward, I wanted to spend the least amount of time on the tutorial I was watching and it ended up improved my typing ability.
Number 4: read the documentation. Even if you're at zero level, documentation usually have something like introduction and small tutorial that is enough to write code.
I especially like the reading code advice. A lot of what I learned about meta programming I learned by studying Ruby gems that used it like Rake, RSpec, etc. I often learn a lot about the tools I use by reading the code, as well.
I really liked one of your advice from another short is building your own projects on other people's open source projects that you like (if that's what you meant). Although might be overwhelming if you're not familiar with the language or concept but it's still a step in learning new things.
I think the best way to improve at programming is to not immidiatly google any issue you don't understand, but to try to figure out how to solve it using just the docs as it forces you learn how to solve the given problem, rather than just the copy pasting other people's code
I think in general if you want to learn something you need to always do the thing that you wanna learn. One example is gaming, when you play a game for the first time its going to be confusing but the more you play, the more you understand how it works
Do cs50 I just spent all day to right a tiny bit of code (8hours for like 15 lines) but when it all came together holy I felt good and i did mot use any tutorial.
You know i'm learning programming slow but i'm doing it like you said and i don't regret it because its true that i'm going on slowly but atleast i'm learning properly
How can I start doing projects if I haven't master the fundamentals? Is'nt it better if first I do tutorials to master the fundamentals and then start doing projects?
Tip 3 imo is the best I vaguely understand a bunch of programs by just reading them, most of the time if I don't understand a line I google and it and shows exactly what it means
The way I learned was coding card games and calculators that do specific things. I am actually still learning python by coding games like Mancala and Devils Grip
As someone who excels in his computer science class and after school programming classes which are considered to be really hard, I 100% agree, this is what you should do, now next time someone asks me how do I learn to code ill turn them to this video
If I don't any logic of programming then what will i do after reading others code?? I learned every syntax and definition but it's of no use 😔.... I'm having only one problem that nobody could solve 🥺... How can i make my own project?? How means how??? How will i know what to do next??? When to use Or execute this particular code step?? All are saying only one thing build project! Build project! Build project!!! Nowadays im doubting myself I'm going to be a good programmer or should I quit this.... Stuck with this from passed 1 month... By everyone are saying same thing practice practice practice, but what to exactly practice??
I didn't start learning Vue by reading tutorials... I just started a job that had Vue in it. I find my easiest method of learning is being given the resouces to find the existing code, and how it relates to other code, then it's pretty straightforward from there...
I use to pick up ancient programing languages by garbing a manual, and some sample code within 24 hours. Basically, there were only so many ways to open a file, read an input, compare data, move data around, do math, display text, write output, and close a file. Once you have a framework to be able to answer these questions, you can code in other languages rather quickly.
I wanna a say a big thanks to you. I facing problem with this 'tutorial hell'. As a 2nd year from a decent college I thought that the only way to ace a technology is doing a multiple courses on online platforms and RU-vid. Nowadays some thought are come in my mind that programming is not for me. I'm feeling stressful and stuck. You opened my eyes. Helped me to think twice. Helped me to understand how to learn programming in right way. BTW ♥️ from 🇮🇳. Your videos are really helped me a lot.
These are some pretty usefull tips, but i would add 1 more thing. Do not overwork yourself. if you are stuck on a line that you can't get to work, than just take a break, maybe watch some youtube or play videogames , and try later, problemsolving is way more doable if you do it with no stress, and you will probably figure out the aswer sooner then trying otherwise.
Yep I am just starting making Minecraft mods I watched 1 tutorial on how to get it set up and started then I was on my own with nothing but google and looking at other peoples code to see how they did it has help me much more then tutorials
The way i started to lean code was from computercraft (a mod for minecraft) I was programming pcs with lua code After that (outside the game) i got into python and C++ (for arduino)
Can you start a series of programming for absolute beginners. Specially people with experience in other domains such as design, account, marketing. Problem with experience is that you have a expertise and you brain is framed so so what exactly to unlearn? Learn new? Observe things?
Actually good advice! Thanks! RU-vid kept giving me code advice like "Lol use stack overflow" or, "Learn c variants or you're a b**** a** p****." Good to see someone just be genuine.
That last bit is really important. “As a programmer, you’re more likely to read more code than you are to write code.” Very true. You may learn how to code on your own, but a key thing about programming is that you’re almost always going to be collaborating with other programmers, each of whom have their own styles, experiences, attitudes, etc. There will always be a certain level of self-sacrifice when working with a team. In other words, oftentimes you will need to adjust your own habits and style of coding to follow the coding conventions of the team. That’s the hardest part-being able to quickly pick up the work that others have done and adjust to the coding conventions of the team. So you should always be open and willing to learn. Coding is a journey that will have you constantly learning something new!
