27 Jan 2011 17:14 UTCThu 27 Jan 2011 - 5:14 pm UTC
Greetings, aside from version control, what are the best practices to keep one developer from breaking the code of another developer. Often, someone will break another's code, won't realize they've done so, and then our team spends hours searching for the root cause of the fault. We want a list of best practices in this area so that we can be sure to follow them. Any comments on specific tooling is welcome as well. Thanks
30 Jan 2011 18:04 UTCSun 30 Jan 2011 - 6:04 pm UTC
5 Feb 2011 07:18 UTCSat 5 Feb 2011 - 7:18 am UTC
We have version control. If we roll it back, yes, that removes the conflicting features but it doesn't solve the fundamental problem. That is, the logic that one developer uses to implement a new feature is conflicting with the logic that another developer uses to implement a different new feature. If we want both features we need to find a way to move past this challenge. Part of the answer appears to be "continuous integration". Namely, accepting that this conflict will happen but catching it as soon as possible.