For starters, I think we can utilize the "advocacy" in our job titles :) Meaning looking at what stresses or confuses developers about our products and advocating for a change. From numerous interviews with developers, I know for instance that they often worry about breaking the production environment, often their expectations are set incorrectly, and they ask themselves questions such as "What does this button do?", "What does this method do?", or "Can I go back after I click it/call it?"
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.
For starters, I think we can utilize the "advocacy" in our job titles :) Meaning looking at what stresses or confuses developers about our products and advocating for a change. From numerous interviews with developers, I know for instance that they often worry about breaking the production environment, often their expectations are set incorrectly, and they ask themselves questions such as "What does this button do?", "What does this method do?", or "Can I go back after I click it/call it?"