yes, i do agree, i jumped on one extreme though it does have grounds.
what about a happy median, ,.... i noticed that questions like these cause 4
or so (+/-) responces come back to this question all saying why not to do
it, that is good information but its only that. its easy enough to say to
not just through a snippet and let them use it, but the other responces
were only information. i think all "tips" should be included in solutions
to problems (snippets if you will). this way the person knows how to go
about what he wants to do but he also gets the information. not,... just a
snippet, ,... but also not just "you shouldn't do that".
-----Original Message-----
From: Brian Mathis <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, January 06, 2000 10:43 AM
Subject: Re: Ending an application
>As developers, it is our responsibility to make sure people are informed
>about things. Simply answering a question with "here's how to do it", and
>leaving out all the other info that goes along with it is worse than not
>answering the question at all. As a community, we all have a stake in it
>when someone does something that is "wrong", as far as guidelines go,
>because once that thing is in place, it will be very hard to change it.
>
>You can give a man a fish, and he can eat for a day. You teach him how to
>fish, and he can eat for a lifetime. The same applies here. Teaching
>people about how and why things are the way they are is infinitely more
>valuable than just giving them a code snippet that does what they want.
>
>--
>Brian Mathis
>Direct Edge
>http://www.directedge.com
>
>
