Norm Radder wrote:... I continually see responses to posted code that says: "Here is the problem" or "change this to make it work" without any explanation of how the poster of that response found the problem so that the OP could find the next problem himself
I'm quite sorry you feel that way. Maybe you can point out a particular post that absolutely needed explanation and the poster didn't provide one ?
Norm Radder wrote:... but had one of the senior staff back it out in frustration over biting my tongue vs wacking some poster for just posting the solution without any explanation.
Norm Radder wrote:Here's what happens. An OP posts code with problems. I spend time finding the problems and work on ways to lead the OP to finding them.
Then some hotshot comes along and gives the OP the answer. The time I have spent is wasted. The OP is no longer interested in how to find the solution because he has it.
It often seems that there is a race on this forum for who can find and post the fix first.
paul wheaton wrote:I feel like this is a group of people that wish to deeply understand what "good" means to them. To be able to be the superstar engineer because of an understanding of how to write magnificent code. Code that is lean and easy to understand.
Norm Radder wrote:Then some hotshot comes along and gives the OP the answer. The time I have spent is wasted. The OP is no longer interested in how to find the solution because he has it.
I agree with Norm on that point. If you think the OP is nearly there, all the work is undone if somebody posts a complete solution (and you can't delete it). I prefer to leave at least twenty‑four hours before posting a solution, or post it ten minutes after hand‑in time.
Norm Radder wrote:. . . Then some hotshot comes along and gives the OP the answer. . . .