Re: WISH LIST

> This sounds more like a TODO list. (TODO = what the developer thinks
> should be done, WISHLIST = what the users would like to see.)
>
> Well, as Plato so diligently points out, design decisions that require
> _expertise_ should not be thrown to the _majority_ do decide.

TODO vs WISHLIST

Lets have a look at in my way. In the wish list that I suggested it is on
the developer to select the features for next version of the project.
Because:

- it his/her project

- it is necessary for the project to have a shape, so there must be some
final arbiter

- there are more factors in the game (how complicated it is to program the
feature, how much time is available, what other features are being
developed, etc.)

This is the TODO part of it.

On the other hand the wishlist has to be populated by comments requests etc.
from other people

Because:

- the project is usually developed with the intention to please and attract
some users (so it is not a case of a pure autistic mind doing it only for
selfpleasure without any respect to other people)

- it gives you feedback of how others perceive the intended feature (Will
they understand it? And how can I make it in understandable design?)

- it gives other users an information what features are currently most
relevant to discuss (probably those that are going top be implemented soon)

- it also gives better information to decide which version of logo to use
(the desicion is based on current capabilities and the probability that it
will be able to evolve in the future).



Ad PLATO

a) Who posses enough expertise to be able to enter the discussion about new
features? In fact this an inverse version of the recent e-mails "techies vs
teachers".

b) Here it is on the developer to decide whether it is made only for experts
(and knowing many experts - in the ultimate meaning this would involve only
the developer himself) or whether it is intended for broader audience. And
accepting the concept that the developer is not the only soul in the
universe who can have a good idea about the project is very important for
making a good version of logo.



Petr


.

Relevant Pages

  • Re: OOP/OOD Philosophy
    ... The methodology is well-documented. ... It is agile because the term 'extreme' as been so over-exposed that the ... > in which you do design can enable the team to respond to change, ... > that surveys of users have shown that nearly 50% of all features in a BDUF ...
    (comp.object)
  • Re: OO Design induces an existential crisis
    ... You call yourself an experienced business applications ... that is pretty good for meeting the principles of both OO design and SOA ... If they are reading one of my articles, they are probably a developer ... a function point counter and a cost wonk, ...
    (comp.object)
  • =?windows-1252?Q?www=2Eelectronics=2Dmac=2Dsony=2Ecom___Motorola_KRZR_K1_Phon?= =?windows-12
    ... Product Features and Technical Details ... the KRZR K1 is the definitive handset for those who ... design, you get Bluetooth wireless technology, an integrated music ... detailing and premium materials shrouded within a distinctive metallic ...
    (alt.cellular.verizon)
  • Re: Code generation - Was: AOP in PHP - Was: OO in PHP
    ... It's called meta programming and though the concepts ... else (or there is no performance problem at all), ... There is much design humbug with respect to C++ and Java ... More features usually means more code. ...
    (comp.lang.php)
  • Re: VS2005 Not ready for prime time
    ... Css features are extremely lacking. ... It demanded more knowledge of the developer, ... Microsoft hit the ball right out of the park. ... (like all the code-behind and project model "improvements" in ASP.NET ...
    (microsoft.public.dotnet.framework.aspnet)
Loading