Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
    Plan a design before you start.[...] Plan to throw away at least one design and start over.

Try to keep your design fairly compartmentalized, and loosely coupled. That way, when you do find a flaw in your first design, you don't have to throw everything away: some of the code you've already written will easily work with your new code. (For instance, if you're always updating a database the same way, and you keep the database update code well-separated from everything else, you won't need to make any changes to it when you realize that your interface code is hopelessly screwed, trash it, and start over.)

The hell with paco, vote for Erudil!

In reply to Re(2): Writing a large application in perl? by FoxtrotUniform
in thread Writing a large application in perl? by BUU

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.