Wenn Developer Websites bauen werden es oft typografisch mehr oder weniger interessante Textwüsten, die besser laufen alles andere im Web. Wenn Designer Websites bauen, kann man, während eine Seite lädt, einen excellenten Single Malt destillieren oder die Costa Concordia bergen. Hier ist eine die das Problem kennt.

Aus: Anika Henke (selfthinker.org) „The Story behind DokuWiki’s new Template“

Most OpenSource projects get initiated by developers. And at the stage they get initiated it’s already very late to get a designer involved. Ideally design should start before the development and later happen alongside it.

Another problem why designers rarely contribute to an OpenSource project directly, is because it would mean working with its code. And designers don’t usually code that much. This calls for someone acting as a bridge, willing to work with them, who understands both sides and can implement the designers’ ideas.

The one comment from the aforementioned discussion on Forrst which best sums up the dilemma: “Design is not democratic. Most open-source projects are.” Why does collaboration between designers and developers work better in a corporate environment then? It doesn’t really, but it has to! Because having a client (and a boss) makes it much less of a democracy and makes it just necessary to collaborate, otherwise there will be consequences.

As OpenSource is often about doing things voluntarily, you’ll naturally walk away if things don’t work out.Read all of this: http://blog.selfthinker.org/2012/10/20/the-story-behind-dokuwikis-new-template/

Vielleicht sollten sich Designer und Developer öfter mal zusammenraufen und gemeinsam etwas Gutes und Schönes machen (denn das wollen ja beide). Wenn wir das alle ein wenig üben braucht kein Team mehr Chef-Zampanos, um sich zusammenzuraufen und die Zampanos können sich auf das konzentrieren, wofür sie da sind: lächeln und Jobs an Land ziehen.