Re: Flame retardant
Re: Flame retardant
- Subject: Re: Flame retardant
- From: Chuq Von Rospach <email@hidden>
- Date: Thu, 23 May 2002 18:55:57 -0700
On 5/23/02 5:05 PM, "Roy Lovejoy" <email@hidden> wrote:
>
> Look at the documentation for NSString, specifically the "cString" method. In
>
> the future, please consult the documentation before posting questions on the
>
> list.
>
>
IMHO, even that's not so GOOD.
>
>
The person asked an honest question.. they didn't ask to be lectured..
Yes, he did. Because he was looking for an answer to a question. That is,
pretty much by definition, a lecture. And unlike some answers, this one may
be short, but it at least gives them a place to start. If they'd already
looked at that, they should have told us, so we didn't waste time assuming
they handn't and wasted a round of postings.
>
Perhaps, they are at a trade show and don't have access to any docs,
Perhaps they are -- and if so, they should tell us. That way, we know it's
an unusual case and can deal with it as such, and not just someone who is
expecing us to do their homework for them...
See, the "newbies" shouldn't create such assumptions, because it's in these
assumptions conflicts arise. But when they happen, we shouldn't assume the
worst case ("what if they were trying to fix a bug because if it's not fixed
in ten minutes, the terrorists will shoot them?"), but a typical case. And
by doing so, both sides can help train each other towards a more effective
discussion.
>
Unless the person is a chronic pest who sees a mailing list as their personal
>
'outside developer', why not just ANSWER the question..
Because after the 100th time you've answered the same question, it gets
pretty darn tired. If you don't believe me, wander over to usenet, head into
rec.arts.sf.written, and ask "hey, has anyone here heard of an author named
heinlein?" -- if you survive, you'll understand why people get tired of
constantly answering the same thing.
But that's why I sugggest if you're tired of answering the questions, don't
answer it. Silence is better than anger, because it allows others to fill
the void, and in a group like this, likely someone will. Nobody should try
to (or feel they have to) fill the entire void of unanswered questions. It
really is a group project. But at the same time, new users need to get in
the habit of trying first and asking second, not coming here first -- and I
think it's appropriate to educate them to that expecation in a professional
manner. I think what Charles did here does that. It's team building.
What we're getting into is an issue of whether you give someone a fish, or
teach them to fish. Everyone is much better off if people are taught to
fish, but it takes more work and energy -- htrowing fish to make them shut
up is a lot easier -- but you know what? I think that attitude is best left
to training seals, not cocoa programmers...
>
Many times, due to the dearth/organization of Apple's documentation, it's hard
>
to know where the 'TFM' is before one can 'R' it..
That's why the best answer in many cases is not the answer, but a pointer to
WHERE TO LOOK. Because otherwise, how will they ever learn how ot find stuff
in the documentation?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.