Is this literature?
That page itself is a lightweight intro but on the left are all the functions and properties available on the Array object, each one is quite detailed but they all have a similar structure. For example:
Gives the order and type of the arguments that must be supplied, what the function returns (produces) and other comments on its behavior.
This is followed by a series of code examples, some of which are trivial but some would be good to memorize - not verbatim but the point of the demostration.
In the old days, documentation was on paper and probably not in your building. I was forced to memorize but, there was a great deal less to know. Modern languages are a different game.
At the moment I’m doing this, each function is a little room or scene. Object.defineProperty is drawn as a fenced yard with the arguments (the required data items) laid out in the yard. I have done a few of these, so far.
An advantage of sketching is that I can keep the papers and refresh easily.
Various other details are then added to this scene. The sketching causes a lot of engagement. The properties themselves are a linked list. Like wise the list of major Objects would be a linked list.
What I am aiming for a ‘tree’ structure, a linked list of linked lists that themselves hold little palaces or scenes. From my software background this seems logical, but I am not sure if it’s appropriate for the brain.
This is a big undertaking. I don’t want to invest a lot of work only to have to restructure later. I would appreciate advice or comments, thank you.