A bit of both. It depends on how many times I've done the solution to the problem at hand. And how familar I am with the problem domain. The more experience/familarity I have, the more time I spend trying to improve the code. I have to admit that I don't ever remember saying 'I need to decrease coupling' though—usually it's more along the line of 'This code sucks!' or 'What the hell was I doing there?'

When I start on something new, I spend most of my time doing research. Then when I have some slight clue, I proceed to implement my newly acquired vague notion. I tend to do this in a top down fashion and I iterate the code until I've achieved some minimal goal (i.e. like 'Ok, this works, now what?) One thing I do as I move (hopefully forward) along, is review the code that I've written. This is particularly handy if I'm stuck on some feature or solution, since I can switch to improving existing code as a break from pondering problems. Often a side effect of this disjoint approach is that my subconscious mind manages to come up with the needed answer/s.

hsm

In reply to Re: Code that feels good by hsmyers
in thread Code that feels good by scott

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.