We should be collecting data! But who, what, when, where, why and how? 🤔

[howagain]

I'm reading articles like this one https://www.forbes.com/sites/kylewong/2014/11/12/startups-are-a-marathon-not-a-sprint-run-at-your-own-pace/?sh=6ae037cb6c10 and think that it's great advice. I'll work to incorporate it in the repo now. However, I also feel that we need to have his advice contribute to a larger meta analysis. I feel like we could use some advice from a meta-analysis author to see how we could construct such a thing.

What data would we need to collect? How much work would it be? Can we get any tips for how it should be done?

For example, could we have GPT's that assess measures like "Was this advice followed?", and we could start tabulating the few factors that make an outside impact (Pareto principle).

So in the long run I see something like a table with various principles like "worked with a community", "focused on work life balance", "relevant experience", "digital ads", "size of team", "top 3 principles"

If we get a good spreadsheet and data collection process going, we could eventually do something like state of js survey. Could send a message to every one of registered startups and see what their preferences were. Could even call or send follow up emails automatically to get better results from founders.

Also we should have a registry of startups. Maybe that can be the first step to becoming a community member. Only anonymous users can submit a PR to have their name added. Their account is associated with their startup. A bot could even automatically approve them at scale. It's a good incentive to becoming a coder and being comfortable with the PR process. A video guide would be good for that.

[howagain]

I'm thinking that building some sort of "success" tracking is the most important. I think that maybe a simple "did you make more money this sprint than last?"