Re: Give a fish or teach to fish?

I share kyle's view on this.

One point to bear in mind is that the answers are useful to others besides the poster. For example, a short snippet that succinctly makes a point can help add to the wisdom of the monastery regardless of whether you think the poster is a good cause.

<whinge>If you have an aversion to perceived homework questions please pass on by. Ease up on the lectures. :-)

Comment on Re: Give a fish or teach to fish?

Replies are listed 'Best First'.
Re^2: Give a fish or teach to fish? by jnbek (Scribe) on Apr 01, 2008 at 07:56 UTC
I agree with this fully. Sometimes I find myself here after google searching an issue or a better way to accomplish a task I am working on. I generally won't ask something until I've searched this issue and either not found a reasonable solution or just plain don't understand a solution presented. Resources like the monastery are priceless sources for information. For me it is obvious when a poster has done his homework before posting the question. It can be helpful to point to a path that may be applicable, one that the poster had not thought of before, but sometimes, a couple of lines of code as an example can say more than 100 lines of documentation. And as noted, it can help others in the future, who may just simply stumble into it using google, such as myself.	[reply]

Replies are listed 'Best First'.

Re^2: Give a fish or teach to fish?
by jnbek (Scribe) on Apr 01, 2008 at 07:56 UTC

I agree with this fully. Sometimes I find myself here after google searching an issue or a better way to accomplish a task I am working on. I generally won't ask something until I've searched this issue and either not found a reasonable solution or just plain don't understand a solution presented. Resources like the monastery are priceless sources for information. For me it is obvious when a poster has done his homework before posting the question. It can be helpful to point to a path that may be applicable, one that the poster had not thought of before, but sometimes, a couple of lines of code as an example can say more than 100 lines of documentation. And as noted, it can help others in the future, who may just simply stumble into it using google, such as myself.

[reply]