on-line courses typically list resources (used, additional, related)
looking at project documentation for things on a site such as thingiverse / instructables of references to other things aka what did to be able to enable project to be done. hopefully not a wrote own os.
I feel like this begins to blur the lines between discovery tool and resource to be discovered.
The idea of instructable /project blog is interesting as a discovery tool though. It makes me wonder if the act of creating one is also a discovery tool, similar to a lecture pad or research notebook. It's kind of like, active vs passive discovery, kind of like I wrote about in the other comment, where one might have to develop a certain "method" using various tools to create a reliable + repeatable process. Once I start searching for an answer or move towards a goal, by keeping a log of the steps, the "discovery" of something "novel" might be just where the knowledge gaps are - knowing what I don't know. But like asking questions of other people, this isn't automated, and requires skill/practice/time.
even a simplified version of snarfing bibliograph data for setting up web "automata" munging with available tools, such as https://ahrefs.com/blog/link-building-tools/ , requires some skill/practice/time before "return key" worthy.
Comments
somewhat topic/project specific: makezine / instructables
personal web page(s) of project/thesis author(s)
on-line courses typically list resources (used, additional, related)
looking at project documentation for things on a site such as thingiverse / instructables of references to other things aka what did to be able to enable project to be done. hopefully not a wrote own os.
I feel like this begins to blur the lines between discovery tool and resource to be discovered.
The idea of instructable /project blog is interesting as a discovery tool though. It makes me wonder if the act of creating one is also a discovery tool, similar to a lecture pad or research notebook. It's kind of like, active vs passive discovery, kind of like I wrote about in the other comment, where one might have to develop a certain "method" using various tools to create a reliable + repeatable process. Once I start searching for an answer or move towards a goal, by keeping a log of the steps, the "discovery" of something "novel" might be just where the knowledge gaps are - knowing what I don't know. But like asking questions of other people, this isn't automated, and requires skill/practice/time.
even a simplified version of snarfing bibliograph data for setting up web "automata" munging with available tools, such as https://ahrefs.com/blog/link-building-tools/ , requires some skill/practice/time before "return key" worthy.
Ah I need to learn more about this.