Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • "If it's stupid, and it works, it's not stupid."


    • Hoo boy! I do not subscribe to that as I have done things that "work" but even I admit that the solution was "stupid".
      • But what is "stupid"? I think programmers have an all-too-common tendency to worry about the "right" way of doing things from a programming point of view, and ignoring the business reasons, whatever "business" that may be.


        • Curiously, we recently had an applicant who seemed really solid, good skills, nice background, but kept talking about their desire to write perfect code. There was a great feeling of unease about whether or not this individual would be sometimes be willing to write code that was less than perfect in order to meet deadlines or odd requirements (we never found out. He doesn't work for us.)

          By the way, will you be at OSCON this year?

    • As long as "it works" means "it passes the extensive automated test suite."

      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • I've found the best solutions, pristine or not, come from people who truly understand the problem and problem space in which they are working. The truly ugly or "stupid" solutions are the ones that work by accident when the coder didn't really understand how or why.

    The bigger the project, the more important to have someone breaking the big problem into logical smaller problems. Even then, I think everyone needs to understand the larger problem.

    This is where I might find some fault with Microsoft as an exa
    • This is exactly how I feel.

      Code is always a trade-off. It always caters to some cases better than to others, because there is never any single way to do things that would always be best. Of course, I'm not saying anything new this is why Extreme Programming proposes what it proposes, and why it embraces constant refactoring as a way of life for a project.

      What is important, is to be aware of the trade-offs. That requires a solid understanding of the problem first; it's okay to parse HTML with sim