Note: This list assumes peer-reviewed design, if not peer-reviewed code.
- Before writing new code, demonstrate that what is needed cannot be found on CPAN.
- Before writing new code, demonstrate that what is needed cannot be found in-house.
- Attempt to write large modules and small scripts that use aforementioned large modules.
- If you want to disable strict and/or warnings, you better have a damn good reason.
- It's better for the code to run 10% slower than for the coder to take twice as long. Code reuse is good for a reason.
- Standardize to a common set of idioms / modules / processes for the following items:
- Configuration files
- Database connectivity
- Logging
- Exception handling
- Documentation (not everyone should use POD, believe it or not)
- Source code rollouts (how should you install something?)
- Taking an extra hour before touching a keyboard will save you a hundred hours in the next 6 months. To truly be Lazy takes a lot of preparation.
And, my favorite recommendation is Keep It Stupid-Simple ... so simple even stupid people can understand. Cause, frankly, the guy after you will most likely be stupider than you are.
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.
