Personally, it's this very aspect of programming that keeps me doing it.

The fact that I can look back at code I've written a few years ago, or even weeks in the case of my Perl, and notice that I no longer do things inthe way I used to, means that I never get to the point were I could say "I've done it it all so I'm bored".

For the last few years I have kept an archive of code I have written (originally on optical disc, now CD's, DVD's soon.) and I wish I had started doing this 20+ years ago. I started out with the intention that I would be able to use it for code re-use and whilst there have been occasions when i have been able to simply crib something straight from the original version and use it, its a rarity. Most often I look back at the original, work out how I did it then and then re-code from scratch. The results are (mostly) a big improvement but because I can normally get back into the mindset I had when I wrote the original, I benefit from that as a starting point.

Back in the early 80's a company in the UK produced a program that caused a lot of hype. They called it "The Last One", with the meaning that it was the last program that human beings would ever need to write! One of my lecturers at that time suggested that those of us who were looking to making a career from programming might like to rethink as "it is patently obvious that before long all programs will be written by computer". I'm glad that a) I ignored this 'sage' advise and b) programming continues to be more craft than engineering. As a one-time mech.eng. (draughtsman) who had become bored with lack of challenge in that field.

Despite being of (now very apparent) mature years, my 'yearn to learn' is still strong, and is, in many ways, the saving grace of my sanity in a world filled with corporate dogma, rhetorical coding standards and the rule of lowest common denominator.

Long live the craftsman's Guild of Itinerent Software Labourers.
And long live its defacto creed of 'live to learn, whatever the source'. Down with nee-syndrome.

In reply to Re: What to do when you realize you've written bad code by BrowserUk
in thread What to do when you realize you've written bad code by l2kashe

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.