T
Twisted
Yes. My impression is that some of the most knowledgeable people are
the quickest to snap at minor transgressions.
Which is seriously bad, since it discourages newbies and too much of
that kills the whole field. I FINALLY found a spot on the 'net where
someone else says something I keep saying regarding patronizing
responses, particularly "RTFM" and "Google is your friend", and
something I keep saying regarding searching being easy when you know
the answer but not so often when you only know the question:
http://digg.com/linux_unix/How_dumb_can_GNU_Linux_users_be/#c4028847
This arose in connection to a discussion of things discouraging
adoption of GNU/Linux on the desktop, but it seems just as applicable
here (or in comp.text.tex)...
Even you, who sympathize with the n00bs, makes the mistake of referring
to these things as "transgressions", as if they should nonetheless
somehow be avoided, and are minor crimes not worthy of prosecuting
rather than not crimes at all.
Anyway, the tendency of a subset of knowledgeable people to snap at
n00bs is a problem far more serious than n00bs not knowing stuff,
especially since the latter is only addressable by educating them, and
trying to do so in a way that puts them off even trying, discourages
them from entering some field entirely, or forces them onto an
entrenched defensive is doomed to failure. Of course, it depends on
whether you consider the problem to be "n00bs not knowing stuff" or
"n00bs not knowing stuff AND POSTING TO MY NEWSGROUP!!"; the latter is
"solved" by driving them all away, but the latter is not the real
problem. In fact, the real problem is people with the "MY NEWSGROUP!!"
proprietary attitude and anyone being hostile or condescending to
n00bs.
Given the above, I think it behooves us all to call the "smarmy
know-it-all" subset on their attitude and tone whenever it shows, far
from criticizing the lone voice to (thus far) do so for getting uppity!
(And see above for evidence that I may not, in fact, *be* a "lone
voice" anymore. Now there are at least two...)
I'm usually willing to put up with less than perfect behavior from someone who has expert
knowledge and is willing to share it -- I think it's a fair tradeoff.
If that behavior drives away the lifeblood of progress, the n00bs who
must someday replace them in big enough numbers "or else", then it has
crossed the line. Same if it forces n00bs to entrench a (possibly)
misguided approach or position just to save face, since then their
efforts to educate are actually actively hindering that cause. And
*anyone* whose primary motive is ego masturbation can go stuff
themselves of course.
Could be. Again speaking for myself, if I get an answer that seems
incomplete or doesn't work "out of the box", I'm apt to try first to
figure out for myself why it doesn't work, and then ask a follow-up
question if I can't figure it out.
Fine, but the experts should:
* Not expect you to succeed at adapting it to make it work; if you had
sufficient knowledge to do that, you probably had sufficient knowledge
to solve your original problem anyway, so you would probably not have
asked the original question to begin with. That you did is strong
evidence that anything low-level or technical that needs fixing in
their solution is going to be beyond you. Minor tweaks, like
substituting your name for "insert your name here" or changing
something from "center" to "right-justified" as a matter of taste or
something are another matter of course.
* Not snap at you if you do, as is likely, complain that it didn't work
out of the box and ask for something that will.
* Seriously contemplate, if this happens a lot, if there may not be
deep architectural flaws in need of addressing that make problem
solutions brittle and prone to fail when copied and pasted. Things like
lack of namespacing, lack of encapsulation or implementation/interface
separation, bogus/missing abstraction more generally ...
I suspect that on the whole the
folks in c.t.t. are more apt than the folks here (in c.l.j.p.) to
expect that the people being helped are willing to fill in some
gaps themselves.
Their error is in assuming that they are able to, and in assuming that
everyone posting is a techie when many are just writers. (Usually
technical writers, but knowledge of physics (say) doesn't maye you any
more likely than a lay person, on average, to be able to fix a TeX
problem yourself.
In c.l.j.p we have a somewhat different situation: people posting
questions here are ipso facto programmers, with a presumed
greater-than-layperson knowledge of software development and related
concepts. That lets the experts make more assumptions about the state
of knowledge of the questioner. I'm guessing the other difference of
substantial effect may be that Java has a lot of abstraction and
namespacing to make cut-and-paste code much less likely to fail, that
Java things are specifically designed to be unlikely to fail in obscure
ways instead of failing in obvious ways or working (e.g. "fast-fail"
use of ConcurrentModificationException, specifically done to reduce
obscure failures involving collections and concurrency), and of course
that when pasted code does fail it's much closer to certain that the
paster has the knowledge to diagnose and fix the problem himself to
adapt it to his own needs.