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.
  • Here's mine:

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

    I tend to agree with Bill de Hora [dehora.net] that source control, a build system, and issue tracking are more important than most people (particularly non-developers) credit. Poor ones act as an anchor on anything you do, particularly on larger projects.