You'll be surprised how often this practice will lead you to an answer without ever pressing send.
I've been at my job for almost 2 years, and I still draft out a question to my boss 2-3 times a week, and I only really send it once every couple weeks. I just type out my question, then I start adding the context he will need, and what I've tried, and what some certain values are. By the time I get all that and organize it into a coherent question, I usually end up figuring it out myself. If I don't, then my boss has a much easier time helping me out than if I had said, "Hey, this isn't working."
I feel it is very similar to a "rubber duck" approach, with the added benefits of communicating with another person, but without the drawback of potentially "wasting" the other person's time if you figure out the answer as you explain the question.
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've been at my job for almost 2 years, and I still draft out a question to my boss 2-3 times a week, and I only really send it once every couple weeks. I just type out my question, then I start adding the context he will need, and what I've tried, and what some certain values are. By the time I get all that and organize it into a coherent question, I usually end up figuring it out myself. If I don't, then my boss has a much easier time helping me out than if I had said, "Hey, this isn't working."
I feel it is very similar to a "rubber duck" approach, with the added benefits of communicating with another person, but without the drawback of potentially "wasting" the other person's time if you figure out the answer as you explain the question.