comment on

Too many increases the chance that the other persons code is written with themes and idioms that the maintainer is not familiar with.

Why does your organization not have coding standards?

Why are you not performing code reviews of some kind?

Why are you hiring maintenance programmers without sufficient language experience or at least sufficient training in your organization's coding standards?

You betrayed your own argument when you said "poorly written code". How can you even identify code quality without these things?

If your maintenance programmers can't handle the style of syntax your organization uses, I can't see how they have any hope of handling the interesting problems of maintainability.

In reply to Re^3: Some thoughts around the "is Perl code maintainable" discussion by chromatic
in thread Some thoughts around the "is Perl code maintainable" discussion by oyse

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks