Skip to main content
8 events
when toggle format what by license comment
Apr 29, 2011 at 22:52 comment added S.Lott @quant_dev: In the short time the "problem" is vanishingly rare. Indeed, the conflict is trivially solved through management and a phone call among the three principles.
Apr 29, 2011 at 22:42 comment added quant_dev I just don't like the answer "this is not a tool problem". Changing architecture to avoid such conflicts is a long-term solution. In short term, it would be nice to have a tool which can alleviate the problem. And there are such tools (e.g. SVN, which would prevent the emerging of "two heads").
Apr 29, 2011 at 15:45 comment added S.Lott @David Thornley: "rethink your architecture, because it isn't going to scale". Actually, if you're having update conflicts, it didn't scale and the update conflict is all the evidence a manager or architect needs to fix it.
Apr 29, 2011 at 14:58 comment added David Thornley @quant_dev: If the main configuration file requires changes in the same places for all sorts of different changes, so that merging is not normally automatic or at the very least easy, rethink your architecture, because it isn't going to scale under any circumstances.
Apr 29, 2011 at 14:28 comment added S.Lott @Andrea: At 100 files per person, it's really, really unlikely to have this kind of overlap. With a team of 500 the responsibilities must have some partitioning and structure to them. Chaos is really, really unlikely.
Apr 29, 2011 at 14:16 comment added Andrea I agree. But I have never worked in a large team, and I'm not sure it would be unlikely in a project with 50000 files and 500 people.
Apr 29, 2011 at 13:59 comment added quant_dev Not necessarily, there are some files which will always end up being edited by many people. For example, the main configuration file for the application.
Apr 29, 2011 at 12:02 history answered S.Lott CC BY-SA 3.0