I used to write art reviews and I often made exactly the same point; one very unpopular in the art world: process is nonsense. Only the product, the art, matters. To some degree this becomes a context argument again. :)

Software development is completely different. It's not one person creating a finished work. Keeping a software base together is itself process. I would never have quit my last job if even 1/3 of the practices in that assessment were in place (they weren't all process either). It was primarily the homegrown, ad hoc, à la carte, manager's choice process drove me out.

Before you think I'm disagreeing with your major point I'll mention that I refused to be sent for Six Sigma Black Belt training a few of jobs back because, in the main, I agree with you; and strongly enough to cripple my own career. That was one of two choices that probably cost me a directorship or major program manager job at one of the Net's biggest animals.

So I don't disagree with you. I think there's a huge difference between bureaucracy -- which is what I feel you are really critiquing -- and best practices -- which I found most of the assessment to encourage.

In reply to Re^5: Some reflections on the Brainbench Perl Test by Your Mother
in thread Some reflections on the Brainbench Perl Test by metaperl

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.