Simple problem, simple solution.

Seperate your good/opensource/happy code into one place. Seperate your bad/custom/closed/less-happy code into another place.

Your good code should always be a kernel. It's least buggy, easy to refactor and all that good stuff, reusable to all hell.

Your custom/ugly code should wrap your good code. As features are wanted in that kernel, and things are clean in the outer layer, it works its way in. But be warned, be careful about how they interact as the outter wrapper should not influence the good code on a continuous basis. It should come in sparks of brilliance, and reealuations.

In reply to Re: (OT) Sponsoring open source by exussum0
in thread (OT) Sponsoring open source by creamygoodness

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.