Taking Notes is a WASTE OF TIME When You're Learning To Code! DO THIS INSTEAD!

Zero To Mastery - Complete React Developer in 2022:

Receive 10% off at Zero To Mastery by using FRIENDS10 coupon code at checkout!

Here are some direct affiliate links for the gear that I use in my home office and gear that I use to make my YouTube videos

_____YouTube Gear_____

______Home Office_____

[vickys]

1. Don't Bother taking notes for the first 2 months rather focus on the course or tutorial.
2. After learning the basics, start building projects and comment on every single line.
3. Write documentation, basically explaining the purpose of your project (watch other tutorials on how to write documentation in VScode).
4. Only take notes of those concepts which you use very often and find it difficult to remember them.
Thank you, Dorian it really helped a lot :)

[viper]

I'm an Unreal Engine game dev working on a large project, and documentation and commenting is SOOOO important, it's everything. All code is at its core is a communication tool, so one of the biggest parts of being a good developer is communicating as clearly as possible.

[Jamal-pdtl]

You are absolutely right. Programming is similar to mathematics you write down important formullas but at the end it's all about practicing and solving more and more problems.

[dawn-of-newday]

I did a course on Udemy, I created my notes in a document. Since I forgot stuff and tricks. I have to again go through the video. Now using a document my speed to catch up is instant. It is real gold. I don't mind the time it takes. It is worth the effort when u take a break for a month and forgot what that class or syntax do.

[TricoliciSerghei]

My 2 cents as a senior developer. This is a good starting point for juniors, but as time goes on (maybe 1-2 years or more) you will understand that it's better to write clean-code and name identifiers correctly (this comes with years of experience), and you won't need comments, they will slow you down because they need to be maintained just as your code does.
Quality code are the best "comments" you can possibly write.

[bruno]

I’m glad I caught this video. I have been self teaching myself and have been taking notes on a 5 subject notebook. Half of the notebook is filled and I’m not even halfway through my course! I will definitely take your advice and comment more on my code.

[-ASTROMAGIC]

Tips broken down into steps:

1. Comment on your code, build this habit.
-The amount of comments at the start should be commented to explain what they're doing. As you get better, this will be needed less and less. Eventually you will only need to comment on important steps (this will be intuitive).


2. Write documentation.
-Every project you start should start with a readme file. Learn basic markdown, many markdown cheat sheets often. You'll build the habit of starting with readme files. See how other apps and technologies write their own documentation. Expand and develop this skill as you learn. Potential employers will look at github documentation will value this. A nice portfolio will have applications with explained comments and documentation.

[JDMorris]

For me the taking of notes reinforces the learning more than reviewing the notes later

[meceka]

Your videos getting better and better every day.

[dacritter]

While learning, I absolutely agree. The problem with comments in the workplace is that -- code gets updated but comments rarely do so you wind up working on code where the available comments are no longer applicable. Companies prefer code that is self explanatory through descriptive class/method/variable/etc names which act as comments as you're reading the actual code. That is a GREAT habit to form while you are learning that transfers very well to the workplace.

[fnregistration]

I had a high school programming teacher back in the day who really emphasized comments. Especially early on, he would give us assignments requiring us to write nothing but comments or pseudocode first and submit it, then go back and write the actual code. I think it helped me a lot.

[christinefredricksen]

When I started I took a lot of notes and have cut way back as I feel more comfortable working with the editors, languages and all of that. I use index cards to jot down quick reminders and notes as I am learning something and just keep them nearby, and as soon I don't need them anymore I toss them. I really like the idea of commenting your code and making documentation for your project, good thinking to build those habits and get the benefits of note taking all in one. I am going to make the effort to do this from now on. Thank you so much for the video!

[victorekea]

When I saw this video, I thought the title was clickbait, but since I take a ton of notes, I decide to check it out. And I have to say that this is really good advice. I realized taking notes has made me spend twice as much time to learn something because I have to write it down in human language, which is hard. It helps you retain more information but you spend too much time in the process. The worse part about it all is I never go back to my notes. The comments I make on each code line ends up becoming a better reference point. Absolutely sound advice! Thanks for sharing, Dorian. Subscribed.

[cristopherarecheguillen]

Im starting to think that you are actually reading my mind dude. 😭 Great video!

[Nigromancy]

Thanks dude I was getting overwhelmed by my notes! Just going to go through the courses and trust my muscles from now on!

[--__--]

I learned the essence of how to properly write your code and commenting when I first watched CS50. They'll grade your code based on its functionality and its design and then I also learned that the most efficient way for me to write my code is creating the pseudocode first. Understand how you want your program to run, then for each line of the pseudocode, write the actual code which will make everything else really easy.

[itsjustme]

I cant imagine how many careers this guy has like doctors, teachers, plumbers, step father...and now he is a coder dang

[GyngerNynja]

Thanks for that, I started thinking way more critically about my code when I started using annotations, this is a really good tip.

[dariusseals]

Great vid! Two benefits I gained from taking notes. They helped reinforce things as I learned, and I was also able to look over them later on in my career to measure my progress and understanding because what didn’t make sense before made sense. I was able to confirm what I understood by looking through my notes and explaining the concepts to myself and others, whereas I could not do that early on.

[F-fp]

One for the algorithm.
Your videos are getting really good man. Keep it up!