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.
| [reply] |
The Right Way(tm) elements are far more then just indenting , improperly scoped varibales, etc.
Elements central to the ideas behind my original point are:
- The initial time it takes to learn what The Right Way(tm) is
- Remembering and applying The Right Way(tm)
- Fully understanding concepts and the ramifications of not doing it The Right Way(tm), before you move the knowledge from the mind (private space) to the physical (public space)
This goes beyond programming and extends into any discipline. However, the shared realtiy of life is that the above does not work because if we all remained inactive until we comprehended then we would remain inactive. We must crawl, walk, run.
| [reply] |
