It's perhaps the weirdest thing about programmers. They'll spend countless hours persuading their grandmothers to keep their knitting patterns and recipes and photos on a computer. And countless more automating drawing the curtains, making coffee, and anything they can. But when it comes to using computers to assist the the process of programming, it's like you'd asked them to dance naked in a fire-pit.

I don't trust most humans to assist the process of programming. The way I see it, a computer is useful at doing repetitive tasks. A good program, following DRY, isn't repetitive. So, where does the computer fit in?

The reason DRY works is because of modules, such as Moose, Catalyst, and DBIx::Class. I'd prefer to have the computer work through the medium of a module than the medium of an IDE. I don't have to think about the module where I have to think about the IDE.

And, personally, I enjoy dancing naked around a firepit. In one is a slightly more burning matter. :-)

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re^5: Steve Yegge on how to build IDEs and improve speed of dynamic languages by dragonchild
in thread Steve Yegge on how to build IDEs and improve speed of dynamic languages by zby

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.