Re[n]: Should I even bother?
Re[n]: Should I even bother?
- Subject: Re[n]: Should I even bother?
- From: Lance Drake <email@hidden>
- Date: Sun, 21 Mar 2004 17:29:50 -0700
With regard the usefulness of writing to these lists - MANY times I
find the answer to my (seemingly) dumb question only a short while
after posting the question. It may be that this is a result of forcing
myself to ask as salient a question as possible which includes the most
pertinent details. The result of this exercise is to (sometimes)
reveal the answer to myself.
At least it seems more like I have done due diligence if I have tried
to solve the problem, written to the list, gotten no response and STILL
not figured it out. All in all, it helps me better gauge just how
capable it is I may be with a particular disciple and - hence - do a
better job in estimating how long things will likely take me to
complete in the future.
Yes, it's humbling to have to admit (to your professional peers) you
are the clueless-wonder - but it's all a relative thing. A year and a
half ago, I wasn't sure how to SPELL Cocoa. Now I wouldn't want to be
developing in anything else. Objective-C could have just as easily
been sanskrit, for all I knew about it. Now, it's my favorite
language. So, what does that say about all the dumb questions I have
posted (and which have gone unanswered) in the intervening time?
As far as ME answering questions posed to the list - here's another
interesting thing. MANY of the people to whom I write with suggestions
for answers to their posted questions do NOT write back - even 5
letters like 'thanx'. It's a little bit of aversion therapy to hear
some fellow's desperate plea for assistance, send him source code with
the solution, and never hear anything back. That's why I answer EVERY
SINGLE LETTER ever sent to me - because you never know who's out there
with the answer that's gonna save you an afternoon of rudderless
fumbling - so you sure as heck don't want to be a rude-dude and not
respond to the folks who are kind enough to take time out of their day
to try to help you.
One last thing - learn how to best construct your question so it's most
likely to get an answer. Look at the list - observe the form and
content of questions that get answered. I don't think there is such a
thing as a question that's 'too hard' - maybe 'too broad' or 'too
vague'. Well, 'nuff jaw-flappin' for one day.
Lance Drake
_______________________________________________
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.