> If you want to modify a method that has 10 unique contributors. Do you really need to talk to different 10 people to maintain to make a change? I think the m

> If you want to modify a method that has 10 unique contributors. Do you really need to talk to different 10 people to maintain to make a change? I think the more apt example in this case would be if somebody made a modification in that file and you rewrote just their modification immediately after they done it without discussion. If the modification is necessary so soon it means that the feature/implementation were not discussed properly before and the process probably needs revisiting. Of course if you are modifying part of the file, or doing some previously agreed refactoring effort then explicit author consent is not necessary. > Secondly: version control. If you want the old version of some code I think here we talk mostly about production code. The problem with relying on the source control for "I will revert this to the old version when it will become required" is that the code will evolve in subtle manners and it will be hard to roll back and apply all patches on top of it.