Ah, that is different then yes. I think another comment alluded to it but much documentation these days is just simple reference material which without context

Ah, that is different then yes. I think another comment alluded to it but much documentation these days is just simple reference material which without context is only so useful for deep understanding. I fully agree with understanding the perspective of the people making the thing, knowing the what isn't always as useful as knowing the why. I speak a lot about being idiomatic, which is to say developing in a way that is sympathetic to the system and its existing approaches. That takes understanding the why more than the what. I am reminded of the Honda motorcycle maintenance manuals. They are like being face to face with the engineers who designed the bike, reading that back to back would give you that deeper understanding of the system I think. That's my pet peeve with auto-generated docs, they don't actually help much. I can see the function for myself, I don't need to be told it exists, I need to know why!