I agree. Our team gets a lot of value from talking through features before implementing them. Doing this sometimes brings us to the conclusion that we don't really understand the request. Then we have a dialog with the customer to gain more understanding. If we had started coding first, the code would have been thrown away. Or if we had pressed on and finished it without really understanding, the customer's request would be implemented in a way that probably does not solve their underlying problem. It is still wasted work, because the customer will just keep requesting more features to solve the same problem.
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 agree. Our team gets a lot of value from talking through features before implementing them. Doing this sometimes brings us to the conclusion that we don't really understand the request. Then we have a dialog with the customer to gain more understanding. If we had started coding first, the code would have been thrown away. Or if we had pressed on and finished it without really understanding, the customer's request would be implemented in a way that probably does not solve their underlying problem. It is still wasted work, because the customer will just keep requesting more features to solve the same problem.