>Readability is a very worthy objective. Agreed, but its not the only objective. There is a balance to be struck. Speaking from the perspective of an individua

>Readability is a very worthy objective. Agreed, but its not the only objective. There is a balance to be struck. Speaking from the perspective of an individual that delivers software as part of a team: producing readable/understandable code == GOOD letting your aesthetic preference be disruptive == BAD As an anecdote I have worked on teams where a certain individual's need for symmetry in the code base has significantly reduced the efficacy of source control and caused issues particularly with automated build/deployment. When I criticize "readability" its not because I don't believe its important, but rather because its too often used to justify one individual's preference without regard to objective counter criteria and too often embodies "The perfect being the enemy of the good"