The situation where I saw this pattern involved a solution which had 2 systems with BizTalk in the middle. The developers then hooked together the solutions on each of their machines so that when one of them wrote a little code he would need the component on each of the other 2 developers machines to be able to run his test. This would work okay until one of them added a breaking change and the others would not be able to do anything until everyone was working again.
The main point on this anti pattern is it is good to integrate early. So for example if you have a feature which is ready you could make it available for the others to use by in BizTalk's case publishing your application to a server where the others could hook up to it if they wanted. Integrating Early can often find problems and is a good thing. However integrating all of the time is a bad thing because you create strong dependencies on other teams and other people. For example if Developer 1 goes home early and turns off his machine then Developer 2 can not do any work. |