Ratio War

A RatioWar is a HolyWar, or at least a controversial opinion, that the ratio between two items should be high or low, or greater or lessor than it is usually done in practice. Some point to technical considerations, e.g. regarding optimizations and analysis available in tools today, granularity for meta-data, and reuse. Some suggest that it's primarily a matter of personal preference: the position that WetWare is the primary driver of the best balance choice.

Topics related to RatioWars include:

An interesting question is whether there are commonalities in the arguments for or against these different items.

Another interesting question is whether pairs of policies lead towards a 'natural' (fixpoint) balance between large and small, yin to the other's yang. Example: DoTheSimplestThingThatCouldPossiblyWork (brute-force addition of features you need) and RefactorMercilessly (splits out shared elements, makes components smaller) and YouAintGonnaNeedIt (don't support features that aren't in demand) are a trio of SoftwareEngineering policies that achieve a natural balance in the 'size' for functions, classes, methods, etc. And MissingFeatureSmell and LanguageIdiomClutter balance one another as well.
See also: IncompatibleGoals
CategoryConflictResolution, CategoryArchitecture

View edit of November 10, 2014 or FindPage with title or text search