This is not really an answer to your question, but after reading your post I can't help but think that maybe you should try out test-driven development, and see whether that improves your job satisfaction as a developer. I don't know exactly why you feel you're not efficient (enough) as a developer, but for me TDD cancels out many of my personal failings which would otherwise hamper my development work (like procrastination in the face of a big task, indecisiveness on what to do next, over-engineering a project rather than starting it, and more). This is not what TDD is about primarily of course, it's foremost a design methodology, but these are nice side effects which make my work more enjoyable and productive. Maybe it'll do the same for you? And if not, at least it's a step in the right direction towards full-time testing.

As an aside, one of the links adrianh gives in his post lead me to a blog-entry which has got to be one of the best articles on TDD-related topics I've read recently.


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

In reply to Re: OT: Testing, operations and support resources by tirwhan
in thread OT: Testing, operations and support resources by talexb

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.