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.
  • by jplindstrom (594) on 2007.09.13 19:10 (#57799) Journal
    Something like this:

    1. Mature supporting infrastructure.
    2. Coding skills of team members.
    3. Quality of project management.
    4. Non-rushed deadline.
    5. Clean, well-organized code.
    6. Choice of framework or tools (aside from language).
    7. Choice of implementation language.
    8. Good (and plentiful) hardware.
    9. Good documentation.

    Notice how I sneakily expanded "just tests" to encompass the whole concept of supporting tools, e.g. automated tests, version control, continous integration, etc.

    Project size would also belong somewhere near the top of the list.

    Item 0: Competent, clued in people who reflect upon what they do.

    From that, all else follows.