I'm pretty bad at reading documentation when programming. I often find it hard to parse even enough to orient, and steer toward the pages that are relevant to my problem. I'm pretty sure this is my biggest bottleneck as a programmer.
I think that part of this is because reading the documentation for a code base is sometimes an inherently frustrating task.
But I bet there are a few of discrete heuristics that would make this much easier for me.
But I bet there are a few of discrete heuristics that would make this much easier for me.
What do you actually do, at a moment-to-moment level, when you go to read the documentation for some software (or an API, or a library, or whatever) that you're new to?
@threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
