You might design the industry-strength application?
Actually you need modularity and scalability then.
The application should remain maintanable and flexible.
You do need design patterns!
But be aware that Perl design patterns are quite idiomatic:)
They differ from C++ design patterns.
So use the perlish patterns and build the application.
The key word is 'to build' the application instead of to 'to code'.
There is an entry point:
The good idea is to avoid them all at once.
Different layers require different set of patterns.
And different application scale also want various approaches.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||