[FusionAdmin] Admin list usage (was: The New Layout -- Mockup)

[RYX]

Am Freitag, den 27.07.2007, 22:59 -0400 schrieb Will Farrington:
> On Fri, 2007-07-27 at 15:09 -0700, Quinn Storm wrote:
> > Sorry for the megaquote, still getting used to the ui
> > 
> > Sent from my iPhone
> > 
> > On Jul 23, 2007, at 7:00 PM, Will Farrington <wcfarrington at gmail.com>  
> > wrote:
> > 
> > >
> > > On Tue, 2007-07-24 at 00:47 +0200, Kristian Lyngstøl wrote:
> > >> Please don't top quote and only quote the relevant part you are  
> > >> answering to.
> > >>
> > >> On 7/24/07, Will Farrington <wcfarrington at gmail.com> wrote:
> > >>> Simply put, within hours we'd have had a Digg posting on the front  
> > >>> page
> > >>> and 328793754 rabid forum-goers all trying desperately to have  
> > >>> their own
> > >>> individual little request put into the theme... and as a result  
> > >>> things
> > >>> would take longer and the final product would be of lesser quality.
> > >>
> > >> People keep throwing this argument right and left. That we get
> > >> attention shouldn't be a reason to choose a closed development cycle.
> > >> And I also think you overestimate the importance of this. If digg
> > >> people really want to read all about it, then why shouldn't they be
> > >> allowed to?
> > >
> > > Because it's begging people to judge an unfinished product as if it  
> > > were
> > > a finished one. After all, it's unfair to both the person designing  
> > > the
> > > layout as well as the project which is represented by the layout when
> > > people begin to assume and critique it as if it's an entirely final
> > > product - which it isn't.
> > >
> > 
> > Aren't we trying to do an open project here? Isn't the whole point  
> > that there is no "finished" until the users say so?
> 
> In terms of code, this is true.
> 
> But web development is not at all comparable to development of code.
> There is no "sourceforge" for developing websites for many reasons.
> Simply put, "opening up" web development is not a feasible solution by
> any stretch of the imagination.
> 
> That is not to say that once the website is launched that feedback will
> not be accepted, and in fact appreciated, from the users - but rather
> that such feedback in the middle of the design process offers no
> immediately rewarding gains and instead puts more undue stress on those
> developing the website in question.
I couldn't agree more here. Nobody steps up to an artist who is
currently in the middle of his work and says: "Oh, why don't you put a
little bit of green there? Doesn't that look better?" ... And that is
indeed a major difference between programming and web-development. 

A programmer _needs_ input from his users, way before his work reaches a
complete state - a webdeveloper instead _hates_ input from other people
before he sees his work as (somehow) finished. Even though he may feel
like presenting his work to other people earlier (for whatever reason),
it doesn't mean he wants to hear constructive critics.

In sense of art there is no thing like "constructive criticism" - only
complaining based on differing tastes ... ;)

> 
> _______________________________________________
> Admin mailing list
> Admin at lists.compiz-fusion.org
> http://lists.compiz-fusion.org/mailman/listinfo/admin