Earlier quoted context omitted.
Building a solid design culture is extremely hard - in my experience having worked professionally as a designer and engineer, much more so than a solid engineering culture (which is already insanely hard). There’s a reason only a handful of organizations in the world succeed at both. I spent time volunteering for Gnome many years ago (2.x days), and it was extremely hard there, even though it had a reputation for bei…
Perhaps having "skins" capabilities would allow the best of both worlds...though it might end up like WinAmp with thousands of unuseably designed yet popular skins.
For example, you could decide to move some functionality from a sidebar to a context menu. this implies reprogramming the interface very differently; a skin can't do that. This also implies prototyping a lot. So basically the designer and the coder have to sit together quite a lot, that's not easy when you communicate via internet.