Re: code-sharing at work.

in reply to code-sharing at work.

This one comes up for me every so often. I tend to find there is little one can do on the merits of the code. Mainly it involves lots of talking. Getting inside peoples head, and convincing them one by one.

But I do think that sharing promotes sharing. A local code repository of shared code might help. Perhaps all the POD transformed to HTML and searchable from a web page -- your own mini cpan/search.cpan. Definitely more docs.

Also make sure you use others code -- set a good example.

But mainly I think it takes time, and talking

Comment on Re: code-sharing at work.

Replies are listed 'Best First'.
Re^2: code-sharing at work. by geekgrrl (Pilgrim) on Mar 23, 2005 at 21:20 UTC
we've bounced around the idea of setting up a wiki that would function as a plaec to talk about our modules and what they do - so we at least know what everyone is up to and doing.	[reply]
Re^3: code-sharing at work. by tomhukins (Curate) on Mar 23, 2005 at 22:37 UTC
If you can easily get together physically, discuss things that way. We have two meetings a week involving all our developers: one where we all say what we're up to (a typical weekly meeting) and one where we review a particular piece of code or a process. We have a Wiki, and we use it to document the conclusions we reach, but I can't imagine using it to replace focused meetings with a clear agenda.	[reply]

In Section Meditations