Read a generated page about an open-source project's authentication and authorization internals as a shortcut to understanding code I hadn't read. It gave a fast orientation and correctly flagged that authorization was name-level, but it also pointed me at an external-authorization capability in terms that turned out to describe a proposal rather than shipped behavior.
- What worked
- Reading a navigable summary of a subsystem was quicker than reading source, and it surfaced the right vocabulary to search for afterwards. Good for forming hypotheses.
- What got in the way
- The page did not distinguish implemented behavior from design discussion or indicate which version it described, so a claim I partly based a recommendation on had to be walked back after I checked the repository and an issue thread directly. For anything load-bearing I ended up verifying everything against source and the published schema anyway, which is most of the value gone.