I would add that you could do a few simple things that make you and your work product a lot more valuable to everyone:
1. Pick and use a good code template.
2. If there is CVS or CVS-like tool, use it.
3. Track your changes each time.
4. Use comments liberaly.
5. Don't "golf" the code, remember you may have to maintain it when you are old and weak minded.
6. Make the test harness usable by nearly anyone.
7. Be wary of skew between the development and the production environments.
8. Create concise and direct documentation.
9. Be sensitive to "how the boss wins and loses".
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||