Branch and Merge vsTrunk: Latent code pattern

http://www.infoq.com/presentations/The-Kiev-Experiment

time: 58:54
[Source Control/ CI (Continuous Integration)] Latent code pattern:
Multiple teams work on the same Trunk (no branching, merging hassle). Some checked in code is simply unreachable (not executable): this is ensured by event driven architecture (event does not happen, code is not triggered); modularity/partitioning and Dependency Injection technique.
The (new) feature (bit) can be OFF or ON (configured). You can promote configuration into production weeks before the release and have some features off. And when you are ready, you just flip the switch on. It allows you to be agile. Business tells you want they want and when.