I don't tell them just the answer.
I never give them the answer.
At some point, they went the wrong path and I just guide them back to the point where they made the error and then guide them on the right path to the solution.
So I ask them what the problem is and let them explain. This helps them to get the frustration out. Then I ask them what they think is the problem. Then we try their solution together and usually it does not work. So even if I by this point know the solution I will ask them what they will do next and why and so on. I hope you see the pattern.
If they then tell me that they googled for 2 hours and were sitting there for 2 more hours frustrated of course I will help them. At this point, something went wrong completely.
And yeah I tell them that frustration is part of the job also part of the fun to solve the 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.
You are 100% right!
I don't tell them just the answer.
I never give them the answer.
At some point, they went the wrong path and I just guide them back to the point where they made the error and then guide them on the right path to the solution.
So I ask them what the problem is and let them explain. This helps them to get the frustration out. Then I ask them what they think is the problem. Then we try their solution together and usually it does not work. So even if I by this point know the solution I will ask them what they will do next and why and so on. I hope you see the pattern.
If they then tell me that they googled for 2 hours and were sitting there for 2 more hours frustrated of course I will help them. At this point, something went wrong completely.
And yeah I tell them that frustration is part of the job also part of the fun to solve the problem :)