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.

I am not you. Please keep that in mind. 2 Comments More | Login | Reply /

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

  • Well said! (Score:1)

    by soulchild (8747) on 2008.08.29 11:41 (#64661)
    There's this zero-tolerance attitude many coders exhibit which only allows perfect code which might work in the lab, but as soon as you throw it into production environments problems surface. And often nobody's willing to change the implementation because it would involve a workaround which might break the perfect design. Telling somebody that the database you've been using for the last 10 years is the culprit and you should switch to another one (just to make this one module work correctly) is just plain ridiculous! I have the feeling that the Perl community could learn a thing or two from the PHP folks which seem to be better nowadays in just getting the job done.

    • Funny you should mention PHP because I was thinking about a blog post defending PHP programmers. At the end of the day, those people who rip on PHP (and its programmers), are often bad about asking why it's so successful. Many people rail against the issues with PHP, but I doubt that most, if any, of them have produced perfect code. Hell, we're Perl programmers. We might defend lack of method and subroutine signatures because "that method is deep in the system and can't get bad arguments", but that's a

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