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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

See Spot Program! 1 Comment More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Spot, on (Score:1)

    by bluto (225) on 2006.02.15 11:39 (#46157)
    Why optimize for people inexperienced with the language, platform, or problem domain when you could optimize for fixing the problem?

    I tend to agree. For maintainance reasons I can see helping people ignorant of the platform, or perhaps even the language in some rare cases, but definitely not the problem domain. It's not worth writing kernel code so that programming newbies can understand. You may be able to write much of it so that *kernel* newbies could pick it up and maintain it. Even then, some problems exist (e.g. code requiring complex multilevel locking semantics) that even if the code is clean and well designed, it will still require a programmer to come up to the understanding level of the code.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.