Can a writer really refuse to show his/her work when under contractual deadlines? Is this really that different from the creative output of a software developer? Once the work has been released into the world, literary authors don't go back to rework their works too often, I imagine, but neither do they build on previous works the same way as software authors.

In the course of writing a piece of code, I have not infrequently had to rewrite the code multiple times during the initial phases (design, coding, unit testing), and less frequently during later phases (integrated testing). But if that's what is required to get the functionality correct, that's what I do. It's not that I tell my manager that's what I'm doing, nor that I don't tell my manager. It's just what I believe is the fastest way to get an accurate, reliable piece of functionality.

Larger (subsystem+) rewrites are much more rare. But, again, if that's what is required to get reliable, functional code, then that's what I do.

It is important, though, that you've learned from previous mistakes before going through a rewrite. In the initial phases, this is pretty trivial: you just wrote the non-working code, so rewriting it immediately should naturally incorporate what you've learned. For later phases, where there may have been a time span of a week, a month, or even a year, between write and rewrite, this can be much more difficult.


In reply to Re: rewrite: in literature and in coding by Tanktalus
in thread rewrite: in literature and in coding by johnnywang

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.