I have a bit of a graphics background (a major that was 1/2 computer science & 1/2 photography), but I don't really think that relates too much to this. while I think that your idea of graphically illustrating a program is interesting, I don't really think that would contribute that much to a program.

I've seen programs diagramed as flowcharts illustrating the different steps a program takes while executing, which is certainly useful for some. It's not as good, though, as a good design for your program. Good abstraction, elegant algorithms, and well written code will, in my opinion, do far more to make a program easy for someone other than the original author to understand than all the flowcharts in the world. Those same 3 things are pretty much my only criteria for the beauty of a program.

Personally, I think that stuff like tux poster is ok, but not that pretty to look at. I'd rather judge how beautiful code is by 1 set of standards & how beautiful a illustration or painting is by a completely different set of standards. I know a lot of stuff has tried to merge the two (like the antitrust movie desktop wallpapers) but it seems silly to me. -- cat


In reply to Re: Beyond literate programming... by cat2014
in thread Beyond literate programming... by larsen

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.