I don't know about you, but I haven't tried all 7500 possible combinations to know which works best. What I think works fine could really stink. I could really be missing out on something great, and not even know it.You don't need to find 7500 ways that work. You need to find one way that works well enough. If it's fast enough to develop, easy enough to maintain, and scales well enough in production then your problem is solved.
One of the first things you learn in an economics class is the importance of opportunity costs. There is always a different way to spend your money or your time. The most important lesson about opportunity costs, though, is not that you must be perfectly methodical in your evaluation of them. The most important thing about opportunity costs is that if you spend all your time trying to figure out how to spend your time and money, then you'll have no time or money to spend and will never spend it on anything useful anyway.
Pick which trade-offs are acceptable to you and which ones are not. Then, be prepared to actually make a decision and follow it through. If you find you can't complete a task reasonably well with what you've chosen the first time, that's an expense. It's probably a smaller expense than never making the decision because you were still studying the options when it was time to act.
More information would be nice, and there have been numerous metadiscussions about the module selection process here already. However, this is not a perfect world and we often must act with incomplete or even inaccurate information. There's a large middle ground between acting too hastily and acting too cautiously. Try to find that middle ground, because that's where things get accomplished.
In reply to Re^3: On the scaleability of Perl Development Practices
by mr_mischief
in thread On the scaleability of Perl Development Practices
by jdrago_999
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |