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
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
here's my shot (Score:1)
2. Clean, well-organized code.
3. Quality of project management
4. Good documentation
5. Coding skills of team members
6. Non-rushed deadline
7. Good (and plentiful) hardware
8. Choice of implementation language
9. Choice of framework or tools (aside from language)
Reply to This