On occasion I have heard that a single style of programming with which everybody complies is a good thing because then code is easier to read and a number of other warm, fuzzy advantages. To that effect, in Opera Anecdotes by Ethan Morden, one finds the following.
A lesson from Sardou
We have already seen Alberto Franchetti expressing doubts about the musical possibilities in Sardou's La Tosca, even when Verdi gave it his recommendation. Oddly, after having taken the libretto away from Franchetti (through their publisher Ricordi, who played on Franchetti's doubts), Puccini himself suffered doubts.
He revealed them to Sardou in Paris. Perhaps a Frenchman should set it, perhaps Tosca is too forceful to suit Puccini's kind of heroine, perhaps Franchetti's fear of it is a warning that others should fear.
Sardou couldn't have disagreed more. Tosca was not a Frenchman - it is a Roman work, and needs italian canto. Moreover, there is no such thing as a "kind of heroine" --- women in love are all the same. As for Franchetti, the very fact that someone else had shown interest in Tosca proves its viability.
Still Puccini hesitated. Even if Tosca is right for opera, is it right for Puccini? Sardou is tense, direct, violent, but Puccini's music is gentle, delicate. Puccini writes in a different style.
"There are no styles, Monsieur Puccini," Sardou thundered. "There is only talent!"
In other words, Monsieur Puccini, forget about style. Everybody has their own, get over it and just do what you are talented at. After all, what are listeners going to say? That Monsieur Puccini's music is bad because he did not write an opera in the style of Joseph Haydn or anybody else whose style we arbitrarily choose as the golden standard?
No. Instead, while we can have our likes or dislikes, I think it's better to recognize that even if we were ultimate composers, we will never compose like Ravel, or Schubert, or Mozart. They are unique and irreplaceable.
Oh but when it comes to code my friend, we do not always have that attitude. Why do we seek to convince ourselves that our subjective style is superior to that of all other developers? Why do we assume it is our duty to behave like art critics who, more often than not, are not creative artists themselves? Why don't we account for the fact that others may have made choices differently than us because they had their own set of unique experiences and decisions to make?
In my opinion, discussing things like style in terms of better/worse wastes time and distracts us from what we really have to do. As long as the problem is not truly beyond subjective judgment, such as having 100 line methods or being tightly coupled in ways that demonstrably make stuff fragile, the best thing to do is to let the work of others be.
Does this mean that we should complain about everybody else's style because it's not ours, only doing so secretly because it's more polite? No, not really. A better answer than that can be found in what happens in truly restrictive development environments. In fact, it is extremely likely that most of the developers told to use a particular style end up using a style which is not their own.
But why should anybody be put into the uncomfortable situation of not being able to do things one thinks are best? Since no style is best, then imposing any particular one is tantamount to accepting a certain degree of uniform badness. Why? Isn't just doing our work hard enough in the first place? And who says what is best? On what grounds?
Instead of all that mess, it's much better to just train yourself into reading
any style just as fast as you read your own. There are two huge benefits to this. First, one keeps the mind flexible because of the clearer exposure to how different people think about things. If the first reaction is not rejection on grounds as silly as blocks not being indented "right", it will be easier to learn new things. Second, one does not spend time talking to coworkers about topics as transcendental as whether they put that final period at the end of the method or not --- or even worse: whether you happen to like it or not.
So my friend, on to the bigger fish to fry now.