Thank you.

I was actually thinking that the way one develops code is highly non-linear. According to me, the way we study e comprehend it too. Moving from this principle could be useful for books, as I said in my previous message. Or for teamworks, so that different programmers at different levels could communicate between them.

Code provide at the same time all levels of details: documentation, comments, high-level code, tricks and so on. Good programmers organize this stuff so that one can easily dig trough their code (for example, with POD you can separate documentation from code). I think this could be done more effectively, using principles of graphic design.

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.

Me too. But, for example, maps of undergrounds are illustrations, and I think I can judge them by aesthetic and readibility standards. I'd like to try to transform computer programs in illustrations. Perhaps this is a complete waste of time. I hope not :)

It's better I provide an example of what I'm talking about: if I'll have time, I'll do it this weekend.

see you. larsen

In reply to Re: Re: Beyond literate programming... by larsen
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.