How i learned it! | just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏 Here is how i learn these days ->| take the course ->write codes in intellij Idea/Android Studio -> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn -> when i get better i watch another tuto Any improvements please!Thank you for your time fam
thats exactly what i was thinking while listening to the video. it's overwhelming trying to remember everything but i just look up exactly what i need at any given moment and have much better results that way
"I was writing down, highlighting, and memorizing recipes. But, I just wasn't getting better at cooking. Then, everything changed once I started cooking!"
I reduced my notes to a "What have I learned?" list that I keep handy with every project. It will sometimes contain fundamental concepts if I didn't know them already, and sometimes only items specific to that project.
This is a great tip I have a slight tweak tho, instead of copy-pasting, I type it down myself. You will probably notice something you didn't notice before if you type every character yourself
honestly this is something I've been telling so many people for such a long time it's not about memorizing how something works, it's about understanding how it works, you just gotta "connect the dots" for your brain
@xtrappin | just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏 Here is how i learn these days ->| take the course ->write codes in intellij Idea/Android Studio -> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn -> when i get better i watch another tuto Any improvements please!Thank you
That means you either made notes of unimportant things or you never put yourself in a position where you would need the information again. Or maybe didn't make it easy enough to review the notes so that you'd rather search it up again.
Hello @shadowslayer2248 | just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏 Here is how i learn these days ->| take the course ->write codes in intellij Idea/Android Studio -> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn -> when i get better i watch another tuto Any improvements please!Thank you
In my opinion taking notes is good if you need to keep an eye of something important when you're doing a big project, like remembering how a part of someone's else code work. Or like creating a visual and more concrete graphic rf something, that you could not try to change in a big code project without doing damage to all the logic behind. But a the end of the day active code is one of the best option to understand how something works
bro this short video really changed my mind im stressing myself about taking notes digitally or physically and i now i know what to do, great video straight to the point
The notes I do take, I take with obsidian. Can screenshot and drag and drop charts in, can write sample code with double tab. Markdown support. It is 20x faster than hand writing/drawing stuff. Not to mention the link system to navigate is handy af. Free to use, would recommend. For pure learning though, yeah. Actually coding is the way. Can watch tutorials all day and still not grasp jack.
I think it is still a good idea to take note. I take notes in order to revisit it at a latter date in case I forget something. But I mainly take notes to use as way to memorize things and realize what I still don't understand. My way of studying is as follow: - Watch a tutorial session, try to apply what you have just learnt into coding (just mess around with it until you understand). - Try to teach yourself again about the concept you have just learned. - Take a note, try to write it as simple as possible in your own understanding. - If you don't understand something, experiment with the code again, try to reach your own conclusions before watch the video again. - Rinse and repeat.
It's useful to take notes to refresh on stuff you'll eventually forget and need to refresh on. Applying niche concepts without note taking is suboptimal.
It's still vital to be able to know when and how to take notes as a SWE. When story-pointing or dissecting a ticket, it's use case-specific. What also works for one does not always work for another
I agree and disagree at the same time. If notes are just for "memorizing" then yea, it's worthless. But I code AND take notes (or save some unedited scripts into a note) so I can use search. The same way people make videos, blogs or conference presentations, writing something down in a way that that you can explain easily to somebody - it can be very useful. It elevates how much you know because you have to dig deeper in order to be able to put the words down. For me this is "deliberate practice" feedback loop that drives learning and this way motivation is still high after so many years. I can track my progress and I don't have a problem that you mention about not knowing how to code
Currently I’m learning python and I totally agree that you should test out code whenever you are learning a new concept but it is also nice to keep track of what you learn so you can look back to it. I would take little snippets of past code I’ve done so I don’t forget simple obvious things like how to set up a try… except function. Lol
I prefer having some sort of notes that contain code snippets, especially in my early days, where having the intuition written down step by step below a code snippet was reassuring to me so that I could visit it back and be sure that i could understand it with significantly less effort. Although I didn't refer to it extensively, it gave me the fearless attitude i needed to move ahead on to more advanced topics without worrying about refining my memory of its prerequisite concepts. I did default to code first before taking down the notes with the code snippet in it
@jswlprtk | just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏 Here is how i learn these days ->| take the course ->write codes in intellij Idea/Android Studio -> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn -> when i get better i watch another tuto Any improvements please!Thank you
To be fair, I think it depends where you are in your programming learning path. Early on, in AP CS and some of my undergrad CS courses, I would take copious (sometimes silly) notes on things like you mentioned-what X means in Y language or how it's used. This was mainly as a form of self-teaching by trying to internalize those concepts and understand them as someone who was only just beginning to study CS. Now that I've been working as a dev for ~4 years, I learn mostly by reading and coding/trial and error.
Of course you need to apply what you've learnt so far but also you need to take notes for remembering them in the far or near future. There is nothing wrong with doing both of them which is superior imho.
@NecdetSanli | just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏 Here is how i learn these days ->| take the course ->write codes in intellij Idea/Android Studio -> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn -> when i get better i watch another tuto Any improvements please!Thank you
@@nevz9851 The problem is your solution may be different from the example in the docs, so keeping notes or a spreadsheet of some obscure thing may make you say "I remember having to deal with this before, lemme check my notes"
@@meltygear5955 right on point tbh. I swear if i had to lookup docs each time instead of notes, id spend 5x time just googling what the thing meant again xD
Taking notes in my opinion is more taking care about future you than trying to somehow memorize things. When I want to remember how to correctly write http interceptor, I likely will use my brief explanation that I took from docs than try to scan enormous docs page. You can't remember all the things you've learned as some of them are not being used so often.
Taking notes is also an active process, IF you're making up the words yourself. Don't just copy definitions, reverse engineer and play with the concepts and write down your findings and how you got there. To me it really helps solidify my understanding of things, and since I write it down, even if I forgot, I can always check and redo the process to get to the same understanding. Yes you 100% need to default to code, but not writing it down is just asking to forget it in the future. Our memories are waaay too unreliable. But I only do this for concepts and finnicky stuff that doesn't make sense first glance, so maybe I'm missing the point of the video altogether.
10 หลายเดือนก่อน +1
I love your concept. Actually it shouldn't has worked due to youtube's algo and monetization stuffa however it worked and the channel is growing day by day. ❤
I just think of everything as a switch. A switch is on off, and everything is just a more complex version of that You basically are making switch boxes, where when you flip one switch, it shuts a series of others off and or on. Coding is just the interface for making that happen.
This is good advice for a beginner whose aim is to learn "coding". But after a certain experience level, coding turns into unskilled labour (something for ChatGPT to do), while design and algorithms become the difficult things to do well. Another thing I noticed is that when I was younger, I wanted to code everything from scratch. This is still true for some cases, but nowadays I mostly want to see if I can do do something that a big library, say library 'X', does by chaining together small open-source tools or libraries. My thought process is that "yes, I know I can code the whole thing myself, but I'm sure there exist lightweight tools that can help me with certain bits. Besides, my two-day hack would not be as feature-rich as the tool that someone took months or years to build. Why not use these small tools to get stuff done, and in the process recreate the functionality of library 'X'".
absolutely True it just like learning blender courses but when you finish it you can't draw any human or other model you need to create it play with program and try to draw anything to know how blender work and start your journey thank you for tell this information for beginner it is absolutely useful for who want to start coding right now
personally i prefer taking notes, but my strategy is not copy pasting documentation i dont try to memorize them as well. for my note i write my own understanding, and my experimental codes, i learn smtn i try to grasp it, and i write my own version with my own words then i make examples, i tweak around the code, then i paste it to my note. That is the best way to learn for me
Sometime ago I felt compelled to take notes for everything new or interesting I learned, fearing that otherwise I would lose that knowledge after some time. Sometimes it's enough to rely solely on the textbook or the language reference.
Hello @0rmai | just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏 Here is how i learn these days ->| take the course ->write codes in intellij Idea/Android Studio -> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn -> when i get better i watch another tuto Any improvements please!Thank you
When learning taking notes doesn't really help, since you need to understand and learn how it works rather than just the theory of it. Though, when you are actually working on something and you encounter bugs, take notes, it'll help you if you encounter the same thing in the future.
I was torn on deciding on whether I should write notes or not, eventually didn't write any. I was not good at writing notes myself and relied on someone else's notes *documentation*. I used devdocs a lot and kept it on the side of my screen whenever I was doing anything programming related, it was probably the best decision in my life it taught me how to read through and grok documentations and yes even the bad ones, it definitely is a skill that I'm fortunate to have trained since the beginning. The mindset I had was "I can just google it" and you know what? It worked great! And also memorizing/understanding syntax/concept is just a side effect of applying and building things. Something to add is I do take notes whenever I build something but that's more on planning stuff but when I'm learning? Nope.
wow. I hate notes but was still doing it, maybe the cost to learn programming. But you showed me a better alternative which i already like. thanks mate
@jabuci I feel like doing both is too time consuming. I think as you learn actively, you tend to remember stuff better and for longer whilst saving lots of time.
@@DroidX143 Doing both is time consuming, but I believe a balance of both is needed. Rather than just typing up wiki articles in obsidian, try taking notes to really grasp a concept. Take networking, for instance. We often use HTTP in code, but digging into how data flows on the internet and how the web actually works can help you connect the dots and learn more effectively. :0
came to a similar conclusion as you, but i still take notes, but it's stuff that I came up with after learning a concept or a great piece of code that someone else had written.
I was watching other videos on note taking and some of them feel like just gimmicks and you managed to debunk them in 1 minute. I will take notes with my code editor open.
Personally i like to take notes on basic syntax and concepts to use as my own reference for later. Usually end up looking back on the notes once or twice before i dont need them anymore. Its also nice to write code on pen and paper for first few examples. But yeah definitely good to keep it to a minimum.
As a developer, you just need to know where things are when need be. That's it. I did the same in the past, and I would get frustrated if I didn't remember the things I'd learnt. It's always a good idea to read as much documentation as you possibly can, though.
I like to take notes. Not notes on the theorethic shit that none uses, but after I am done with a coding session, I like to revise the new things i have implemented and write them down for me. This said, im a beginner but coding is fun!
Only if you understand why. If you just "accept" what the code is in the tutorial or proompt from chadgpt then you are just memorizing and couple of days later that piece of information is gone in the wind.
Hello @BurninVinyl | just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏 Here is how i learn these days ->| take the course ->write codes in intellij Idea/Android Studio -> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn -> when i get better i watch another tuto Any improvements please!Thank you
If you ever need to learn something, you need three things - a runtime/compiler able to handle the code - an editor able to handle the runtime - a debugger or REPL that interfaces with the executable/runtime Everything else is completely secondary to those three things. Don't take notes. Write code. Break whatever you were learning.
Remember, do whatever works best for you. When I was learning, I would often take many notes by hand and learn the skill by thinking about it really hard. I would participate in active learning during note review and note taking. The only time I used programming was for the specific programming language syntax and implementation. I agree with the premise of this video, and its a good suggestion for many, but remember that one size doesn't fit all when it comes to learning.
I would partake in active learning by just thinking about the concept really hard, and asking "why" until I understood or had a question with no answer, to which I would research my question (google, textbook), or ask a question to my professor - if you are learning via class.
My process nowadays is: Have docs open Have editor open Keep testing things from doc in a test project (a playground of sorts) Take concepts I've learned from experimenting and use them for my project now that I know how they work Not a one-size-fits-all, but for many projects this is how it goes for me. It's akin to taking notes but is a much more hands-on approach.
For me it is about, writing notes, or references, to what is what, so that I can go back to it and look it up and try to use it again. More of a reminder than anything else. Basically active learning notes, not just passive copying tons of information that is out there. That way when I am coding, I go HEY I remember this was a thing what was it called? go back to my second brain and find the references, and there you go.
It makes sense to not make notes but instead document your journey when building something with the framework/language you're learning. Because the next time you read your code, it is most likely that you don't remember what it does.
I was always an applied learner never a passive learner and ig this is very common among our generation ! A big part of our education system is smh based on passive learning techniques which is sad cuz bcoz of that many brilliant brains kinda distance themselves from the quality sorted stuff they could've gotten to learn only if the method of teaching was different. 😢
Exactly. I took some notes while i was learning a programming language and today I look at them and say myself aggg,, i took these notes while i do these every single day now?!!
I would say DO write notes for OpenGL or whatever complex like that, if you have to write a lot of code to even see if thing works, do write down some abstract notes/bulletpoints.
taking notes at the start can be helpful... but after about a month of trying to make things from scratch... you find you no longer need the notes, you just u look up an old project, then use a search engine to see if there's a better way
looking at some of my old notes... I see a lot of stuff I know to be wrong now, or simply a way a beginner would do it. Which is ok when learning... Its nice to look back at old me note taking. Its a great way to remember what it was like to be at the very beginning. Something I often forget when trying to explain things to ppl who don't know what syntax is, or that they don't need a crazy editor to start making things
I don't really understand the struggle people have, especially the so called "tutorial hell" or something. Am I the only person that can just watch a tutorial and be able to do it straight away? Not perfectly of course, but there is no "hell" or anything, it is just seemless *trivial* practice with no problems diving into code whatsoever. And that was pretty much since the very start for me. But I guess I got even better after time, since I can watch/read tutorials in full 2x speed about an entirely new concept or a language and then go do the same no problem. I only have the 2 keys(rules?): 1. If you watch something and think of a quick and dirty idea of something, why not go try it (usually not more than 10-30 minutes for me). I usually have a side project open that is fully new and creative, that needs this tutorial so I can make it work. I don't watch a tutorial just for the sake of "vaguely learning the language/technology for no tangible reason" but for the practical purpose of actually doing the side project I had an idea beforehand. 2. No need to be too specific/detailed about something. You are an engineer, not a scientist, so you need to be practical before all. If it works, it's good enough. "Building a strong foundation" ground up approach imo is just a *silly unrealistic ideal* some people have that sounds good on paper, but fails miserably in reality, because just doing something practically, without putting much thought into it, will give *much* better results for less time investment in practice (counter intuitive, right). You can always brush up the basics after acquiring the practical skills. It is the path of least resistance that will give the best results in my (and most people's) experience.
Yeah, also people seem to forget that most frameworks and libraries and languages mostly have the same concepts applied to them. If you know what reactive programming is about, it is not that hard to switch from vue to learning react for example. Like it is basically the same, just with different syntax and sugar.
I tend to write notes when I say "Huh I didn't know you could do that with X". One example is you can "store" a simple conditional into a variable at least with JS. Ex:[ const canDrive= age >= 18 && license;]. Also I was gonna say It's important to write notes one example is React but honestly I try not to write A LOT because it's a lot of info and keep it brief so I don't get overloaded of words
*the problem* : i am a student who is learning 1 or 2 new languages each semester so yes when i am learning i understand and remember everything but when i looked back , i have forgotten basic syntax , wtf is this code , why did i do this ( i guess commenting would have helped but we were never told to comment i guess because we were just learning basic things but in my opinion writing why you did it would be very helpful for your future help and you dont have to relearn from scratch again
I mean... you can do both. you can take notes of the things you discover when you experiment. And taking notes is a form of active learning if you write the notes with your own words instead of copy pasting exactly what you read
i just note some useful tips for some problem when learning programming or watching tutorials. Then when i face a problem, my brain was like, oh i have noted that or faced that before so that i can visit that note:D
also the only reason notes are actually good for things like math is because that literally is how you actively practice those subjects. you just work equations
I didnt take many notes at all in over 10 years of programming (most of them as a hobby) But lately, i began taking more notes... Except the notes are just code. Kind of like "___ by example", except i make the examples
It's suited for beginners, freshers...If you keep this up for long you will not get a good job or any job....as you will become a guy who knows bunch of languages and frameworks and not well experienced in any of them....Tech hoping is fun but it's dangerous....You can't keep exploring forever.....In the begining it's fun but if you don't settle down and be really good at something soon you will end up jobless.... Explore but not for too long...Get really good at something and expand in that domain...
I never really took notes with the intention of memorizing so to speak. I do it so I wouldn't have to spend hours just searching on the Internet just to find that one thing that could have been avoided if I just take the damned note. Opening it up, searching for the keyword and boom come up.
![[DRIP] ‘BILLIONAIRE’ PREVIEW](http://i.ytimg.com/vi/m0eXQD0gIeE/mqdefault.jpg)
that's why making projects to learn a new language or concept is the best method to learn, in my opinion
How i learned it!
| just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏
Here is how i learn these days
->| take the course
->write codes in intellij Idea/Android Studio
-> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn
-> when i get better i watch another tuto
Any improvements please!Thank you for your time fam
Hy, I learn something new everyday by programming and pushing my limits
Not good for interview preparation 😂
@@jdn9717 it’s better to learn in general, you have to build features once you get that job
Hey i just have a doubt that if i dont now the syntax of a programming language ho am i going to start working on a project.?
For fundamentals it's ok, but for learning a new language or framework... Active learning is what we need
I agree I guess. Cause I tried taking notes vs not.. and I learned better in taking notes.
thats exactly what i was thinking while listening to the video. it's overwhelming trying to remember everything but i just look up exactly what i need at any given moment and have much better results that way
@@rtyprty pretty sure that’s called passive learning though
"I was writing down, highlighting, and memorizing recipes. But, I just wasn't getting better at cooking. Then, everything changed once I started cooking!"
"they never let me cook("
I reduced my notes to a "What have I learned?" list that I keep handy with every project. It will sometimes contain fundamental concepts if I didn't know them already, and sometimes only items specific to that project.
This is a great tip
I have a slight tweak tho, instead of copy-pasting, I type it down myself. You will probably notice something you didn't notice before if you type every character yourself
honestly this is something I've been telling so many people for such a long time
it's not about memorizing how something works, it's about understanding how it works, you just gotta "connect the dots" for your brain
@xtrappin
| just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏
Here is how i learn these days
->| take the course
->write codes in intellij Idea/Android Studio
-> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn
-> when i get better i watch another tuto
Any improvements please!Thank you
You should not tell others it will just increase the competition
@@nishantsingh7235 just another indian chithole advice
I would always take notes to never look at them again.
That means you either made notes of unimportant things or you never put yourself in a position where you would need the information again. Or maybe didn't make it easy enough to review the notes so that you'd rather search it up again.
This one-minute video can transform how you learn drastically and in a fundamental way. A big thank you to you for this.
1 minute videos that give advice that can save you hours!! bigbox never disappoints!
Hello @shadowslayer2248
| just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏
Here is how i learn these days
->| take the course
->write codes in intellij Idea/Android Studio
-> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn
-> when i get better i watch another tuto
Any improvements please!Thank you
In my opinion taking notes is good if you need to keep an eye of something important when you're doing a big project, like remembering how a part of someone's else code work. Or like creating a visual and more concrete graphic rf something, that you could not try to change in a big code project without doing damage to all the logic behind. But a the end of the day active code is one of the best option to understand how something works
bro this short video really changed my mind im stressing myself about taking notes digitally or physically and i now i know what to do, great video straight to the point
The notes I do take, I take with obsidian. Can screenshot and drag and drop charts in, can write sample code with double tab. Markdown support. It is 20x faster than hand writing/drawing stuff. Not to mention the link system to navigate is handy af. Free to use, would recommend.
For pure learning though, yeah. Actually coding is the way. Can watch tutorials all day and still not grasp jack.
This guy is what every programming content creator should look up to. No bs, no waste of time, no bluh bluh bluh, just straight up to the point.
I think it is still a good idea to take note.
I take notes in order to revisit it at a latter date in case I forget something. But I mainly take notes to use as way to memorize things and realize what I still don't understand.
My way of studying is as follow:
- Watch a tutorial session, try to apply what you have just learnt into coding (just mess around with it until you understand).
- Try to teach yourself again about the concept you have just learned.
- Take a note, try to write it as simple as possible in your own understanding.
- If you don't understand something, experiment with the code again, try to reach your own conclusions before watch the video again.
- Rinse and repeat.
Great tip for beginners. As a strong middle, I find notes very helpful for both work and personal stuff
Thank you so much! I made the same mistake and got frustrated and disappointed. I will definitely apply active learning.
It's useful to take notes to refresh on stuff you'll eventually forget and need to refresh on. Applying niche concepts without note taking is suboptimal.
I've never had this problem because I learned to create through creating.
It's still vital to be able to know when and how to take notes as a SWE. When story-pointing or dissecting a ticket, it's use case-specific. What also works for one does not always work for another
I agree and disagree at the same time. If notes are just for "memorizing" then yea, it's worthless. But I code AND take notes (or save some unedited scripts into a note) so I can use search.
The same way people make videos, blogs or conference presentations, writing something down in a way that that you can explain easily to somebody - it can be very useful. It elevates how much you know because you have to dig deeper in order to be able to put the words down. For me this is "deliberate practice" feedback loop that drives learning and this way motivation is still high after so many years. I can track my progress and I don't have a problem that you mention about not knowing how to code
Couldn't agree more. I felt something was off when he said he took notes to "memorize".
Currently I’m learning python and I totally agree that you should test out code whenever you are learning a new concept but it is also nice to keep track of what you learn so you can look back to it. I would take little snippets of past code I’ve done so I don’t forget simple obvious things like how to set up a try… except function. Lol
Your channel is a gem man, thank you for these.
Thanks for the video. Saved me a bunch of time. Tons of notes already, thinking to myself, "theres no way I'm going to remember all of this lol".
I prefer having some sort of notes that contain code snippets, especially in my early days, where having the intuition written down step by step below a code snippet was reassuring to me so that I could visit it back and be sure that i could understand it with significantly less effort. Although I didn't refer to it extensively, it gave me the fearless attitude i needed to move ahead on to more advanced topics without worrying about refining my memory of its prerequisite concepts.
I did default to code first before taking down the notes with the code snippet in it
@jswlprtk
| just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏
Here is how i learn these days
->| take the course
->write codes in intellij Idea/Android Studio
-> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn
-> when i get better i watch another tuto
Any improvements please!Thank you
That's also how I learned to code, and this method has given me very satisfactory results.
To be fair, I think it depends where you are in your programming learning path. Early on, in AP CS and some of my undergrad CS courses, I would take copious (sometimes silly) notes on things like you mentioned-what X means in Y language or how it's used. This was mainly as a form of self-teaching by trying to internalize those concepts and understand them as someone who was only just beginning to study CS. Now that I've been working as a dev for ~4 years, I learn mostly by reading and coding/trial and error.
Oh lord I thank you for showin me this video for changing my perspective, ur content is gold bro👌👌.
Of course you need to apply what you've learnt so far but also you need to take notes for remembering them in the far or near future. There is nothing wrong with doing both of them which is superior imho.
@NecdetSanli
| just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏
Here is how i learn these days
->| take the course
->write codes in intellij Idea/Android Studio
-> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn
-> when i get better i watch another tuto
Any improvements please!Thank you
Is the docs good enough for notes?
@@nevz9851 i use google docs and they help me
@@nevz9851 The problem is your solution may be different from the example in the docs, so keeping notes or a spreadsheet of some obscure thing may make you say "I remember having to deal with this before, lemme check my notes"
@@meltygear5955 right on point tbh. I swear if i had to lookup docs each time instead of notes, id spend 5x time just googling what the thing meant again xD
Taking notes in my opinion is more taking care about future you than trying to somehow memorize things. When I want to remember how to correctly write http interceptor, I likely will use my brief explanation that I took from docs than try to scan enormous docs page.
You can't remember all the things you've learned as some of them are not being used so often.
Taking notes is also an active process, IF you're making up the words yourself.
Don't just copy definitions, reverse engineer and play with the concepts and write down your findings and how you got there.
To me it really helps solidify my understanding of things, and since I write it down, even if I forgot, I can always check and redo the process to get to the same understanding.
Yes you 100% need to default to code, but not writing it down is just asking to forget it in the future. Our memories are waaay too unreliable.
But I only do this for concepts and finnicky stuff that doesn't make sense first glance, so maybe I'm missing the point of the video altogether.
I love your concept. Actually it shouldn't has worked due to youtube's algo and monetization stuffa however it worked and the channel is growing day by day. ❤
I just think of everything as a switch. A switch is on off, and everything is just a more complex version of that
You basically are making switch boxes, where when you flip one switch, it shuts a series of others off and or on. Coding is just the interface for making that happen.
This is good advice for a beginner whose aim is to learn "coding". But after a certain experience level, coding turns into unskilled labour (something for ChatGPT to do), while design and algorithms become the difficult things to do well.
Another thing I noticed is that when I was younger, I wanted to code everything from scratch. This is still true for some cases, but nowadays I mostly want to see if I can do do something that a big library, say library 'X', does by chaining together small open-source tools or libraries. My thought process is that "yes, I know I can code the whole thing myself, but I'm sure there exist lightweight tools that can help me with certain bits. Besides, my two-day hack would not be as feature-rich as the tool that someone took months or years to build. Why not use these small tools to get stuff done, and in the process recreate the functionality of library 'X'".
absolutely True it just like learning blender courses but when you finish it you can't draw any human or other model you need to create it play with program and try to draw anything to know how blender work and start your journey
thank you for tell this information for beginner it is absolutely useful for who want to start coding right now
thanks man, this is what i needed to hear today, keep it up the good content
personally i prefer taking notes, but my strategy is not copy pasting documentation i dont try to memorize them as well. for my note i write my own understanding, and my experimental codes, i learn smtn i try to grasp it, and i write my own version with my own words then i make examples, i tweak around the code, then i paste it to my note. That is the best way to learn for me
Sometime ago I felt compelled to take notes for everything new or interesting I learned, fearing that otherwise I would lose that knowledge after some time. Sometimes it's enough to rely solely on the textbook or the language reference.
Hello @0rmai
| just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏
Here is how i learn these days
->| take the course
->write codes in intellij Idea/Android Studio
-> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn
-> when i get better i watch another tuto
Any improvements please!Thank you
Very useful suggestion! Also cure my anxiety for never finished some famous c++ book
the last remark really strikes me.. the best way to learn and remeber what you learn is by getting your hands drity.
recommend taking notes and practicing examples in an IDE so you can run the example code while taking notes by creating comments
When learning taking notes doesn't really help, since you need to understand and learn how it works rather than just the theory of it.
Though, when you are actually working on something and you encounter bugs, take notes, it'll help you if you encounter the same thing in the future.
I was torn on deciding on whether I should write notes or not, eventually didn't write any. I was not good at writing notes myself and relied on someone else's notes *documentation*. I used devdocs a lot and kept it on the side of my screen whenever I was doing anything programming related, it was probably the best decision in my life it taught me how to read through and grok documentations and yes even the bad ones, it definitely is a skill that I'm fortunate to have trained since the beginning.
The mindset I had was "I can just google it" and you know what? It worked great! And also memorizing/understanding syntax/concept is just a side effect of applying and building things.
Something to add is I do take notes whenever I build something but that's more on planning stuff but when I'm learning? Nope.
sometimes you just need a youtuber with 100k+ subscribers to make it sink in
I like this videos, short and straight to the point
wow. I hate notes but was still doing it, maybe the cost to learn programming. But you showed me a better alternative which i already like. thanks mate
You need to do both! Try everything AND take notes. If you just try everything without notes, you forget those things.
@jabuci I feel like doing both is too time consuming. I think as you learn actively, you tend to remember stuff better and for longer whilst saving lots of time.
@@DroidX143 Doing both is time consuming, but I believe a balance of both is needed. Rather than just typing up wiki articles in obsidian, try taking notes to really grasp a concept. Take networking, for instance. We often use HTTP in code, but digging into how data flows on the internet and how the web actually works can help you connect the dots and learn more effectively. :0
But notes aren't memory.
If you're going to write it down then write it down in your IDE.
came to a similar conclusion as you, but i still take notes, but it's stuff that I came up with after learning a concept or a great piece of code that someone else had written.
You got the best swe videos in the game! Thanks bro
I was watching other videos on note taking and some of them feel like just gimmicks and you managed to debunk them in 1 minute.
I will take notes with my code editor open.
I love your videos, man.
This is why our daddy ThePrimeagen always tells us to learn how to type fast
me: currently taking programming notes for class
youtube recommendations:
Turn off notifications
Your vídeos are helping me a lot, thx brother
Personally i like to take notes on basic syntax and concepts to use as my own reference for later. Usually end up looking back on the notes once or twice before i dont need them anymore. Its also nice to write code on pen and paper for first few examples. But yeah definitely good to keep it to a minimum.
i love you . short and concise
I'm not sure if this is the same as taking notes, but practicing your technical writing is a soft skill that you need in the workforce
As a developer, you just need to know where things are when need be. That's it. I did the same in the past, and I would get frustrated if I didn't remember the things I'd learnt. It's always a good idea to read as much documentation as you possibly can, though.
I like to take notes. Not notes on the theorethic shit that none uses, but after I am done with a coding session, I like to revise the new things i have implemented and write them down for me.
This said, im a beginner but coding is fun!
This is really good. Thank you.
love your content. thank you
Appreciate your advise, BigBox :)
That's why I'm writing code in my anki cards. GOTTEM!
A big
❤❤❤❤Thank Youuu❤❤❤❤
for making these videos!
I still remember having a notebook full of css property name and their definitions lol
Thanks man. All That I Need.
Only if you understand why. If you just "accept" what the code is in the tutorial or proompt from chadgpt then you are just memorizing and couple of days later that piece of information is gone in the wind.
Hello @BurninVinyl
| just bought a freecodecamp course on kotlin mobile dev, i forget a lot, but i started practicing more when he recommended it 🙏
Here is how i learn these days
->| take the course
->write codes in intellij Idea/Android Studio
-> summarize the course and create myself practical exercise using 1st principles that will require me to use all the concept i learn
-> when i get better i watch another tuto
Any improvements please!Thank you
If you ever need to learn something, you need three things
- a runtime/compiler able to handle the code
- an editor able to handle the runtime
- a debugger or REPL that interfaces with the executable/runtime
Everything else is completely secondary to those three things. Don't take notes. Write code. Break whatever you were learning.
Remember, do whatever works best for you. When I was learning, I would often take many notes by hand and learn the skill by thinking about it really hard. I would participate in active learning during note review and note taking. The only time I used programming was for the specific programming language syntax and implementation. I agree with the premise of this video, and its a good suggestion for many, but remember that one size doesn't fit all when it comes to learning.
I would partake in active learning by just thinking about the concept really hard, and asking "why" until I understood or had a question with no answer, to which I would research my question (google, textbook), or ask a question to my professor - if you are learning via class.
Thank you, I wrote this down
My process nowadays is:
Have docs open
Have editor open
Keep testing things from doc in a test project (a playground of sorts)
Take concepts I've learned from experimenting and use them for my project now that I know how they work
Not a one-size-fits-all, but for many projects this is how it goes for me. It's akin to taking notes but is a much more hands-on approach.
I’d tried taking notes in college at first since I was nervous asking my teacher to stop so could catch up typing along
For me it is about, writing notes, or references, to what is what, so that I can go back to it and look it up and try to use it again.
More of a reminder than anything else. Basically active learning notes, not just passive copying tons of information that is out there.
That way when I am coding, I go HEY I remember this was a thing what was it called? go back to my second brain and find the references, and there you go.
It makes sense to not make notes but instead document your journey when building something with the framework/language you're learning.
Because the next time you read your code, it is most likely that you don't remember what it does.
I was always an applied learner never a passive learner and ig this is very common among our generation ! A big part of our education system is smh based on passive learning techniques which is sad cuz bcoz of that many brilliant brains kinda distance themselves from the quality sorted stuff they could've gotten to learn only if the method of teaching was different. 😢
Amo esse cara!
Exactly. I took some notes while i was learning a programming language and today I look at them and say myself aggg,, i took these notes while i do these every single day now?!!
I would say DO write notes for OpenGL or whatever complex like that, if you have to write a lot of code to even see if thing works, do write down some abstract notes/bulletpoints.
I love this man
great video as always
Outstanding 🙌🏻🙌🏻🙌🏻
taking notes at the start can be helpful...
but after about a month of trying to make things from scratch...
you find you no longer need the notes, you just u look up an old project, then use a search engine to see if there's a better way
Was thinking of this while scrolling and found this vid 😂
I'm doing both, first i take notes, then I immediately code.
Programming notes are good(if you actually revisit them)
looking at some of my old notes...
I see a lot of stuff I know to be wrong now, or simply a way a beginner would do it. Which is ok when learning...
Its nice to look back at old me note taking. Its a great way to remember what it was like to be at the very beginning.
Something I often forget when trying to explain things to ppl who don't know what syntax is, or that they don't need a crazy editor to start making things
@@Mel-mu8ox agreed 🤝
I don't really understand the struggle people have, especially the so called "tutorial hell" or something. Am I the only person that can just watch a tutorial and be able to do it straight away? Not perfectly of course, but there is no "hell" or anything, it is just seemless *trivial* practice with no problems diving into code whatsoever. And that was pretty much since the very start for me. But I guess I got even better after time, since I can watch/read tutorials in full 2x speed about an entirely new concept or a language and then go do the same no problem.
I only have the 2 keys(rules?):
1. If you watch something and think of a quick and dirty idea of something, why not go try it (usually not more than 10-30 minutes for me). I usually have a side project open that is fully new and creative, that needs this tutorial so I can make it work. I don't watch a tutorial just for the sake of "vaguely learning the language/technology for no tangible reason" but for the practical purpose of actually doing the side project I had an idea beforehand.
2. No need to be too specific/detailed about something. You are an engineer, not a scientist, so you need to be practical before all. If it works, it's good enough. "Building a strong foundation" ground up approach imo is just a *silly unrealistic ideal* some people have that sounds good on paper, but fails miserably in reality, because just doing something practically, without putting much thought into it, will give *much* better results for less time investment in practice (counter intuitive, right). You can always brush up the basics after acquiring the practical skills. It is the path of least resistance that will give the best results in my (and most people's) experience.
Yeah, also people seem to forget that most frameworks and libraries and languages mostly have the same concepts applied to them. If you know what reactive programming is about, it is not that hard to switch from vue to learning react for example. Like it is basically the same, just with different syntax and sugar.
Currently learning Flutter and this hits too close to home lmao
I tend to write notes when I say "Huh I didn't know you could do that with X". One example is you can "store" a simple conditional into a variable at least with JS.
Ex:[ const canDrive= age >= 18 && license;].
Also I was gonna say It's important to write notes one example is React but honestly I try not to write A LOT because it's a lot of info and keep it brief so I don't get overloaded of words
Anki is pretty incredible.
*the problem* : i am a student who is learning 1 or 2 new languages each semester so yes when i am learning i understand and remember everything but when i looked back , i have forgotten basic syntax , wtf is this code , why did i do this ( i guess commenting would have helped but we were never told to comment i guess because we were just learning basic things but in my opinion writing why you did it would be very helpful for your future help and you dont have to relearn from scratch again
The documentation are the only notes you need.
I mean... you can do both. you can take notes of the things you discover when you experiment. And taking notes is a form of active learning if you write the notes with your own words instead of copy pasting exactly what you read
i feel personally called out lol
I felt that also
Yep. That's the best way... With chatgpt by our side...👌
i just note some useful tips for some problem when learning programming or watching tutorials. Then when i face a problem, my brain was like, oh i have noted that or faced that before so that i can visit that note:D
Programming is like math, practicing is the best way to learn it
also the only reason notes are actually good for things like math is because that literally is how you actively practice those subjects. you just work equations
I didnt take many notes at all in over 10 years of programming (most of them as a hobby)
But lately, i began taking more notes... Except the notes are just code. Kind of like "___ by example", except i make the examples
It's suited for beginners, freshers...If you keep this up for long you will not get a good job or any job....as you will become a guy who knows bunch of languages and frameworks and not well experienced in any of them....Tech hoping is fun but it's dangerous....You can't keep exploring forever.....In the begining it's fun but if you don't settle down and be really good at something soon you will end up jobless....
Explore but not for too long...Get really good at something and expand in that domain...
You guys were taking notes?
I never really took notes with the intention of memorizing so to speak. I do it so I wouldn't have to spend hours just searching on the Internet just to find that one thing that could have been avoided if I just take the damned note. Opening it up, searching for the keyword and boom come up.