You go up to a assembly worker and tell them their job requires minimal skills and that the "engineers" will have solved most of the problems in the manufactoring process and you'll probably get a thump :-)

Thanks. You are right to call me on this and you are right that i expressed myself poorly. To clarify (and save myself a thump :-) I shouldnt have said minimal skills. I probably should have said "minimal engineering skills". The point is that the folks working on the drawing board most likely have engineering degrees and the folks working the floor dont. If thats no longer true due to advances in the manufacturing process then forgive me for being a touch out of date. (I can imagine that robotics has probably eliminated much of the "unskilled labour" from the factory floor.)

I think engineering/factories and architecture/building are deeply flawed metaphors for software development. Any time I see one little warning bells start ringing in my head. They are usually based on "folk" ideas of how these processes work that have little resemblance to reality.

That would be a meditation id love to read. I still believe that there are things to be learned by such comparisons however. In this context however id like to emphasise that the process is not really what im comparing here. Im comparing the skill types and levels required of the different players in the game not really the process by which they work together.

I seem to recall that Knuth had a chunk more on the analysis of Shell sort in the second edition of his Sorting and Searching volume

Im pretty sure the edition im referring to was the second edition which does a fair amount of analysis, but also says that there are still unanswered questions about the algorithm.

---
$world=~s/war/peace/g

In reply to Re^5: Analogies & metaphor (was Mathematics eq CompSci) by demerphq
in thread Mathematics eq CompSci by kiat

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.