Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 1. Quality of project management.
    2. Good documentation.
    3. Automated tests.
    4. Clean, well-organized code.
    5. Coding skills of team members.
    6. Non-rushed deadline.
    7. Choice of framework or tools (aside from language).
    8. Choice of implementation language.
    9. Good (and plentiful) hardware.

    If no one is leading, things go nuts.
    Lead can't happen without docs (requirements at least). Testing tracks intent, documentation, and regression. Skliz can be learned/aquired, and poor skils can be overcome with good testing and clean code.