Well, uniform code is nice, modular code is better. You don't need to
worry about uniformity if everything actually calls the same code. And
if you need to change how it works, being able to do it in one place is
much less likely to cause problems. Of course, that needs to touch
foreign code in a lot of places instead of just leading by example. And
that's where actual leadership is helpful since it can _make_ people
change their _own_ code, and they usually are much better qualified to
see problems in connection with those changes than a self-appointed
global janitor can hope to be.
I totally agree.
> I think a good policy is that, when working on that which one wants to
> work on, one should always strive to do it in a way that leads to
> better maintainability and extensibility.
If those efforts are not coordinated, there is no end user benefit.
"Coordinated" does NOT mean slavery and being a bored, sad programmer ;) It just means that no one is "a self-appointed janitor", because there is always someone, who keeps an eye on some guidelines of a quality of a Lilypond code.
Hoping to read soon your answers to my questions,
Łukasz Czerwiński