I get this a lot while reading about something new which I have heard might solve my problem, or while better trying to understand a system already in place. The documentation begins with a comforting high level description that is vague enough to sound like it might fit my use case, but then abruptly transitions into a table of contents listing the minutiae of interfaces, API calls, system components, without giving…
— an emoji-laden intro employing borderline UwU-speak
— jumping into API reference immediately after
— the reference is auto-generated with half of it being stubs, implying you should throw it away and just simply read the code