On Wednesday, February 16, Frode Nilsen wrote:
>
> There are two situations that makes this "mess".
> 1. The developers are situated at different sites, working at different
> times etc.
I've worked with people on projects all over the world. This has *never*
been a problem. Not ever.
> 2. Some of the code are libraries that no one thought anyone else was
> working with, but they needed a quick improvement.
Here is your problem. These "quick" improvements tell me that you do not
have any management structure within your developers. It's basically a
"free for all". While this may work in some environments, it usually causes
duplicated and wasted effort. Communication *WILL* solve this, locks will
not.
> That is true, but as always, real life is not so simple. The code stays
> this modularized for about 6 months, then bug fixes, new features etc.
> makes their way in and mess things up until someone says 'Hey we need a new
> design for this solution' and then after 6 new months your code are
> "correctly modularized" again.
Exactly why managers are paid more. If you have a "mess", your managers
are not doing their job.
--Toby.
