I was reading some quotations and I read a lot of them that reflect my thinking.

"When I am working on a problem I never think about beauty. I only think about how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong. " - Buckminster Fuller (1895-1983)

When programming perl I have the same way of working. I try to solve the problem. Only afterwards I examine if it's ok code.
Analyzing is not really my cup of tea, I just get in there and get the problem solved(I have to say that with every new experience my code gets better). Afterwards I see if the code is good and most of the times I think there are hings that could be imporved.
It's vicious cirkel: starting to solving a new problem I use the knowledge of my previous project to write better code, but afterwards I see other things that could be improved.

What are other opinions on this matter.

I would also bring on as a second issue that analyzing and programming is best not done by one guy. Because or your a good analyzer or you are a good programmer, but being good at both is almost impossible.
This last statement is being said by some guys I work with. I haven't formed a opinion on that issue yet.


My opinions may have changed,
but not the fact that I am right

In reply to Just thinking ... by toadi

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.