Good practices that take more time:
- Writing tests. Either after the code, or doing TDD.
- Proper modularization of code. It's faster to just throw together procedural code than create a new module.
- Documentation. Everything from proper comments to user docs takes time to write.
- Quality assurance of third-party modules. Grabbing something off cpan and assuming it works is a lot faster (short-term) than testing it.
Those are what immediately come to mind. There are plenty more. As for your points: indentation takes no time so no excuses there but many times global variables can speed things up development (think instead of passing args and returning values from subs) this is however a very tricky process and rarely (but still sometimes) the best approach.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||