Give my Dad the source code to Word and he won't be happy. Give him a running program and he will be (at least, as happy as anybody can be with a copy of Word ;-) Source code is not a product

That is an old, but fundamentally flawed argument. The fact that the source might need to be compiled into a different language (machine language instructions) to be used as intended doesn't mean the source isn't the product. The source code for the Parrot virtual machine isn't a specification of that virtual machine, it is an implementation of that virtual machine. Knuth's TAOCP volume I *specifies* a MIX machine without implementing one. It could be implemented in Perl, C, or even in hardware. And if I write MIX machine code that implements SomeApp, that machine code is my source code for SomeApp. The fact that the SomeApp's source code happens to be directly executable on a physical MIX machine, but is ultimately translated down to a completely different machine code when run on my Perl or C based virtual MIX machines, doesn't make that source code a final product in the first case, and just a specification or design document in the second case.


In reply to Re: Re^6: Programming Versus Engineering by Anonymous Monk
in thread (OT) Programming as a craft by revdiablo

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.