What do you do when you realize you've written unmaintainable code?

Either refactor it or throw it away and start over.

In either case, try to take things one "story" (use case) at a time, building and testing small increments, and refactoring the code when you're done. Refactoring is like cleaning the kitchen when you're done cooking. It leaves less places for bugs to hide, and sets you up for a clean start for the next meal.

The key to making this kind of development work is having an up-to-date test suite. Otherwise, you're never quite sure if you broke something.

If I step into a mess, I'll try to write some test cases before I start to refactor. Often, the simple (hah!) act of getting tests cases running is enough to uncover substantial problems.


In reply to Re: What to do when you realize you've written bad code by dws
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.