Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • My take on this:

    • 1. Quality of project management; I think nobody wants to admit it, but good management is crucial for setting end goals and keeping the minutae out of your way
    • 2. Automated tests; this is absolutely crucial, you can't ship unless 100% of tests are passing.
    • 3. Coding skills of team members; good coders imply that 2) will happen on its own
    • 4. Choice of implementation language; you can't write a high performance firewall in php, for instance (not to pick on php)
    • 5. Good (and plentiful) hardware; having hardware that is consistently slow or crashes just plain kills morale
    • 6. Good documentation; not so important for the initial launch but if this project requires any maintenance this is essential
    • 7. Non rushed deadline; it's good to have time to think things through but you don't want to take forever
    • 8. Choice of framework or tools; I think the reason I put this here is because I just assume that everyone wants to use the same framework as me :) I've worked with some frameworks that have been really painful to maintain, but fast to develop with, so I guess that the framework is more important to maintenance than initial project success.
    • 9. Clean, well-organized code; this is important definitely, but I've learned that good coders can work their way through bad code. Although I've seen code (I'm sure everyone has) that takes hours to figure out what's going on.