For code that others may see, beautiful code is something that is easy to read to me. As a goal I prefer self documenting code, but if there is a trick then comments are necassary.

If it's something I banged out in an afternoon and may never use again; Whatever works. If something new was discovered or it's a neat bit of code; I tend to save those off to the side for incorporation elsewhere. They get cleaned up before hand.

Short description: If I can read it, it's beauty. If I look at my code later and go "What the hell!?", that's ugly

And obsuscation is beauty of a different type.

In reply to Re: Monk ethics: Beauty vs. Power by lemming
in thread Monk ethics: Beauty vs. Power by kaatunut

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.