in reply to
Re: Worst thing you ever made with Perl
in thread Worst thing you ever made with Perl
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.