This is a great idea! As an MVP we could well make a link to a recommended Stampy path (this is an available feature on Stampy already, you can copy the URL at any point to send people to your exact position), once we have content. I’d imagine the most high demand ones would be:
What are the basics of AI safety?
I’m not convinced, is this actually a thing?
How do I help?
What is the field and ecosystem?
Do you have any other suggestions?
And having a website which lists these paths, then enriches them, would be awesome. Stampy’s content is available via a public facing API, and one other team is already interested in using us as a backend. I’d be keen for future projects to also use Stampy’s wiki as a backend for anything which can be framed as a question/answer pair, to increase content reusability and save on duplication of effort, but more frontends could be great!
I think that list covers the top priorities I can think of. I really loved the Embedded Agency illustrated guide (though to be honest it still leads to brain implosions and giving up for most people I’ve sent it to). I’d love to see more areas made more approachable that way.
Good point on avoiding duplication of effort.. I suppose most courses would correspond to a series of nodes in the wiki graph, but the course would want slightly different writing for flow between points, and maybe extended metaphors or related images.
I guess the size of typical Stampy cards has a lot to do with how much that kind of additional layering would be needed. Smaller cards are more reusable but may take more effort in gluing together cohesively.
Maybe it’d be beneficial to try to outline topics worth covering, kind of like a curriculum and course outlines. That might help learn things like how often the nodes form long chains or are densely linked.
This is a great idea! As an MVP we could well make a link to a recommended Stampy path (this is an available feature on Stampy already, you can copy the URL at any point to send people to your exact position), once we have content. I’d imagine the most high demand ones would be:
What are the basics of AI safety?
I’m not convinced, is this actually a thing?
How do I help?
What is the field and ecosystem?
Do you have any other suggestions?
And having a website which lists these paths, then enriches them, would be awesome. Stampy’s content is available via a public facing API, and one other team is already interested in using us as a backend. I’d be keen for future projects to also use Stampy’s wiki as a backend for anything which can be framed as a question/answer pair, to increase content reusability and save on duplication of effort, but more frontends could be great!
I think that list covers the top priorities I can think of. I really loved the Embedded Agency illustrated guide (though to be honest it still leads to brain implosions and giving up for most people I’ve sent it to). I’d love to see more areas made more approachable that way.
Good point on avoiding duplication of effort.. I suppose most courses would correspond to a series of nodes in the wiki graph, but the course would want slightly different writing for flow between points, and maybe extended metaphors or related images.
I guess the size of typical Stampy cards has a lot to do with how much that kind of additional layering would be needed. Smaller cards are more reusable but may take more effort in gluing together cohesively.
Maybe it’d be beneficial to try to outline topics worth covering, kind of like a curriculum and course outlines. That might help learn things like how often the nodes form long chains or are densely linked.