Wrong rant.

My comments are based on a situation where a small team that included me both developed and did maintainance on an evolving codebase over time. I was one of the maintainance coders (and was the fallback if things got out of hand), and don't think that lack of ability on the part of the maintainers was an issue.

Rather my comments have to do with a recognition of the fact that good coding is all about making code clear and understandable. It isn't about showing off how crazy a line of punctuation you can spew to get things done in 2 less lines. If you have someone who has that priority wrong, and thinks that their demonstrations of cleverness are a good thing, they either need to learn better, or if uneducable, be fired.

As for the good environment that you praise, just think about how someone who was cocky and determined to lay claim to stardom would have fit in. Not well, huh? Well those are the people who I am pointing out as being problems. By contrast the simple awareness of what will and won't be understood based on the feedback you describe is enough to achieve the goal that I am after. Not a binding of good programmers with sufficient rules to make them by force understandable to relative idiots, but just an awareness of how the team works, and what kind of code will be clear to the rest of the group.

In reply to Re: Re: Re: Re: Re: Re: A Perl aptitude test by tilly
in thread A Perl aptitude test by Jonathan

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.