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.
My take. (Score:1)
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.
Reply to This