Great that you have work like the arxiv paper! You could even explicitly ask for feedback on that work
Make it easy for people to understand your work: Try and answer questions like “Why did I do this? What did I learn and/or what update did I make? What is my theory of change?”, and so on...
Make it easy for people to engage with your work: Display it prominently, tweet about it, write a blogpost on lesswrong about it. Polish and publish the code base (see an example here), and so on...
Everyone has their own style of building relationships. I think a powerful way to do so is to try and add value to others: can you summarise/discuss their work in public, or give them feedback, or extend it in an interesting way? Are there volunteer or part-time opportunities that you can help out with? Can you identify issues in their codebases and improve them?
Quick thoughts:
Great that you have work like the arxiv paper! You could even explicitly ask for feedback on that work
Make it easy for people to understand your work: Try and answer questions like “Why did I do this? What did I learn and/or what update did I make? What is my theory of change?”, and so on...
Make it easy for people to engage with your work: Display it prominently, tweet about it, write a blogpost on lesswrong about it. Polish and publish the code base (see an example here), and so on...
Everyone has their own style of building relationships. I think a powerful way to do so is to try and add value to others: can you summarise/discuss their work in public, or give them feedback, or extend it in an interesting way? Are there volunteer or part-time opportunities that you can help out with? Can you identify issues in their codebases and improve them?