Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
As someone who has been known to venture his opinions on maintainability, I think this dream exam is impossible to make work for various useful values of work.

The problem is that maintainability is not inherent in the code. Instead it is an interaction between the code and the maintainance programmer.

For reasons I hint at in nodes like Re (tilly) 1: Compactness, one of the characteristics of highly maintainable code is that it does a good job of maximizing the understanding the programmer gets for time spent studying the code. This is very different than maximizing functionality per character. For instance it is far more important to make it as easy as possible to chunk concepts together into higher level constructs, with which you can express your solution very naturally. And, of course, you would like to name and document your chunks suggestively so that the maintainance programmer can learn to use the chunks you are working with without having to go through all of the details.)

However note that this description is highly dependent upon the programmer. Using powerful constructs like map can make it very hard for someone who knows only a little Perl to figure out what is going on, while causing no trouble for the experienced Perl programmer. Experienced programmers immediately chunk idioms upon sight, while less experienced ones don't know and don't care that something is a common idiom. Competent programmers generally have far more tolerance for having ideas rapidly build on each other than average ones or novices. (Code meant to be read by non-programmer, eg configuration files, should not be organized like you would for a fellow programmer.) There are many different styles of programming and you chunk in each in a different way. For instance OO and functional styles pose problems for people who are not experienced in them, even while they simplify life for people who are familiar with the style.

And so on.

In short, the maintainability of code is not something that exists in the abstract. Sure, code can be (and often is) clearly bad. But in general there isn't really such a thing as clearly maintainable code. The maintainability of code is defined through interaction with your audience, and the audience of possible Perl programmers is too diverse to be readily characterized.


In reply to Re (tilly) 1: Certification Foo by tilly
in thread Certification Foo by sheriff

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others surveying the Monastery: (6)
    As of 2014-12-25 15:47 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      Is guessing a good strategy for surviving in the IT business?





      Results (160 votes), past polls