Whenever we impose a structure onto a set of objects, we also impose our values. Nowhere is this clearer than when the structure is hierarchical. Divisions clo

Whenever we impose a structure onto a set of objects, we also impose our values. Nowhere is this clearer than when the structure is hierarchical. Divisions close to the root of the tree implicitly carry a greater weight of importance than those close to the leaves. This property means that it is difficult to find compromise within a single hierarchy; a driving force behind the prevalence of flat 'tagging' mechanisms. In spite these drawbacks, the very rigidity of hierarchies offers us an unparalleled communications opportunity: The distinctions that we make at the root of the tree are highly visible and send a clear message about the divisions and items that we consider important. Is it important that tests be kept separate from product logic? Is it important that projects be kept distinct from one another? Is it important that each component or service be kept isolated? How about maturity? Is it important that research code be kept distinct from production code? We have the opportunity to form a strong opinion, to make a lasting choice, and to shape the culture and the attitudes of those who follow.