comment on

Wow! Great node. Lots of ideas and comments; all great!

This node happens to hit home for me right now. I've been given the task of developing and intitutionalizing a set of System Engineering "Best Practices" for our work developing and fielding a variety of systems and I am facing many, many of the exact same issues as brought up here...though mine pertain to overall engineering rather than coding.

I have found many of the ideas and comments on this node surprisingly meaningful and applicable to my challenge and will weight all the comments carefully to find a multitude of nuggets.

Some ever spur me to think about adding some coding-specific "best practices" for our systems' software, too.

PM always delights, astounds, and teaches so much to so many. Thanks to you all!

ack Albuquerque, NM

In reply to Re: On Coding Standards and Code Reviews by ack
in thread On Coding Standards and Code Reviews by eyepopslikeamosquito

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.


Keep It Simple, Stupid
	PerlMonks