in reply to
code-sharing at work.
Yep, I agree with most all the posts above. Time is going to be the biggest key. The only way I can think of to make the time shorter is if you or your manager or his/her boss can create some sort of personal benefit for the individuals who start to incorporate parts of the "library" into their code.
Examples off the top of my head are
- Cash for each library used within a certain time frame
- Lunch out for those who've migrated to using x modules at the end of a month
- Golf day
After about 3 of these, there should be enough momentum toward change that the rewards can decrease/cease.