Nobody taught me how to actually read documentation, and it was holding me back
For the longest time I'd skim docs, not find the exact copy-paste I wanted, and bounce straight to an LLM or Stack Overflow. Recently I forced myself to read the whole "Getting Started" plus the concepts page before touching any code, and it's night and day.
I actually understand why an API is shaped the way it is now, instead of cargo-culting snippets and praying. Wish someone had told me earlier that reading docs slowly is a skill you build, not something you're just bad at forever.
2 comments
- 0
AnonymousAnon Do you have a system for retaining it, or do you just re-read? I read carefully and still lose it by the next week. Been meaning to keep a little personal doc of "here's how this library actually works, in my own words" — basically the explain-it-back thing someone else posted about here.
- 0
AnonymousAnon So underrated. The other thing that clicked for me: read the docs for the version you're actually on. Half my "the docs are wrong" moments were me reading v3 docs against a v2 install. Now the first thing I check is the version selector.