Templating is a good solution, but you have to define your problem first. If you just use it and don't have a good sense of why they are good, then you'll "use" them but not in a way that solves any
problem - and then they'll seem useless.
Re (tilly) 6: Code Critique tries to give an overview of why templating is good, what you need to do to make it succeed, and what you can hope for from it if it succeeds. Unfortunately it tends to be the case that you can hear all of the advice in the world but it won't "digest" properly until you've actually tried it in practice and you have some experience to put it into context. So the first time you try to use templating to clean up your code you probably won't realize the benefit that people talk about getting - but you will get the experience to be able to figure out what you could do differently to get a better benefit next time. (Which is still valuable. Plus you'll likely still get some benefit.)
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||