@b0rk Do not read what the documentation is saying, but try to infer things about whoever was writing the documentation. E.g. the total lack of statements on some topic usually mean that either this topic is unimportant for some obvious reason, or it has totally escaped the authors' minds. Similarly, often one can extrapolate precision levels of one part of the documentation onto others (which makes looking at documentation for a part you know very well useful).

If you lack some sort of fundamental understanding about general design of the thing (e.g. its data model, which things are mutable, what identifiers of remote objects are assumed to persistently point at the "same" object, etc.) then often looking for the answer to that question in the documentation of fundamentals is less expedient than picking one feature that (or its usage) will have to depend on that property and doing a depth-first search on reference documentation for that feature/API call/...