I think this also applies to asking questions as well. If you're working on a new feature, but don't fully understand the requirements then you should definitely be asking questions instead of making assumptions.
If you find yourself in a situation like this, try to think out as many questions as you can and compile them into one email or list. Take some time to compile them before approaching the person(s). That way both your time and the person(s) answering the questions is used efficiently and you'll have a nice list of Q and A's to refer to.
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.
I think this also applies to asking questions as well. If you're working on a new feature, but don't fully understand the requirements then you should definitely be asking questions instead of making assumptions.
If you find yourself in a situation like this, try to think out as many questions as you can and compile them into one email or list. Take some time to compile them before approaching the person(s). That way both your time and the person(s) answering the questions is used efficiently and you'll have a nice list of Q and A's to refer to.