On 2/14/12 at 4:44 PM, [email protected] (Iain Duncan) pronounced:
Wondering if such a thing is around? I am stuck doing a pitch to a
committee on why we are using Pyramid and not Drupal
"It's a trap!"
Seriously, any discussion that includes, "Why are you using X,
and not Y?" should be followed with, "Y must be useful,
otherwise you would not suggest it. Why do you think we should
use Y?" It's a useful tactic to learn more about the client and
their project requirements.
I welcome these discussions and never disparage any suggested
tool. Yet I find comparison of tools to be tedious,
unproductive, and, frankly, ignored. Ultimately the client will
hire you for your competency and professionalism, not for what
technology you use.
I could spread myself really thin and learn a little bit about a
lot of technologies, or I could focus on only a few technologies
and be an highly effective expert and do that well. Now if the
client has an expert in Y, then it may be a good idea to
collaborate on a small pilot project to see how we could work
together through the use of APIs. Sometimes the best way to
deal with the "Why X, not Y" question is to say that you are
technologically agnostic and welcome the opportunity to work
with experts in Y.
--steve
--steve
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pylons-discuss?hl=en.
