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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Excellent point. Having come from a fine-art background myself I have always been annoyed with these types of comparisons, because they almost always miss the ways in which programming is actually like $something_that_is_not_programming. Especially high level comparisons like this, they always fail once you look at the details. Fact is that programming, like anything you do, can be an aesthetic act if you choose to make it one.

    - Stevan

    • In a way I agree with you. I's annoying when the details don't match and people still keep trying to infer too much from the analogy when some things clearly aren't they same.

      It's like the tired, programming-isn't-like-building-a-house/bridge/brick wall analogy, as if these things are completely well known and explored and repeatable whereas software development isn't. Usually stated by programmers who don't know how to do either of these other things.

      I once read a thread on Reddit that went down this route, and I just loved it when someone who knew how to build a house responded and demolished the analogy with actual facts. And then someone who knew about bridges did the same. And then someone wrote a long post about how difficult brick laying was.