Graduate student in statistics at Duke University. Former dev.to employee. I like to blog about data science on my Medium publication, perplex.city, and on dev.to
Alaina -- pumped to see you posting on dev.to! Many moons ago you wrote a very nice tweet about my Medium blog, perplex.city, which I now sometimes cross-post here now that our whole team works on dev.to, where you now post, where...etc. etc. Small world!
Anyway, at the moment I'm but a data scientist in training, so I can't speak with too much expertise about engineering teams, but I have watched a handful of people come aboard dev.to and Texts.com (dev.to's corporate ancestor), and I think the most successful ones were the ones that asked Ben the most questions and weren't afraid to suggest new things. So I would say identifying someone on your team who seems open to "mentorhood" and bothering that person a lot is a good idea.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Alaina -- pumped to see you posting on dev.to! Many moons ago you wrote a very nice tweet about my Medium blog, perplex.city, which I now sometimes cross-post here now that our whole team works on dev.to, where you now post, where...etc. etc. Small world!
Anyway, at the moment I'm but a data scientist in training, so I can't speak with too much expertise about engineering teams, but I have watched a handful of people come aboard dev.to and Texts.com (dev.to's corporate ancestor), and I think the most successful ones were the ones that asked Ben the most questions and weren't afraid to suggest new things. So I would say identifying someone on your team who seems open to "mentorhood" and bothering that person a lot is a good idea.