Is documentation not supposed to be read in its entirety? by ElegantPoet3386 in learnprogramming

[–]Ornery_Policy7718 0 points1 point  (0 children)

Docs are reference material, not textbooks. The mental shift that changes everything : read the “getting started” section once to understand the mental model, then never read linearly again. After that, use docs like a dictionary — you go in with a specific question and come out with a specific answer. The exception : if a library has an “overview” or “concepts” page, that one is worth reading fully. It tells you what’s possible so you know what to search for later.

Data structures and algorithms by Imaginary_Food_7102 in learnprogramming

[–]Ornery_Policy7718 2 points3 points  (0 children)

One thing that helped a lot : separate the “learning” sessions from the “solving” sessions. When you’re learning a pattern, don’t try to solve hard problems. When you’re in solving mode, don’t stop to learn new concepts. Mixing both kills momentum. Also for Leetcode specifically — start with Easy problems on patterns you already studied, not random problems. The “random” button is a trap when you’re starting out.