Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
My first impression is that "whew! you've put a lot of work into this." My second impression is that your work has just begun.

The list is too long and the potential conflicts between some of the various standards you've cited need to be explored. So too, the match between the list and the problem areas for your particular team. The key is focus: too much information is equivalent to no information at all.

Conflicts between "best practices" isn't necessarily bad: good architecture is often a delicate balance between competing principles (e.g. abstraction and simplicity). In fact, discussing and exploring competing principles as a team is a great way to develop good programming judgment about which principles should apply when.

I also noticed that nowhere in your list of sources did you mention interviews with your team members. There is another thought you might want to consider that came up in a recent discussion between tilly and myself: mentorship. Programming is as much an art as a science and if there are experienced members of your team with proven design and implementation skills, it is a good idea to ask them for their insights and to encourage them to coach the less (software wise) mature members of the team. Sometimes the bluebird of happiness is flying around in your own backyard. A design principle taught and tied to the experience of an old hand and a member of the team is going to carry a lot more weight than the rhetorical pronouncements of the latest gurus.

Best of luck with this project, beth

P.S. If you have a manager that doesn't get that last bit (rhetoric vs. ...) I have a nice article from Harvard Business Review on the Rhetoric of Action that I can dig up for you - and I'm sure I can find others as well. Just msg me.


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

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 studying the Monastery: (7)
    As of 2014-09-22 06:54 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      How do you remember the number of days in each month?











      Results (182 votes), past polls