Resistance to change of any kind is pretty much universal. If they have a way of doing things that seems to work for them, naturally they are not interested in investing time to learn your new way, even if it will eventually save them time. Maybe they don't consider the work you're saving them from difficult or time-consuming. But most likely, they just don't want to spend 10 minutes learning how to use your tool if they don't have to.
This kind of resistance can be seen elsewhere (using CVS, using CPAN modules, etc.), and I don't know any silver bullet to solve it. You can try winning them over one at a time, or your manager can tell them they have to use it. I've seen teams waste tons of time or use terrible tools because of unwillingness to try new things. Many won't change if they have a choice in the matter, but once they try the new thing they'll realize how silly it was to do it the old way.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||