Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chromatic (983)

chromatic
  (email not shown publicly)
http://wgz.org/chromatic/

Blog Information [technorati.com] Profile for chr0matic [technorati.com]

Journal of chromatic (983)

Sunday January 19, 2003
05:21 PM

Frustration

[ #10075 ]

What is it in the Perl community that makes presumably otherwise reasonable people unable to address high-level ideas, instead attacking minutiae?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I asked myself a similar question recently. Probably in similar circumstances ?
  • This problem has nothing to do with Perl. You will find the same thing in almost every community. That is, we do not get to blame Perl, which is a good thing. :)

    I do not know the situation that frustrates you, but Kurt Starsinic (or maybe Ziggy) says frequently "they're building a bike shed" [freebsd.org], meaning that people who do not see the big picture (and not always for lack of intelligence) focus on the things they can easily grasp---the minutia.
  • I wish that I really knew why, but I have noticed that many coders tend to try code before thinking about something. I first noticed this on Slashdot, and have since come to expect it from all new/young/inexperienced coders. It may be because they first learned to do something before learning the best way to do anything.

    "Wow, I can make the text on this web page blink." They don't know better, and they don't think about other ways to do it. They don't see how irritating it is to try reading an entire p

    • Hands-on experience can be VERY good. I learned Perl from the book 'Learning Perl' and by coding.

      I have made many mistakes and I still am, but at the same time my success rate has and is increasing.

      So do not underestimate hands-on experience
      • I understand hands-on experience, and I don't mean to underestimate it, but it is no substitute for theoretical knowledge.

        I'm a Mechanical Engineer by training, and an Aeronautical Structures Engineer by trade - there are many experienced people (20+ years on the job) who don't have degrees, but can do most of the day-to-day work of an engineer. But you'll get a blank look if you ask them about the stress distribution in the part. Stress distribution and stress paths are critical to evaluating the safety

  • It is quite a statement, could you give an example of what you mean?
  • People in the Perl Community tend to be very intelligent and often fall into what Edward de Bono (in de Bono's Thinking Course 1985 - Facts on File Publications - ISBN 0-8160-1380-2 (hc), 0-8160-1895-2 (pb)) calls the Intelligence Trap.

    I won't go into depth about the Intelligence Trap, but one problem with intelligent people that the author notes is:

    • The critical use of intelligence is always more immediately satisfying than the constructive use. To prove someone else wrong gives you instant achievement a