@@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.
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 :)
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
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.
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.
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.
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.
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
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.
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
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!
Actually good advice! Thanks! UA-cam 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.
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?
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.
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
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.
I didnt really learn from anything about python. Just a 1-2 hour tutorial. Then I forgot it all. Then I read (and watched) some stuff about hash in python. And I made a hash viewer app. Currently has 71 lines of code. Might be more in the future, who knows. I updated it 3 times in the same day.
Best advice I ever received was “All truth is assembled, you should always be trying to take in as many ideas as you can; keep what works for you and ditch the rest… by that I mean that someone else has already solved your problem, so just got find their solution as a starting place and then refactor it to fit your context” This idea has become what I like to call “open-source piracy” and it has never let me down in the 10 years I’ve been writing code 😂
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 UA-cam. 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.
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.
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.
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.
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 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 biggest problem is that most people really don't have any meaningful problems to solve with programming and reading code by someone without any objective can be supremely boring.
As a gamedev who's currently learning Godot and did a horrible game on Scratch recently, I agree with the first step a lot, and I want to add something to it. You might like check tutorials every now and then to know if what you're doing is right or wrong, but don't check tutorials like every milisecond. Try to watch the tutorial on progamming very carefully and memorise things! Tutorials will make you forget the smallest thing such as removing a certain filter in a sprite if you get into the tutorial hell trap.
I'm a software engineer. I 100% agree with this guy. Tutorials are good but you need to use them to build your own programs. If I'm learning python tkinter I'm learning it to make my own gui and implementing my own things as I go. If you're new to the field I definitely recommend picking up some arduino beginner sets and learn programming for micro-electronics. Arduino IDE is a good place to start. Now you're steps away from making your own product or just tinkering away!
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
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...
A good tutorial isn’t about the thing it creates, a good tutorial explains everything it does and why it does it. No matter what the tutorial is about, wether it’s coding, a blender project, building a table or a Minecraft house. (of course, if it’s an “advanced tutorial” it doesn’t need to explain the bare basics)
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 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
Great advice. I personally went through tutorial hell for python. Just keep learning and learning but never get the hang of even the most straightforward programming language. Then I started my Automation project using Selenium and Python, and I am a much better Python coder. I can understand others' code much better than when I was in tutorial hell. Now that I have finished my automation script using Selenium where most of my work is based on Web Browser, I have moved on to make the script into a GUI so others in the same position as me become more efficient and productive using my script.
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??
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?
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.
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
The only way I was able to learn an engine or language, was to make a full program (with only looking up what I needed help on) I now know Unity, Godot, and Unreal. And python. I now work for a Game Studio. I have learned to only look at forums, I don't watch tutorials for more then a minute to just quick grab something I forgot
Number 4 > Start taking as many interviews as you can, unknowingly you will start learning different approaches for different problems asked by the interviewer.
was stuck like that, learnt about tutorial hell, switched to docs and stackoverflow, asked help from discords and now i can do anything tbh. currently working on a meme generator im writing using only c and win32 api with the help of 2 winapi discord bros and after finishing that wanna also start contributing to open source projects. btw, i started out with brackeys
I remember when i was starting out in coding. I got so depressed that I was looking up Google for every issue and getting "answers" from similar codes on the internet. Untill a senior programmer told me that is exactly what i was supposed to do and he still ran into problems even after 5+ years of experience on that language.
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)
what i have been doing is watch a tutorial like one of yours than i would play around asee what i can to change it to better understand what that thing does. Like if iam trying to set a varible that is refrence through multiple .py files i would watch the tutorial than i would re do it again on my own and change things to serve or display a different purpose or thing. Another i would do is pay attention to how the person im watching write the code so learning different formating is good to by reading the other persons script.
In my 6 months of coding (java Minecraft mods) I have watched 2 tutorials and read 1, it took me way too long to watch those videos it just worked better for me copying bits of code to make something 🙃
My advice from personal experience, start a tutorial, quit at half or so when you feel like you know enough, set a mind on a project and try to make it using available docs and help from online forums...
I personally always followed tutorials until I had the basics. I also tinkered around with them to understand them better. Once I had the basics I just startet using programming to solve problems I had. If I ran into something I didn't understand I I'd watch a video on how it works and how I can implement it.
In addition to reading other peoples’ code, try looking into the documentation first. The documentation will explain the ins and outs of how to use versions instructions and other peoples’ codes are examples of how it’s used, what went wrong, and how to fix it. Sometimes just reading the documentation is better than watching a tutorial or looking at examples. If you’re trying to learn a new topic, the documentation is like a free textbook written by the creator on how it works; the syntax, the use cases, how it functions behind the scenes, etc.
What’s the best advice you have received? 🤔
Apparently juggling helps with coding. It helps to train to brain.
@@livinginthisgalaxy7961 I gotta try this
@@CodingWithLewis not my own tip but after hearing this I realized that the only 2 people I ever known who practiced juggling were also programmers 😳.
Programming tips i received:You should leave programming
Googling stuff is ok
Reading other people's code is the way I learned 😊
Arguably it's the best way to learn :)
Where can i find others people code
@@Kirtoisplayz Thanks
ua-cam.com/users/shortsAfiC6itTN6c?feature=share
Might help you ❤️
Me too:) And I'm More likely To Use Split Screen.
Learning how to read documentation was a huge boost for me
I want to learn how to read documentations too , any suggestions bro?
@@mohammedislam733 usually whichever tech you’re working with will have some form of documentation. Check out their “quick start” or FAQ section
Unfortunately every documentations for different language and frameworks have their own different way to read
What exactly is documentation?
@@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.
"As a programmer you are more likely to read more code than write code". Well ain't that some truth !
ua-cam.com/users/shortsAfiC6itTN6c?feature=share
Might help you ❤️
Copy and paste
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 :)
@@bipo4715 not everyone in planet has english as their native language, but hey glad that mistake made you smile. Stay safe.
"How to fix my stupid javascript code"
i felt that
+ felt that on personal level
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
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
Did you follow same tips as the video and If so what programming language ?
@@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.
tutorial hell is right along the lines of repeatedly watching programming advice videos 🤷♂️
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.
Then that's not tutorial hell but programming advice hell.
More like advice hell
Can someone tell me whay advice hell is and is it bad, if so why?
I personally never really watched tutorials. I mostly fiddled around with code and looked at command references, and I learned very quickly that way.
I am a software Architect and have been developing for 4 decades. THIS is great advice and i wish people will hear the message. Thank you!
"You are more likely to read more code then to write code" so trueee
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'll try that...thanks
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.
So true. I gained like more than half programming knowledge just by solving problems.
So simple and positive explanation. God bless you brother🙏
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.
Luckily I'm doing all these tricks 😁
I mostly learnt not by seeing too many tutorials but making real time projects 😎😎
Big true. My school had us learn syntax of 5 languages instead of learning actual concepts. Such a waste of time.
Same. Online coding challenges were a real eye-opener for me.
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
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.
Reading docs and other's code is very good advice.
I really prefer reading and modifying others' codes rather than watching tutorials only and that really helps me!
I agree with all of these, they all helped me when I started out coding
"Read other people's code", I learned a lot more from that than I ever learned from tutorials.
How to make it look like your good at coding
1) go to stack overflow...
This is my favourite programming youtube channel.
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
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!
"Be a problem solver not a programmer" is so true it needs an hour long explanation
How to solve a problem without being a programmer? Copy& paste?
I just realized that I'm trapped in a tutorial hell..!
same
Try building a project or game.
Start with a simple project then do big projects.
This is the only way in my opinion.
Me too 😔
@@vaibhavnayak3416 what type of project for java
@@spysynth1422 how much Java do you know?
Actually good advice! Thanks! UA-cam 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.
You inspire me everyday!
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?
This extends to basically anything you want to get good at. Great advice overall for anything.
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.
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
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.
I didnt really learn from anything about python. Just a 1-2 hour tutorial. Then I forgot it all. Then I read (and watched) some stuff about hash in python. And I made a hash viewer app. Currently has 71 lines of code. Might be more in the future, who knows. I updated it 3 times in the same day.
What's your experience so far.
I am starting out I need advice.
@@maverickstudiosofficial i quit python, idk why but I just don't feel like coding in it currently
Best advice I ever received was “All truth is assembled, you should always be trying to take in as many ideas as you can; keep what works for you and ditch the rest… by that I mean that someone else has already solved your problem, so just got find their solution as a starting place and then refactor it to fit your context”
This idea has become what I like to call “open-source piracy” and it has never let me down in the 10 years I’ve been writing code 😂
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 UA-cam. 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.
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.
love these shorts. Also best advice, never over promise.
I'm in that "tutorial hell".
Thanks, you made me reconsider my choices.
This is awesome, useful advice
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.
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.
Reading other people's code is the best advice I can give someone. I learned unity C# from reading others code.
But it gives me depression to read others code coz I think how did he write code by himself and i can't
@@spysynth1422 read more
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 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 biggest problem is that most people really don't have any meaningful problems to solve with programming and reading code by someone without any objective can be supremely boring.
Vim (or vim keybindings) is also good for me to code faster. Although it has a steep initial learning curve, the benefits are worth more.
Reading documentation tends to leave out crucial steps for a beginner. Leading to stagnation and quiting.
As a gamedev who's currently learning Godot and did a horrible game on Scratch recently, I agree with the first step a lot, and I want to add something to it.
You might like check tutorials every now and then to know if what you're doing is right or wrong, but don't check tutorials like every milisecond. Try to watch the tutorial on progamming very carefully and memorise things! Tutorials will make you forget the smallest thing such as removing a certain filter in a sprite if you get into the tutorial hell trap.
I'm a software engineer. I 100% agree with this guy. Tutorials are good but you need to use them to build your own programs. If I'm learning python tkinter I'm learning it to make my own gui and implementing my own things as I go. If you're new to the field I definitely recommend picking up some arduino beginner sets and learn programming for micro-electronics. Arduino IDE is a good place to start. Now you're steps away from making your own product or just tinkering away!
I’ve watched 3 tutorials, one for python, one for JS, and a little for html.
This the best .. I’m 70 percent good at tuts but can only 30% good applying it in reality
How to code faster:
1.Copy
2.Paste
3. Job done, you are incredible
One reason you read more code than you write is because you read the code when you write it, and read it again when debugging
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
I naturally done this all before I was beginner.
I definitely do these three things and have saved me a lot of headaches.
More shorts like these please !
Deal :D
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...
A good tutorial isn’t about the thing it creates, a good tutorial explains everything it does and why it does it. No matter what the tutorial is about, wether it’s coding, a blender project, building a table or a Minecraft house. (of course, if it’s an “advanced tutorial” it doesn’t need to explain the bare basics)
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.
This is so True, Excellently Well Done!
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
Gold nuggets as always my friend thank you ❤️👍🏾
Great advice. I personally went through tutorial hell for python. Just keep learning and learning but never get the hang of even the most straightforward programming language. Then I started my Automation project using Selenium and Python, and I am a much better Python coder. I can understand others' code much better than when I was in tutorial hell. Now that I have finished my automation script using Selenium where most of my work is based on Web Browser, I have moved on to make the script into a GUI so others in the same position as me become more efficient and productive using my script.
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??
ChatGPT now is my best friend in solving issues😂
That's exactly what I'm doing! I'm so happy what I'm doing is the right way to do things for the first time!
For the third tip worked a lot for me
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?
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.
Reading other people's code is my job. I average writing around one line of code per week.
After watching this video I found that I'm doing Right ❤️
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
The only way I was able to learn an engine or language, was to make a full program (with only looking up what I needed help on) I now know Unity, Godot, and Unreal. And python. I now work for a Game Studio. I have learned to only look at forums, I don't watch tutorials for more then a minute to just quick grab something I forgot
I actually just started but I am learning the basics
One of the ways I got better was reading code in language, and recreating it in another
Number 4 > Start taking as many interviews as you can, unknowingly you will start learning different approaches for different problems asked by the interviewer.
Lewis, great tips ….👋🏻🇮🇹
was stuck like that, learnt about tutorial hell, switched to docs and stackoverflow, asked help from discords and now i can do anything tbh. currently working on a meme generator im writing using only c and win32 api with the help of 2 winapi discord bros and after finishing that wanna also start contributing to open source projects. btw, i started out with brackeys
I remember when i was starting out in coding. I got so depressed that I was looking up Google for every issue and getting "answers" from similar codes on the internet. Untill a senior programmer told me that is exactly what i was supposed to do and he still ran into problems even after 5+ years of experience on that language.
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)
what i have been doing is watch a tutorial like one of yours than i would play around asee what i can to change it to better understand what that thing does. Like if iam trying to set a varible that is refrence through multiple .py files i would watch the tutorial than i would re do it again on my own and change things to serve or display a different purpose or thing. Another i would do is pay attention to how the person im watching write the code so learning different formating is good to by reading the other persons script.
As progammer javascript & python, i confirm google and stack overflow is your friends
In my 6 months of coding (java Minecraft mods) I have watched 2 tutorials and read 1, it took me way too long to watch those videos it just worked better for me copying bits of code to make something 🙃
Thank you very much this is what in needed
My advice from personal experience, start a tutorial, quit at half or so when you feel like you know enough, set a mind on a project and try to make it using available docs and help from online forums...
Thank you so so much bro very helpful
I personally always followed tutorials until I had the basics. I also tinkered around with them to understand them better. Once I had the basics I just startet using programming to solve problems I had. If I ran into something I didn't understand I I'd watch a video on how it works and how I can implement it.
Make sure you read the right people's code. I've managed to condense a 200 line script written by someone else into roughly 30 or 40.
In addition to reading other peoples’ code, try looking into the documentation first. The documentation will explain the ins and outs of how to use versions instructions and other peoples’ codes are examples of how it’s used, what went wrong, and how to fix it.
Sometimes just reading the documentation is better than watching a tutorial or looking at examples. If you’re trying to learn a new topic, the documentation is like a free textbook written by the creator on how it works; the syntax, the use cases, how it functions behind the scenes, etc.
So smart... thanks for motivation🙏
👍Thank You! Genius insight. Very practical, very attainable goals! Always super-cool presentations and you are SO smart and business-savvy!
When reading other's code, make sure that you know what the code is for before reading it.