Like grandfather says, generate some representative sample data (mock data), then write a test suite around the mock data, and put it into version control
Once you have mock data and test suite, its time to refactor, more on this in What is the best way to add tests to existing code?, Re: Idiomize This - Cleanup/Transform, Re: Moose and Antlers!, Re: Splitting a project into smaller files, Re^3: A question about web service security, Re: What CPAN Modules are Good to Learn From?, Developing a module, how do you do it ?
The actual framework you choose ( Catalyst or Badger Power ... ) is not that important, what is important is making functions , documenting what they do, making sure they work as documented, making sure the program (the public interface ) works the same -- basics of maintainability
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|