Hello

I am very much in favour of code inspections , some of the advantages I see are :

Problems in logic , which may be hard to reproduce, can be spotted early in the development cycle.
They can enforce coding styles in a community.
Knowledge can be spread in a group.
Enhancemenent of team spirit and idea of a common goal.
They can go further than checking the actual functionality, e.g. inspection of maintainability.

These advantages are in my opinion more important for small or medium sized teams working on a common project for some extended period of time.

So, I endorse the practice in a coding community , but don't believe in it for OS.


Tabari

In reply to Re: Code Inspections in Open Source projects by Tabari
in thread Code Inspections in Open Source projects by zby

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.