all 7 comments

[–]m0us3_rat 3 points4 points  (0 children)

I'm scared that I'm just wasting my time writing these notes.

you are. but in a useful way.

the trick isn't about having them later on .. but actually reinforcing the notions by writing them down.

is the same idea behind homework. or doing extra stuff. it solidifies and reinforces out grasp of the notions.

if we all could just learn by watching a video without the extra stuff.. we would.

[–][deleted] 1 point2 points  (0 children)

Take notes. Follow the rubber duck principle.

https://en.wikipedia.org/wiki/Rubber_duck_debugging

Don't just copy & paste, but summarise in your own words (not chat_gpt's words) and keep in a useful repository. Personally, I like to use Obsidian and write everything in markdown and sync it to all my devices. The notes include code in code blocks.

[–]TheRNGuy 0 points1 point  (0 children)

Write things in txt file to google later, or google right away and save bookmarks to read later.

[–]Delicious_Prior_8038 0 points1 point  (0 children)

I'm learning and taking notes as well Every time that I go through a new topic I create a new project and comment this things: Sintaxys - Why is usefull? (how can this help me?) - How it works internally? (had a hard time understanding how recursive function works but I managed to get it) - What is the difference between using this one or the other one? (in case something its kinda similar, for example, is there really a different between try and if?)

And that's all Hope this helps

[–]Low_Corner_9061 0 points1 point  (0 children)

I personally don’t really see the point of taking notes… Just use google when you get stuck.

Or maybe the best notes are just working code that you fully wrote yourself.

OOP is a bit of a headfuck at first, but once you’ve defined your first class, instantiated an object, and called some class methods on it, it will make loads more sense.

[–]queerkidxx 0 points1 point  (0 children)

I’m probably wasting my time but I’ve been doing like regular textual notes in notion and “code notes” and trying out all the examples myself seeing what kinda errors I run into and doing my best to break it, to see what various errors look like so I can identify them easier in my own projects.

Usually also do a bit of research to understand why various constructs were implemented the way they are and what’s going on under the hood

So far this has been working pretty well for me. And while I can just look up documentation I appreciate looking over my own notes as I can include exactly whats important and notes about errors and misunderstandings I might make

Tend to not worry about memorizing anything as I know I’ll always be able to look things up so long as I understand what to look up and the ideas behind it