The tempation is still there ("hm... as long as I'm here, I should also write the mummble method, because I know I'll need that at some point..."),

I know this goes against standard XP guidance, but I find that writing that extra method for completeness sake is often in of itself a form of advanced test. A supposedly general solution that has in fact been tailored for a specific problem set/domain often passes all tests for that domain, but as soon as you push it out of its "comfort zone" you find it breaks. And this breakage sometimes could have happened inside the desired domain, but wasn't being tested for properly because the percieved scope was narrowed so tightly to "get the job done".

Leaving the tension unresolved overnight so that my mind keeps generating ideas and options helps provide instant focus, quickly overcome morning starting friction. And I'm not sleeping any worse than normal.

In some respect I consider you a lucky man. When I have unresolved tension left at the end of the session I cant get my mind off of the subject. I become nervous and irritable and poor company. I far prefer to end sessions with the completion of a module or its core functions or whatever. That way I _can_ fall asleep.


---
demerphq

<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...

In reply to Re: Unit Tests and Creative Tension by demerphq
in thread Unit Tests and Creative Tension by dws

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.