Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 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. Commented Apr 29, 2011 at 13:59
  • 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. Commented Apr 29, 2011 at 14:16
  • @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. Commented Apr 29, 2011 at 14:28
  • @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. Commented Apr 29, 2011 at 14:58
  • @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. Commented Apr 29, 2011 at 15:45