either [1] user test my DB on you (you play with it while I watch) or have you [2] beta test the description
Either sounds interesting, though setting up [1] requires time coordination (or specific tools). If you’re interested in that, send me a private message.
Some thoughts beforehand (since this could be a general problem, and I’m interested in how my perspective might change as a result of such a process***):
Possible issues with ‘communicating in a different medium’*, and how they might be fixed are:
0) They don’t understand the medium.
(This seems ruled out by other people who have used Roam not understanding other people’s Roam documents (although how widespread this is, isn’t clear). Perhaps Roam’s tech support (if they have it) will have or eventually obtain the most experience here—helping people with their documents, understanding more of the tools, and possibly how Roam is programmed. The metaphor of “different languages” doesn’t seem apt here—it seems to be Roam users who share a language, but use it differently that aren’t understanding.)
1) People can’t see their way around it—it’s like an extension of someone else’s mind, and it doesn’t connect to other people. Understanding might be built by watching it grow from scratch or be worked with by someone who understands it might help.** (The alternative is multiple people working together on a document, at the time, and then them trying to explain it to other people afterward, or each other if changes are made independently later on.)
2) Understanding it requires asking questions. (Is this a one time cost or continuous one?)
3) Motivation—people enjoy the way words (and thoughts) are “normally” arranged. People are okay with nested comments on sites like Reddit because the structure is that of a conversation, and that’s something people engage with.
*or “communicating a different medium”
**This could be done via youtube videos or livestreaming. (With or without audio.) Seeing a document be built, and how, might give insight.
***Though this might be uninteresting to other people.
Either sounds interesting, though setting up [1] requires time coordination (or specific tools). If you’re interested in that, send me a private message.
Some thoughts beforehand (since this could be a general problem, and I’m interested in how my perspective might change as a result of such a process***):
Possible issues with ‘communicating in a different medium’*, and how they might be fixed are:
0) They don’t understand the medium.
(This seems ruled out by other people who have used Roam not understanding other people’s Roam documents (although how widespread this is, isn’t clear). Perhaps Roam’s tech support (if they have it) will have or eventually obtain the most experience here—helping people with their documents, understanding more of the tools, and possibly how Roam is programmed. The metaphor of “different languages” doesn’t seem apt here—it seems to be Roam users who share a language, but use it differently that aren’t understanding.)
1) People can’t see their way around it—it’s like an extension of someone else’s mind, and it doesn’t connect to other people. Understanding might be built by watching it grow from scratch or be worked with by someone who understands it might help.** (The alternative is multiple people working together on a document, at the time, and then them trying to explain it to other people afterward, or each other if changes are made independently later on.)
2) Understanding it requires asking questions. (Is this a one time cost or continuous one?)
3) Motivation—people enjoy the way words (and thoughts) are “normally” arranged. People are okay with nested comments on sites like Reddit because the structure is that of a conversation, and that’s something people engage with.
*or “communicating a different medium”
**This could be done via youtube videos or livestreaming. (With or without audio.) Seeing a document be built, and how, might give insight.
***Though this might be uninteresting to other people.