Open jkerak opened 4 years ago
Added a simple use case diagram to show the scope of what I'm thinking for a "version 0" prototype of the survey. I'm thinking of just picking one each of a couple unique "types" of survey questions..
As reference, here are the results of the two surveys we've sent out in the past:
https://twitter.com/codebuddiesmeet/status/1136851599043600388
Let's create an (automated) survey of the codebuddies community.
Some initial thoughts on insights we might want to gather
See what languages/frameworks people use
see where in the world people are from
see what people think of codebuddies
what ide/text editors do people love/hate
please add ideas
how do we ask the right questions?
how often do we ask?
slack? email?
get insights on changes of the community over time (which begs, where do we store results between survey instances?)